Stories
Slash Boxes
Comments

SoylentNews is people

SoylentNews is powered by your submissions, so send in your scoop. Only 15 submissions in the queue.
posted by martyb on Monday August 31 2015, @04:29PM   Printer-friendly
from the so-su-me dept.

The Linux Homefront Project reports on Lennart Poettering looking to do away with the good old "su" command. From the article, "With this pull request systemd now support a su command functional and can create privileged sessions, that are fully isolated from the original session. Su is a classic UNIX command and used more than 30 years. Why su is bad? Lennart Poettering says:"

Well, there have been long discussions about this, but the problem is that what su is supposed to do is very unclear. On one hand it’s supposed to open a new session and change a number of execution context parameters (uid, gid, env, …), and on the other it’s supposed to inherit a lot concepts from the originating session (tty, cgroup, audit, …). Since this is so weakly defined it’s a really weird mix&match of old and new paramters. To keep this somewhat managable we decided to only switch the absolute minimum over, and that excludes XDG_RUNTIME_DIR, specifically because XDG_RUNTIME_DIR is actually bound to the session/audit runtime and those we do not transition. Instead we simply unset it.

Long story short: su is really a broken concept. It will given you kind of a shell, and it’s fine to use it for that, but it’s not a full login, and shouldn’t be mistaken for one.

I'm guessing that Devuan won't be getting rid of "su."


Original Submission

 
This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 4, Informative) by Non Sequor on Tuesday September 01 2015, @03:13AM

    by Non Sequor (1005) on Tuesday September 01 2015, @03:13AM (#230625) Journal

    Interestingly here's a spec for the XDG stuff with Pottering's name on it:

    http://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html [freedesktop.org]

    That spec seems to be a fancy way of telling programs to ignore HOME and put stuff some place else. I guess what's happening here is that now Poettering is having to reinvent an axle to connect two wheels he's reinvented.

    I'm slightly bemused by this and all I'll say is that on OS X (and to a lesser extent, Cygwin) the traditional Unix bits seem to continue to conform to my expectations and the whizbang stuff stays on its side of the chalk line and does it's own thing although there are still some interfaces to the Unix side. I don't see why that approach shouldn't be considered good enough in general. It's easier to interface new stuff to Unix than to redesign Unix to build in the new interfaces you think you need.

    --
    Write your congressman. Tell him he sucks.
    Starting Score:    1  point
    Moderation   +2  
       Interesting=1, Informative=1, Total=2
    Extra 'Informative' Modifier   0  
    Karma-Bonus Modifier   +1  

    Total Score:   4