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

91–100 of 180 posts

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

#91

Post by close04 »

freedomben wrote: post #89
furyofantares wrote: post #86

Earlier quoted context omitted.

As a kid I saw a sign going into the bathroom at Sears that said "prohibited behavior not allowed". I had to ask my mom what prohibited meant and was quite surprised when she explained that it means "not allowed".

Love it! I've seen a lot of signs like, "prohibited items are not allowed in facility." Especially TSA signs at the airport which also include guns and knives and such in big red circles with lines through them. I always wonder if those signs were made by a brilliant low-grade troll or not. I once added text that said, "Unauthorized access is not authorized" as a low-grade troll, and people liked it so it stayed

You can think of “Prohibited items” as a variable which happens to be called like that for clarity. It’s a clearly defined arbitrary list and it’s referred as such in any relevant text. The prohibition starts at an arbitrary point in the building so they reference the variable when communicating this to you.

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

#92

Post by Algent »

ggm wrote: post #16

Back 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…

This is like the warning in emails about "not reading it if you aren't supposed to have received it" like yeah sure how do you know it's not for you then.

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

#93

Post by ksymph »

ggm wrote: post #16

Back 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…

For anyone else who hasn't heard it before, a bush lawyer is "One who is not qualified in law yet attempts to expound on legal matters."

https://en.m.wiktionary.org/wiki/bush_lawyer

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

#95

Post by ochrist »

kawsper wrote: post #75

It's interesting how messages gets their own life. I was building a user-impersonation system, and it allowed a power-admin to login as another user to change their settings and to help them. When you signed in as the user it said: > You are now signed in as User\##{user_id}, behave nicely ;-) and when you switched back to your admin it said: > You are now signed back in as Admin\##{admin_id}, wreak havoc! ;-) I met…

Oh. It sounds like you were The Bastard Operator From Hell: https://en.wikipedia.org/wiki/Bastard_Operator_From_Hell

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

#96

Post by IgorPartola »

VeninVidiaVicii wrote: post #38
Daneel_ wrote: post #27

Earlier quoted context omitted.

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.

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.

It’s because you are a Linux noob. Use a real Unix like macOS! /s

Let the flamewars begin!

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

#97

Post by ricktdotorg »

ksymph wrote: post #93
ggm wrote: post #16

Back 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…

For anyone else who hasn't heard it before, a bush lawyer is "One who is not qualified in law yet attempts to expound on legal matters." https://en.m.wiktionary.org/wiki/bush_lawyer

thankfully the negative use of bush in the context of "bush lawyer" does not extend into the use of bush in "bush pilot"

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

#98

Post by BenjiWiebe »

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 vaguely remember having issues with it at one point - I wonder if having a non-NOPASSWD group setting overrides a NOPASSWD user setting?

Maybe make sure there's only a single sudoers entry that applies to your user, and that single entry is NOPASSWD.

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

#99

Post by ricktdotorg »

unit149 wrote: post #76
tonymet wrote: post #49

Pretty wild that sudo is still the most common authorization framework for linux.

Sudo will temporarily get you in su, whereas the cu command calls another user within the original shell. Designating kernel privileges within an instantiation works in the absence of a w-r permissions setting scheme for designating cron tasks + programs.

s/cu /su /g

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

#100

Post by BenjiWiebe »

deadbunny wrote: post #82
perbu wrote: post #52

sudo also had the ominous warning, "This incident will be reported!" when you fail to authorize the request. ofc, it just just logged.

I remember my first linux admin gig and mistyping my password when using sudo then getting an email about it a few seconds later. After years of home linux use this amused me and was like "oh, so that's what happens when things are configured properly".

It mails the root user by default.
Post reply on HN