On Di, Aug 07, 2018 at 01:18:59 +0300, Reco wrote:
I never had your mentioned problems.Either you have /sbin in your user's path, or you haven't run a single apt-get all these years. There are other possibilities, of course, though less flattering.
Bullshit again. You didn’t read the thread, did you?This is new behaviour in testing because Debian switched the source for the su binary.
Debian 9: stse@fsing:~$ echo $PATH /home/stse/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games stse@fsing:~$ su Passwort: root@fsing /home/stse # echo $PATH /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin Testing: [stse@osgiliath]: echo $PATH /home/stse/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games:/home/stse/wego/bin [stse@osgiliath]: su Passwort: osgiliath:/home/stse# echo $PATH /home/stse/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games:/home/stse/wego/bin Testing with „ALWAYS_SET_PATH yes” in login.defs: [stse@osgiliath]: echo $PATH /home/stse/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games:/home/stse/wego/bin [stse@osgiliath]: su Passwort: osgiliath:/home/stse# echo $PATH /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin I hope you see the difference.
„su” doesn’t change the working directory. So if you compile software as a user you can then type „make install” after su.True. But this tidbit does not relate to this particular problem at all.
It does. Depending on your needs you could use „su” or „su -”.
Now it is simpler to compile as root user.It was always 'simpler'. But not 'smarter'.
Doesn’t matter, security is always a compromise. If it gets to much work it will be reduced.
If you need to run an X11 program as root su preserved the DISPLAY variable.And it also preserves $HOME. So any changed configuration file will be owned by root. Not a big deal if you never try to run the program in
Only if the file never existed.
Luckily you can switch back to the old behaviour, but this should be the default.Care to provide a Debian bug number that you filled on this particular issue? Because rants on debian-user do not transform to patches by themselves.
Which patches?
As Linus would say: „Don’t break user behaviour! Give them an option to switch to a new one.”.A recent kernel update (linux-4.9.110-3+deb9u1) begs to differ. Two notable behaviour changes without any way to disable them.
Are these security changes? Then Linus permits it if there is no other way. By the way, what are these changes that are breaking user space?
Shade and sweet water! Stephan -- | Public Keys: http://fsing.rootsland.net/~stse/keys.html |
Attachment:
smime.p7s
Description: S/MIME cryptographic signature