It’s a funny artifact because most people today use, and have only used Linux in a “single user” context. The “local system administrator” is me!
And that's why we should 1) switch from using "sudo some-command --some-argument" to "some-command --some-argument" in which some-command authenticates and elevates via polkit, and 2) configure polkit to allow the initial human user of the machine to elevate without typing a password. #2 is just a default, and special configurations can of course override it and return a configuration much like what we have today. Bu…
When was the famous "sudo warning" introduced? (2019)
51–60 of 180 posts
Re: When was the famous "sudo warning" introduced? (2019)
#52Re: When was the famous "sudo warning" introduced? (2019)
#53I thought this is about the other warning, which has since been removed: https://github.com/sudo-project/sudo/commit/6aa320c96a376136...
Re: When was the famous "sudo warning" introduced? (2019)
#54I thought this is about the other warning, which has since been removed: https://github.com/sudo-project/sudo/commit/6aa320c96a376136...
What's with all the F responses? I appearedly missed this fad.
Re: When was the famous "sudo warning" introduced? (2019)
#55Earlier quoted context omitted.
I think this is underrated as a design flaw for how Linux tends to be used in 2024. At its most benign it's an anachronism and potential source of complexity, as its worst it's a major source of security vulnerabilities and unintended behavior (eg linux multitenancy was designed for two people in the same lab sharing a server, not for running completely untrusted workloads at huge scale, so it doesn't really implemen…
Actually, I have been wondering if using a Linux system as multi-user could be a boon in security. As single user, each and every process has full and complete control of $HOME. Instead, I would prefer all applications were sandboxed to their own little respective areas with minimal access to data unless explicitly authorized. Without going full QubeOS, get some amount of application separation so my photo utility do…
Re: When was the famous "sudo warning" introduced? (2019)
#56Re: When was the famous "sudo warning" introduced? (2019)
#57Earlier quoted context omitted.
> Except if you're on a team of sysadmins running a fleet of systems not trying to be rude but this doesn't sound like "most people"
Interesting comment actually. I would have assumed that the vast majority of people using Linux are still sysadmins in small and large companies - this is certainly my personal experience. I wonder how many home users there are versus systems managed by sysadmins. I would still think there’s more in the corporate world, while I would think the opposite for Windows.
Kind regard, Roel (former physicist, developing Android apps (for fun) on my Linux laptop, owner of multiple NAS, but never having been a sysadmin in any company)
Re: When was the famous "sudo warning" introduced? (2019)
#58Back in the 90s we were told ostentatiously to include "unauthorised access is not permitted" to the login prompt. Why? Because the login prompt said "please login:" and this was being read by some bush lawyer as an invitation to connect, and therefore would impede a case if we had a hacker login with a stolen password. I think it was founded on urban myth, but I assure you this is what we were told to do: add text t…
Re: When was the famous "sudo warning" introduced? (2019)
#59Earlier quoted context omitted.
Qubes takes that to an extreme: https://www.qubes-os.org/intro/ and runs every application in a virtual machine.
I was experimenting with taking that to a median using containers in nixos. IMO the distinguishing feature of qubes is the fact that there's chrome indicating the security level of a window based on its vm - I put together https://github.com/andrewbaxter/filterway to use with window manager rules to hopefully get the same result.