Re: [-mm patch] seccomp: don't say it was more or less mandatory
From: Andrea Arcangeli
Date: Tue Mar 15 2005 - 11:47:47 EST
Oe Tue, Mar 15, 2005 at 04:05:26PM +0100, Ingo Molnar wrote:
> ugh? Where do i claim any such thing?
You never said such a thing, but you said you believe it's not provable
that sys_read/write and hardware irq processing is secure in linux, so
I wanted to get some statistical significance about your claim from you
just in case I was missing something. I obviously can't have in memory
every single bug since 2.4.0.
> while we are at it, please mention a single ptrace bug in the same
> timeframe that could allow a bytecode 'client' to escape a ptrace
> TRACE_SYSCALL jail at will.
There was this bug around 2.4.10, IIRC a SIGCONT could let the ptraced
task to continue executing. I don't want to depend on other applications
not to send a signal by mistake to the ptraced task.
An oom killer triggering by mistake on a strace -p would have been
enough too. You said if the ptracer is the group leader then the ptraced
task will be killed at the same time, but I doubt many apps depends on
this to be safe, that code is complex and it may break over time during
development if signal handling changes or if the exit code changes.
The interesting point is that no app out there (except uml) becomes
exploitable if you find some hole in TRACE_SYSCALL (at worse strace will
screwup a bit). I don't think an huge amount of research has been done
in those code paths (unlike it happened in mremap and many other kernel
APIs). So even if there are bugs in ptrace they might not being
considered security related. And UML has no other way than to use ptrace
since it needs much more of what I need and UML cannot be arch
While any seccomp security bug is guaranteed to be a major security
linux bug too, so I'm more confortable that more research has been done
in those core code paths than in TRACE_SYSCALL behaviour.
This below is all the code I had to write to secure the remote bytecode
with seccomp, and it's fully arch indipendent (licence is LGPL). Ok,
the seccomp kernel patch is 500 lines, so we should add 500 lines plus
the below ~50 total ~550 lines, but the end result is much nicer and
more secure IMHO. Plus this is simple enough that perhaps Cpushare won't
be the only project using it.
def __init__(self, seccomp, d_start, d_end):
self.seccomp = seccomp
self.d_start, self.d_end = d_start, d_end
self.outReceived = self.enable_seccomp_mode
self.transport.closeChildFD(2) # close stderr right away
self.transport.writeToChild(0, self.seccomp.header + self.seccomp.text_data)
def enable_seccomp_mode(self, data):
assert data == MAGIC_ASK_SECCOMP, "didn't ask seccomp"
seccomp_file = '/proc/' + str(self.transport.pid) + '/seccomp'
if file(seccomp_file, 'r').read(1) != '0':
raise 'seccomp already enabled?'
if file(seccomp_file, 'r').read(1) != '1':
assert self.transport.pid is not None
print 'Killing the seccomp-loader before it starts the untrusted bytecode'
raise 'seccomp enable failure'
self.outReceived = self.send_to_server
self.d_start.callback(None) # now the buyer is connected
def send_to_server(self, data):
self.seccomp.cpushare_protocol.sendString(PROTO_SECCOMP_FORWARD + data)
def recv_from_server(self, data):
def errReceived(self, data):
raise "shouldn't happen"
def processEnded(self, status):
if status.value.exitCode or status.value.signal:
if status.value.exitCode == 4:
print 'Failure in setting the stack size to %d bytes.' % self.seccomp.stack
if status.value.signal == signal.SIGKILL:
print 'Seccomp task gracefully killed by seccomp.'
elif status.value.signal == signal.SIGSEGV:
print 'Seccomp task gracefully killed by sigsegv.'
elif status.value.signal == signal.SIGQUIT:
print 'Seccomp task killed by sigquit - should never happen.'
print 'Seccomp task completed successfully.'
if self.transport.pid is not None:
if self.transport.pid is not None:
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/