From owner-freebsd-hackers  Sun Nov  7  3:11:16 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11])
	by hub.freebsd.org (Postfix) with SMTP id D19D814E08
	for <freebsd-hackers@freebsd.org>; Sun,  7 Nov 1999 03:11:11 -0800 (PST)
	(envelope-from dwmalone@maths.tcd.ie)
Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP
          id <aa31599@salmon>; 7 Nov 1999 11:11:10 +0000 (GMT)
To: "Daniel C. Sobral" <dcs@newsguy.com>
Cc: freebsd-hackers@FreeBSD.ORG
Subject: Re: Procfs' pointers to files. 
In-reply-to: Your message of "Sun, 07 Nov 1999 02:25:55 +0900."
             <382464A3.F8A3ADA7@newsguy.com> 
X-Request-Do: 
Date: Sun, 07 Nov 1999 11:11:10 +0000
From: David Malone <dwmalone@maths.tcd.ie>
Message-ID:  <199911071111.aa31599@salmon.maths.tcd.ie>
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> Err... I don't see the problem. The permissions of the hardlink will
> be different, so the user might be able to see the "code", but won't
> be able to run the suid (because the hardlink won't have the suid
> bit set).

Suid bit is stored in the inode, not the directory entry, so it will
be set. I've tested it - try running su in one window, don't type
the password, and then run /proc/pid/file and typing the password.

	David.


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message