view the rest of the comments
Linux
Welcome to c/linux!
Welcome to our thriving Linux community! Whether you're a seasoned Linux enthusiast or just starting your journey, we're excited to have you here. Explore, learn, and collaborate with like-minded individuals who share a passion for open-source software and the endless possibilities it offers. Together, let's dive into the world of Linux and embrace the power of freedom, customization, and innovation. Enjoy your stay and feel free to join the vibrant discussions that await you!
Rules:
-
Stay on topic: Posts and discussions should be related to Linux, open source software, and related technologies.
-
Be respectful: Treat fellow community members with respect and courtesy.
-
Quality over quantity: Share informative and thought-provoking content.
-
No spam or self-promotion: Avoid excessive self-promotion or spamming.
-
No NSFW adult content
-
Follow general lemmy guidelines.
Debian in its GUI (at least KDE, which I'm using at the moment) demanding the root password to install the updates it's blinking at me about in the tray all the time. In this context, demanding a password at all is rather silly (Windows doesn't require your password to install updates in a single user environment, and it doesn't even pop up a UAC prompt) and this is going to be yet another one of those things that prior Windows users will moan about, declaring that "Linux is complicated and hard" and drive them back to the comfort of the devil they know when they feel like their own computer is actively trying to stymie them at seemingly every turn.
My user account is a sudoer so there is absolutely no technical reason my own password shouldn't work. And, in fact, if I run updates via apt in a terminal it does. But allowing updates to install from the desktop environment, something ostensibly ought to be a routine userspace kind of operation, requires everyone using the system who might want to do this to know the system-wide root password. This is a monumentally stupid idea.
I am well aware there are myriad ways around this but they all involve hand-editing config files and come with stern warnings about "this may break your system so proceed 'carefully,'" as if anyone who is not already an experienced Linux nerd will know just what the hell "proceeding carefully" is supposed to look like.
The inevitable XKCD comic succinctly sums this up:
The UNIX permissions and administration model may have made great sense on glass teletypes in the '70s and when nobody knew any better, but it's certainly long outmoded now. It's going to make a lot of people very angry to read this, but that's actually one of the few things that Windows does much better, at least starting from NT onwards.
Doesn't Ubuntu disable the root user out of the box and expect these actions to be performed via sudo/polkit. There is clearly a precedent for not needing a root password and being able to use your own user's password for these kinds of things. So it is a monumentally stupid idea to require the system-wide root password, but not one that is done by all of linux, and seems to be a decision made by your distro to not use the modern solution.
The fact is though, you're right and the pain point is that distros are still doing things the silly way.
If I can
sudo apt installwithout requiring a password, I could generate a package that installs a custom sudoers config file that allows me to do anything, so "passwordless sudo, but just for apt" is potentially easily exploitable to gain full access. But that also still assumes A) you care and B) someone has access to your account anyway (at which point you may already have bigger problems)While I have switched from Windows to Mint with most of my PCs, permissions are the single most annoying thing I still deal with on Linux. And have been over the last decade of trying out distros over the years. I truly detest the way permissions work and were the main reason it took me so long to switch. The current political world and tech company garbage is what did it.