Universal "substitution"/"renaming" of open(2)

Thomas Bushnell, n/BSG tb@MIT.EDU
Thu Apr 30 11:54:00 GMT 1998


Such an extended open is a serious security problem in setuid
programs, and has other disturbing implications too.  I agree that
it's a nifty hack, but I think that it needs more than just a few
lines of code to decide whether it will have more serious
repercussions.




More information about the Libc-hacker mailing list