SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Maybe it's primarily because my first GUI was DOS PCTools PCShell and Midnight Commander but I am heavily reliant on working from a File Manager in addition to from CLI. In Slackware that means I must "kdesu dolphin" a LOT because, unlike other distros that are serious enough to create a root account by default, for some reason with those, launching just "dolphin" as User, any action requiring root access immediately triggers a root password query. Perhaps I'm missing some config variable that is default in others but it is a bit of a PITA.
For home users doing system maintainence, is it safer to use sudo or log-in as root? I have read it is better to use sudo.
I don't like sudo...
It is safer [than using the root account] if you actually limit what programs you can run with it. ---BUT--- Every "home" user that I know just sets sudo permissions to ALL (which defeats the purpose).
I prefer to use root account because it's one more login, one more password to thwart intrusion. I disable ssh-root login and if someone gets my password they can't do much system damage unless they also get root's password too.
Raspbian's, Mint's, Ubuntu's, etctera's use of sudo is just plain crazy. Allowing a user total access to the system is the same as using the root account (security wise).
It is safer [than using the root account] if you actually limit what programs you can run with it. ---BUT--- Every "home" user that I know just sets sudo permissions to ALL (which defeats the purpose).
Agreed. As the system administrator you trust yourself to safely execute commands on your system. Maybe you have another user (a family member) that has log-in access to your system. Limiting what they can do is a good idea. You don't give them the root password and you set-up sudo so they can do only what you want with their user password. Here's a few tutorials on how to do that.
Raspbian's, Mint's, Ubuntu's, etctera's use of sudo is just plain crazy. Allowing a user total access to the system is the same as using the root account (security wise).
I agree, that's bonkers.
Last edited by hitest; 12-31-2022 at 11:42 AM.
Reason: Addition
Yes. Also as the system administrator you can configure sudo so that a user can only execute a defined set of root commands, that is, they can only do things that you allow them to do. This would be valuable if you have multiple users using the same box. There may be some users that you don't want to have full system access.
While that is absolutely true, you will have to be careful to prevent them running any commands from which they can subsequently run a command-line shell, since they can then run any command from that shell. That would entirely defeat the purpose.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.