[lkml]   [1996]   [Dec]   [12]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Proposal: restrict link(2)

In, article <>, (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:
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="">here</A>. 42

 \ /
  Last update: 2005-03-22 13:38    [W:0.145 / U:0.300 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site