Subject: Re: login.conf integration?
To: None <>
From: Martin J. Laubach <>
List: tech-security
Date: 01/23/2000 21:00:14
  by with SMTP; 23 Jan 2000 20:00:18 -0000
	Sun, 23 Jan 2000 21:00:14 +0100 (CET)
Date: Sun, 23 Jan 2000 21:00:14 +0100 (CET)
From: "Martin J. Laubach" <>
Message-Id: <>
Subject: Re: login.conf integration?
In-Reply-To: <>
References: <> <>

  Peter Seebach just discovered that I accidentially added a piece
of code to our su(1) that wipes out the path and replaces it by the
default settings if one sus to root.

  From the following discussion on current-users:

| >   I can see the rationale in it (not having root depend on
| > other people's path settings (for security reasons)), however it
| > conflicts with the description in the manpage.
| > 
| >   Not sure what TRT is, fix the behaviour or the documentation?

  So what now? I don't really care much which solution we adopt
(a) su squashing the previously set path for the default path
(or what is set in login.conf) as it is now, or (b) reverting
to what we had before, su leaving the path alone.