Re: Running Untrusted Code in a Restricted Process

From: Jeff Dike (jdike@karaya.com)
Date: Fri Jun 09 2000 - 21:46:20 EST

Next message: ronbarry@es.com: "unresolved symbols cropping up in a previously working driver."
Previous message: Andre Hedrick: "ATA100 support for ALI and HPT370 fixed"
In reply to: Alan Cox: "Re: Running Untrusted Code in a Restricted Process"
Next in thread: jesse hammons: "Re: Running Untrusted Code in a Restricted Process"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

alan@lxorguk.ukuu.org.uk said:
> > The old version of the tracing code (at least in i386) didn't allow
> > for
> > syscall_trace to reject system calls.

> Current 2.2.x does so.

For the record, this was added in 2.3.22 and 2.2.15 for i386.

Jeff

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

Next message: ronbarry@es.com: "unresolved symbols cropping up in a previously working driver."
Previous message: Andre Hedrick: "ATA100 support for ALI and HPT370 fixed"
In reply to: Alan Cox: "Re: Running Untrusted Code in a Restricted Process"
Next in thread: jesse hammons: "Re: Running Untrusted Code in a Restricted Process"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Thu Jun 15 2000 - 21:00:20 EST