Re: access() is a security hole?
From: Bruce Evans (bde@zeta.org.au)
Date: 10/12/02
- Next message: Alex Pavlovic: "RE: monitor ALL connections to ALL ports"
- Previous message: zhuravlev alexander: "Re: monitor ALL connections to ALL ports"
- In reply to: David Schultz: "Re: access() is a security hole?"
- Next in thread: The Anarcat: "Re: access() is a security hole?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Sat, 12 Oct 2002 18:02:02 +1000 (EST) From: Bruce Evans <bde@zeta.org.au> To: David Schultz <dschultz@uclink.Berkeley.EDU>
On Fri, 11 Oct 2002, David Schultz wrote:
> ...
> Really, there ought to be a version of the open syscall that takes
> an argument specifying the credentials to use for the call, but
> instead we're stuck with the lovely setuid suite of functions.
Unmentionablux has had the setfsuid suite for some time now.
Bruce
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-security" in the body of the message
- Next message: Alex Pavlovic: "RE: monitor ALL connections to ALL ports"
- Previous message: zhuravlev alexander: "Re: monitor ALL connections to ALL ports"
- In reply to: David Schultz: "Re: access() is a security hole?"
- Next in thread: The Anarcat: "Re: access() is a security hole?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]