On Thu, 2 Dec 1999, Alexander Viro wrote: >such games link() is the least of your problems - it's effect can be >completely reproduced with plain open(). exec 42</bar/foo and several >hours after that sh -c /dev/fd/42 will do the trick - fork() preserves >open descriptors. If there was really a security hole the intruder could as well exploit the system and change the kernel at runtime to hide his backdoors and change the partition table and the lilo executable to continue to patch the kernel at runtime to continue to provide his backdoors even after the administrator rebooted or reinstalled a new kernel. That's not the point. I completly agree with you that the suid hardlink issue is not a good point for the above issues. Doing >suid is the right thing to do. But for the quota forbidding the hardlink in such case is a good point IMHO. Andrea
- Re: Can't hardlink in diffe... Kjetil Torgrim Homme
- Re: Can't hardlink in d... Alexander Viro
- Re: Can't hardlink in d... Kjetil Torgrim Homme
- Re: Can't hardlink in d... Alexander Viro
- Re: Can't hardlink in different dirs... Pavel Machek
- Re: Can't hardlink in different ... Brandon S. Allbery KF8NH
- Re: Can't hardlink in different ... Horst von Brand
- Re: Can't hardlink in different dirs. (BUG#826) Alexander Viro
- Re: Can't hardlink in different dirs. (BUG#8... Peter J. Braam
- Re: Can't hardlink in different dirs. (B... Alexander Viro
- Re: Can't hardlink in different dirs... Andrea Arcangeli
- Re: Can't hardlink in different ... Alexander Viro
- Re: Can't hardlink in diffe... Peter J. Braam
- Re: Can't hardlink in d... Richard Gooch
- Re: Can't hardlink in d... Andrea Arcangeli
- Re: Can't hardlink in d... David Woodhouse
- Re: Can't hardlink in d... Richard Gooch
- Re: Can't hardlink in d... Andrea Arcangeli
- Re: Can't hardlink in d... Richard Gooch
- Re: Can't hardlink in d... Andrea Arcangeli
- Re: Can't hardlink in d... Richard Gooch