Messages in this thread |  | | From | (Matthias Urlichs) | Subject | Re: Proposal: restrict link(2) | Date | 12 Dec 1996 11:40:55 +0100 |
| |
In linux.dev.kernel, article <m0vXnoO-0001bNC@ceres.tat.physik.uni-tuebingen.de>, koenig@tat.physik.uni-tuebingen.de (Harald Koenig) writes: > > why is Joe Random Cracker allowed to make a hard link to /etc/passwd at all > (or to any other file not owed by him) ? > Because that's the Unix semantics. If you can write to a directory and you can execute the directory a file resides in, then you can make a link to that file.
Face it, people, setuid-root programs are _difficult_ to get right. Unless we get an ACL implementation with appropriately-fine-grained rights it will IMHO never be possible to find all the holes.
-- Talent is what you possess; genius is what possesses you. -- Matthias Urlichs \ noris network GmbH / Xlink-POP Nürnberg Schleiermacherstraße 12 \ Linux+Internet / EMail: urlichs@noris.de 90491 Nürnberg (Germany) \ Consulting+Programming+Networking+etc'ing PGP: 1024/4F578875 1B 89 E2 1C 43 EA 80 44 15 D2 29 CF C6 C7 E0 DE Click <A HREF="http://info.noris.de/~smurf/finger">here</A>. 42
|  |