"This incident will be reported" Surely they were thinking at the time that the user was a student.
[deleted]
When was the famous "sudo warning" introduced? (2019)
81–90 of 180 posts
Re: When was the famous "sudo warning" introduced? (2019)
#82sudo 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".
Re: When was the famous "sudo warning" introduced? (2019)
#83It'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…
You infected him with a mind virus. He's going to tell about that message to other people, who will tell about it to others. Before you know it, it's gone viral.
Re: When was the famous "sudo warning" introduced? (2019)
#84Earlier 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…
Have you used containers?
Re: When was the famous "sudo warning" introduced? (2019)
#85Earlier quoted context omitted.
It's a major annoyance. The system knows perfectly well who I am. I shouldn't have to type my password repeatedly to do things the system knows I can do. The threat model no longer reflects the real world.
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
Re: When was the famous "sudo warning" introduced? (2019)
#86Back 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…
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".
Re: When was the famous "sudo warning" introduced? (2019)
#87Earlier 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…
I agree that multi-user should go away for modern server workloads, however, users are used as a blast door. Mainly because Linux's security model is lacking. systemd for example commonly runs services under separate users to make it more difficult for a compromised application to elevate privileges. Android does something similar AFAIK. Users should have never became a security boundary to isolate applications, but…
[deleted]
Re: When was the famous "sudo warning" introduced? (2019)
#88Back 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…
We had a client insist that the SSH prompt be changed to include a half-page rambling about it being an "proprietary system" and "access prohibited for non-authorized users", something like that. Failing to include their specific wording, when we did their new staging setup, was a critical, must fix now bug.
Their argumentation was that it was a regulatory requirement and would allow for prosecution.
Re: When was the famous "sudo warning" introduced? (2019)
#89Back 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…
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
Re: When was the famous "sudo warning" introduced? (2019)
#90FYI, you can turn this off by adding "Defaults lecture = never" to /etc/sudoers. In Nix:
{
security.sudo.extraConfig = ''
Defaults lecture = never
'';
}