|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
Subject: Re: dangerous?
From: Joseph S. Myers (jsm28
cam.ac.uk)Date: Mon May 08 2000 - 16:56:18 CDT
- Next message: Solar Designer: "Re: dangerous?"
- Previous message: Mitchell Blank Jr: "Re: dangerous?"
- In reply to: Chris Evans: "dangerous?"
- Next in thread: Solar Designer: "Re: dangerous?"
- Reply: Joseph S. Myers: "Re: dangerous?"
- Reply: Solar Designer: "Re: dangerous?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Mon, 8 May 2000, Chris Evans wrote:
> mknod pipe p
>
> then write a program which does uselib("./pipe") - any type of inode is
> accepted
Perhaps there should be a CONFIG_NO_AOUT option to disable uselib() and
other a.out compatibility code altogether in the kernel - since AFAIK
uselib() is only relevant to a.out binaries - along with whichever of the
obsolete syscall versions are only used by a.out libraries, and support
for a.out libraries in ELF format and ELF interpreters in a.out format.
Then people with ELF-only systems can enable it and avoid any security
problems that might be lurking in this compatibility code.
-- Joseph S. Myers jsm28
- Next message: Solar Designer: "Re: dangerous?"
- Previous message: Mitchell Blank Jr: "Re: dangerous?"
- In reply to: Chris Evans: "dangerous?"
- Next in thread: Solar Designer: "Re: dangerous?"
- Reply: Joseph S. Myers: "Re: dangerous?"
- Reply: Solar Designer: "Re: dangerous?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]