From owner-freebsd-security Sun Mar 14 13:32:44 1999 Delivered-To: freebsd-security@freebsd.org Received: from mail-out2.apple.com (mail-out2.apple.com [17.254.0.51]) by hub.freebsd.org (Postfix) with ESMTP id A28B71546C for ; Sun, 14 Mar 1999 13:31:26 -0800 (PST) (envelope-from wsanchez@scv2.apple.com) Received: from mailgate1.apple.com (A17-128-100-225.apple.com [17.128.100.225]) by mail-out2.apple.com (8.8.5/8.8.5) with ESMTP id NAA50290 for ; Sun, 14 Mar 1999 13:29:02 -0800 Received: from scv2.apple.com (scv2.apple.com) by mailgate1.apple.com (mailgate1.apple.com- SMTPRS 2.0.15) with ESMTP id ; Sun, 14 Mar 1999 13:28:56 -0800 Received: from joliet-jake (joliet-jake.apple.com [17.202.40.140]) by scv2.apple.com (8.9.3/8.9.3) with SMTP id NAA10220; Sun, 14 Mar 1999 13:28:55 -0800 Message-Id: <199903142128.NAA10220@scv2.apple.com> To: Robert Watson Subject: Re: ACL's Cc: Thomas Valentino Crimi , freebsd-security@FreeBSD.ORG In-Reply-To: Date: Sun, 14 Mar 1999 13:28:52 -0800 From: Wilfredo Sanchez Reply-To: wsanchez@apple.com X-Mailer: by Apple MailViewer (2.106) Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org | BTW, I'd really like to get rid of hard links -- they allow users to | retain copies of setuid files after the owner thinks they are deleted. | I.e., user creates a hard link to /usr/sbin/somesetuidbin to | /usr/tmp/mytemp. Now the admin upgrades the machine, thinking they have | removed the risk of the now known buggy somesetuidbin. Is there any reason (other than "it always has been so") why users should be allowed to create hard links to files they don't own? -Fred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message