seccomp vs reading file input at startup

[GoogleCodeExporter]

$ ol --seccomp -e '(print "hello")'
hello
delivered
$ echo '(print "hello")' | ol -q --seccomp
hello
$ echo '(print "hello")' > /tmp/foo; ol --seccomp /tmp/foo
Killed

Technically this is correct, since the repl goes seccomp immediately after 
parsing arguments if requested, but it would probably be better to read the 
files to memory (sans parsing and eval) and only then go seccomp, so that only 
disallowed things happening during later stages could cause a kill. This would 
also make it possible to use #!/usr/bin/ol -Sr to make seccomp'd scripts that 
take arguments.

Original issue reported on code.google.com by aohelin on 14 Dec 2011 at 10:31

[GoogleCodeExporter]

Original comment by aohelin on 18 May 2012 at 7:59

• Added labels: Type-Enhancement
• Removed labels: Type-Defect