Date: Sun, 14 Mar 1999 17:39:58 -0500 (EST) From: David Gilbert <dgilbert@velocet.ca> To: Michael Richards <026809r@dragon.acadiau.ca> Cc: security@FreeBSD.ORG Subject: Getting rid of hard links? Message-ID: <14060.15038.71703.849469@trooper.velocet.ca> In-Reply-To: <Pine.GSO.4.05.9903141735000.1568-100000@dragon> References: <Pine.GSO.4.05.9903141735000.1568-100000@dragon>
next in thread | previous in thread | raw e-mail | index | archive | help
>>>>> "Michael" == Michael Richards <026809r@dragon.acadiau.ca> writes: Michael> the internals as I did not write it, however I am told our Michael> system can be ported over to OpenBSD with less trouble than Michael> fixing whatever requires the hard links. FreeBSD has served Michael> us well and I hope we don't have to abandon it :( Similarly, I have made a lot of diskless servers (100Mb networking is faster than cheep local disk for swap) and use hard links for each root extensively. Michael> It seems to me that the changes to rm/cp would be the Michael> smartest route because it wouldn't break anything and would Michael> seemingly address most of the issues brought up. Fixing the problem instead of the symptom? Maybe links (hard and soft) should only have the permissions that the user can create subject to a mask of permissions on the origional file? Ie: I can't create a link to a suid file that is suid unless I could create the suid file. Dave. -- ============================================================================ |David Gilbert, Velocet Communications. | Two things can only be | |Mail: dgilbert@velocet.net | equal if and only if they | |http://www.velocet.net/~dgilbert | are precisely opposite. | =========================================================GLO================ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?14060.15038.71703.849469>