Date: Wed, 15 Jan 2003 18:13:21 -0800 (PST) From: Mike Makonnen <mtm@FreeBSD.org> To: seanc@freebsd.org, mtm@FreeBSD.org, freebsd-bugs@FreeBSD.org, mtm@FreeBSD.org Subject: Re: kern/47119: Unable to su to root after root run's a command that runs as a different user Message-ID: <200301160213.h0G2DLSx033190@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
Synopsis: Unable to su to root after root run's a command that runs as a different user State-Changed-From-To: open->analyzed State-Changed-By: mtm State-Changed-When: Wed Jan 15 17:57:19 PST 2003 State-Changed-Why: This is my prelimanry finding: The problem is that when the user associated with the session is changed it propagates back to the parent, even though setsid(2) has been called. You are not able to su(1) after the program has completed because the user associated with the session (the login user) after the program has run is 'www'. I'll investigate some more and figure out if this should be expected, if the man page is wrong and calling setsid(2) is insufficient to completely disassociate from the parent's session, or if there is a bug somewhere. Responsible-Changed-From-To: freebsd-bugs->mtm Responsible-Changed-By: mtm Responsible-Changed-When: Wed Jan 15 17:57:19 PST 2003 Responsible-Changed-Why: This looks interesting. http://www.freebsd.org/cgi/query-pr.cgi?pr=47119 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200301160213.h0G2DLSx033190>