> Err... I don't see the problem. The permissions of the hardlink will > be different, so the user might be able to see the "code", but won't > be able to run the suid (because the hardlink won't have the suid > bit set). Suid bit is stored in the inode, not the directory entry, so it will be set. I've tested it - try running su in one window, don't type the password, and then run /proc/pid/file and typing the password. David. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
- Procfs' pointers to files. David Malone
- Re: Procfs' pointers to files. Daniel C. Sobral
- Re: Procfs' pointers to files. David Malone
- Re: Procfs' pointers to files. Warner Losh
- Re: Procfs' pointers to files. Brian Fundakowski Feldman
- Re: Procfs' pointers to files. Warner Losh
- Re: Procfs' pointers to files. Daniel C. Sobral
- Re: Procfs' pointers to files. Sean Eric Fagan
- Re: Procfs' pointers to files. Julian Elischer
- Re: Procfs' pointers to files. Brian Fundakowski Feldman
- Re: Procfs' pointers to files. David Malone
- Re: Procfs' pointers to files. Peter Jeremy
- Re: Procfs' pointers to files. Anthony Kimball