--NiDZvZUadYKQfYjZ Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Mar 08, 2004 at 10:10:38PM +0100, Georg-W. Koltermann wrote: +> When you restrict links, do you want to restrict copying as well? +>=20 +> Seems somewhat paranoid to me. You already need write permission on the +> directory where you create the link, and permissions are checked against +> the inode on open(2) anyway. This is because this gives an attacker some possibilities. For example he is able to create hard link to some set-uid binary. After some time, a security-related bug will be found in this application, administrator will change it with good version, but old, vulnerable version will be still in system. Administrator have to be really careful when fixing such problems and check number of hard links or just remove such program using 'rm -P'. --=20 Pawel Jakub Dawidek http://www.FreeBSD.org [email protected] http://garage.freebsd.pl FreeBSD committer Am I Evil? Yes, I Am! --NiDZvZUadYKQfYjZ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFATO7cForvXbEpPzQRAvIpAJ9bKqicZVWDBQRJ57qKBsRLwGgO+QCfV1js oVFxSzMdD90ZTqW+V7J2dW8= =00ZR -----END PGP SIGNATURE----- --NiDZvZUadYKQfYjZ--