Why do all the sudo? [was Re: Software updater no longer functional]

Ralf Mardorf silver.bullet at zoho.com
Fri Jan 27 17:06:45 UTC 2017


Btw. I'm used to be root all the time, when running another Linux in a
container.

[root at archlinux rocketmouse]# systemd-nspawn -qD /mnt/moonstudio 
[root at moonstudio ~]# lsb_release 
No LSB modules are available.
[root at moonstudio ~]# logout
[root at archlinux rocketmouse]# systemd-nspawn -bqD /mnt/moonstudio
                                              ^ with the boot option,
                                              it's possible to log in
                                              as user
as well as using sudo

[root at archlinux rocketmouse]# systemd-nspawn -qD /mnt/moonstudio
[root at moonstudio ~]# sudo -i -u weremouse
[weremouse at moonstudio ~]$

but with "-b" it takes longer and I dislike to type "sudo -i -u foo". An
alias IMO is inappropriate for anything security related. Not only for
su and sudo, but also for "rm -i" and similar commands.

Sometimes it's required to log in as user, if I e.g. booted Ubuntu
and run Arch Linux in a container, since building a package for Arch
once provided the option "--asroot", but for good reasons it was
dropped. IOW root can't build packages, this only could be done using a
fakeroot environment.

I'm not in general against compiling with root privileges, but it
definitively is better to avoid this.




More information about the ubuntu-users mailing list