util-linux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ludwig Nussel <ludwig.nussel@suse.de>
To: Karel Zak <kzak@redhat.com>
Cc: "Pádraig Brady" <P@draigBrady.com>,
	"Werner Fink" <werner@suse.de>,
	"Thomas Bächler" <thomas@archlinux.org>,
	util-linux@vger.kernel.org, "Dave Reisner" <d@falconindy.com>,
	"Tobias Powalowski" <tpowa@archlinux.org>
Subject: Re: [su] New su utility messes with my PATH
Date: Fri, 21 Sep 2012 09:54:32 +0200	[thread overview]
Message-ID: <505C1D38.2090005@suse.de> (raw)
In-Reply-To: <20120920094330.GC16499@x2.net.home>

Karel Zak wrote:
> On Sat, Sep 15, 2012 at 03:43:29PM +0100, Pádraig Brady wrote:
>> On 09/15/2012 02:17 PM, Thomas Bächler wrote:
>>> I found what I think is absolutely unexpected behaviour in the new su
>>> utility. It seems to have been introduced by commit a6fdd3f8.
>>>
>>> It is about /sbin and /usr/sbin being in the path: Whenever you switch
>>> to a non-root user, they are removed from the path, and when you switch
>>> to root, they are added. I find it completely unexpected that su (when
>>> not running with -l) messes with my environment at all.
>>>
>>> Commands like
>>>  PATH=... su -c "cmd" user
>>> do not work as expected.
>>>
>>> In my opinion, when you wish your path (or anything in the environment)
>>> to change you should a) use -l to start a login shell or b) configure
>>> your scripts to take care of it.
>>>
>>> I propose to revert the mentioned patch. Opinions?
>>
>> Ouch, I agree.
>> su shouldn't be messing with PATH at all IMHO.

Well, su is such a mess that you better not make any assumptions about
it. Avoid su if you can.

> It's Suse patch, I guess there is/was any reason for the patch
> 
>         commit a6fdd3f8125be23930d955c2bc6b7a46cdaf8a12
>         Author: Werner Fink <werner@suse.de>
>         Date:   Tue Aug 17 09:09:55 2010 +0200
> 
>         make sure /sbin resp /usr/sbin are in PATH
> 
> 
> Werner, Ludwig? What about to revert the patch?

Personally I don't really mind. I don't know the background of the patch
though. IMO using 'su' instead of 'su -' is broken anyways so making the
former less convenient may help teaching people to use 'su -' instead.

cu
Ludwig

-- 
 (o_   Ludwig Nussel
 //\
 V_/_  http://www.suse.de/
SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) 

  reply	other threads:[~2012-09-21  7:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-15 13:17 [su] New su utility messes with my PATH Thomas Bächler
2012-09-15 14:43 ` Pádraig Brady
2012-09-20  9:47   ` Karel Zak
2012-09-21  7:54     ` Ludwig Nussel [this message]
2012-10-02  8:17     ` Karel Zak
2012-10-02  8:23       ` Thomas Bächler

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=505C1D38.2090005@suse.de \
    --to=ludwig.nussel@suse.de \
    --cc=P@draigBrady.com \
    --cc=d@falconindy.com \
    --cc=kzak@redhat.com \
    --cc=thomas@archlinux.org \
    --cc=tpowa@archlinux.org \
    --cc=util-linux@vger.kernel.org \
    --cc=werner@suse.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).