Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

When was the famous "sudo warning" introduced? (2019)

retrocomputing.stackexchange.com

Post reply on HN
Print view View original

111–120 of 180 posts

Re: When was the famous "sudo warning" introduced? (2019)

#111

Post by fsckboy »

aerzen wrote: post #105
TheSpiceIsLife wrote: post #50

Earlier quoted context omitted.

Other way round for me

What kind of sysadmins are they then? I don't want to sound dismissive, but is a "windows sysadmins" a thing? Do companies run windows on servers?

windows sysadmins are very much a thing. desktop and laptop MS Windows installed in any company doing anything important is sysadmin'ed centrally. If you require security (not to leak company info) you must disable the ability for users to install anything. The side benefit of this is that the admins can admin other things like mail servers, ip addresses, etc. My gf (accountant) has to call the sysadmins to plug in an external display at home, which they can do remotely at 2 in the morning.

Re: When was the famous "sudo warning" introduced? (2019)

#112

Post by saghm »

71bw wrote: post #85
yjftsjthsd-h wrote: post #40

Earlier quoted context omitted.

Okay, then just NOPASSWD yourself?

I've always had issues with nopasswd, maybe it's just a thing with how I'm doing it but it never seems to work in Arch

I've personally never had issues with it on Arch; I agree with the sibling comment that some issue with groups might be the the issue. In case it helps, here's what I always do to set it up on a new installation:

1. Install `sudo` via pacman 2. Optionally set the EDITOR env var to use something other than vi for the following command, e.g. `export EDITOR=nvim` (if you do change it and want to retain the default shortcuts like `ctrl+a` to go to the beginning of the line, you'll also probably want to do `set -o emacs` to make sure it doesn't get changed due to the EDITOR being set) 3. Run `sudo visudo` (or `sudo -E visudo` if you want to make sure the `EDITOR` env var is used) to edit the sudoers file and look for the line `%wheel ALL=(ALL:ALL) NOPASSWD: ALL`. Uncomment that one, and comment out the one slightly above that's the same but doesn't have `NOPASSWD`. Save and exit the editor. 4. If you're not already a member of the `wheel` group, add yourself with `usermod -aG wheel `. You might need to log out and back in or reboot to this to take effect; groups are often weird like that.

As an alternative, Arch has `opendoas` in the `extra` repos nowadays, which is a port of the OpenBSD replacement for sudo designed to be easier to configure. There's literally no configuration for it by default, and to enable passwordless, all you need to put in `/etc/opendoas.conf` is `permit nopass :wheel`.

Re: When was the famous "sudo warning" introduced? (2019)

#114

Post by bubblethink »

thrw42A8N wrote: post #80
bubblethink wrote: post #77

Earlier quoted context omitted.

No, the US is the main country that loves these messages. Have you seen the size of universities or the government ? It's just clerical staff doing make believe work. Go to any .gov website. They'll throw up a wall of bs before you log in (e.g., https://ttp.dhs.gov/ ).

Sounds like you have never been to Europe. Here they make you actually sign (as in pen and paper) this stuff before they give you access.

Europe has its own version of this nonsense (GDPR cookie banners), but that stems from a different misguided belief. Europe believes that banners can affect markets. The US believes that banners can affect the law. Both are wrong.

Re: When was the famous "sudo warning" introduced? (2019)

#115

Post by cruffle_duffle »

bowsamic wrote: post #62
VeninVidiaVicii wrote: post #38

Earlier quoted context omitted.

I hate to sound elitist, but I straight-up can’t do any serious coding on anything other than a Linux box. Most of what I do these days is statistical inference on bacterial genomes in the context of antibiotic treatment. I understand that I’m not the average user, but then again, nobody really is.

That sounds like scientific coding, not serious coding

Serious coding like writing TODO apps for the latest WebTV?

Re: When was the famous "sudo warning" introduced? (2019)

#116

Post by vundercind »

reaperducer wrote: post #110
vundercind wrote: post #102

Earlier quoted context omitted.

I used to read an Eastern European world traveler photoblogger who’d been to damn near every country (even a lot that most folks from even semi-developed countries would consider far too dangerous or boring to be worth going out of your way to visit—he’d surely been to at least 150 countries, several more than once) and according to him the specific behavior of posting regulations and signs all over the place is prac…

It's the sort of cultural blindness that comes with not being able to read the native languages in all 150 countries this person's claimed to have visited. Once you're able to read a new language, you see all kinds of new signs, especially when you visit a new country. It's like how people who only read English think of Japan as some kind of blissful artspace, when the reality is that it is far more overloaded with a…

> in all 150 countries this person's claimed to have visited.

They had mountains of boring photos of traffic signs and fire hydrants and bollards and normal people on the street and in other public spaces living their lives and that kind of stuff in lots of countries, so I'm fairly sure they had been to them. :-)

I don't think their take was a result of blindness to languages they don't/didn't know—we really do seem remarkably keen on posting lots of regulations and restrictions at the entrance to every-damn-place, which I've noticed since he pointed it out. Other places may have those restrictions and one may well find a variety of laws and norms enforced in any of several ways in places with less regulation-posting, should one violate them—they're just (I gather—my own limited traveling supports his take, but I've only been to a few other countries) usually not quite as obsessed with posting lots of notices about regulations on every flat surface where strictly-public spaces meet slightly-less-public or private spaces. Since having it pointed out, I've noticed that I'm (when not thinking about it) ignoring a bunch of notices akin to a click-through EULA when just entering stores, and it's not hard for me to believe that lots and lots of places get by just fine, and not necessarily with fewer de jure and de facto restrictions on behavior, with far less posting of notices about those restrictions. Clearly it's not terribly necessary since I'm pretty sure most of us hardly pay any attention to it.

Re: When was the famous "sudo warning" introduced? (2019)

#117

Post by e145bc455f1 »

xorcist wrote: post #73
RulerOf wrote: post #63

Earlier quoted context omitted.

I read a good chunk of that wiki link, but didn't really come away with an understanding of how it differs from just using Docker for sandboxing an app. Did you have any insight there you might share?

It differs by not being insane. Trivial functionality that actually works. It's what's good about systemd. It doesn't require forwarding sockets or giving free access to root just for building images. It doesn't explode just because you touch your nftables rules. It doesn't suddenly expose a process to the Internet because of some undocumented option. You can use all the normal tools such as auditd and SELinux withou…

How is it different from podman then?

Re: When was the famous "sudo warning" introduced? (2019)

#118

Post by bigstrat2003 »

aerzen wrote: post #105
TheSpiceIsLife wrote: post #50

Earlier quoted context omitted.

Other way round for me

What kind of sysadmins are they then? I don't want to sound dismissive, but is a "windows sysadmins" a thing? Do companies run windows on servers?

Companies absolutely run Windows servers. In fact, every single company I've ever worked for (except one very small company) has had them. Usually at a minimum, you will have servers running Active Directory, and perhaps DNS (because AD-integrated DNS zones are useful). Then, more often than not companies are MS Exchange shops, plus Sharepoint is common enough.

Generally people aren't running web servers on Windows, but the internal IT infrastructure world uses a ton of Windows servers.

Re: When was the famous "sudo warning" introduced? (2019)

#119

Post by smitelli »

vasco wrote: post #79
horeszko wrote: post #28

Earlier quoted context omitted.

My networking instructor still suggests this today when configuring the login for routers and switches

It's as useful as people that say they are not lawyers when commenting online.

My views and opinions are, in fact, those of my employer.

Re: When was the famous "sudo warning" introduced? (2019)

#120

Post by cruffle_duffle »

wtallis wrote: post #33
weitendorf wrote: post #24

Earlier quoted context omitted.

These days if the device is expected to be ~always internet-connected (increasingly a safe bet) it probably makes more sense for both the developers and users to handle multiple users with a remote identity provider (email, individual account for the particular service, etc.) rather than implementing identity per-device. I'm pretty sure gaming consoles have had support for this for a long time (at least since xbox 36…

Remote identity only works well when paired with cloud storage; otherwise, you have a recipe for confusion. It works for game consoles because the scope of what needs to be stored in the cloud per-user is reasonably limited. It is problematic for PCs because the remote identity service is free but the free tiers of OneDrive, iCloud, etc. are too limited to actually hold all of the user's data, and it's hard to clearl…

> It is problematic for PCs because the remote identity service is free but the free tiers of OneDrive, iCloud, etc. are too limited to actually hold all of the user's data

Not just that but bandwidth constraints as well. Especially upload bandwidth. I might have 1Gb/s down but I have only like 40Mb/s up.

Even if I could make the device file system sparse and pull what it needs on demand, that stuff still needs to get uploaded initially. And on many internet connections, depending on the user content, it could be a while before the whole thing makes it into the cloud.

Post reply on HN