Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Yeah, I kind of lament them removing this warning if I'm going to be honest. It feels like something such as that should be more common best practice.

Of course decent log collection/monitoring should also be able to catch authlog stuff and alert accordingly and I'm sure most organizations rely on solutions like that instead of letting things get lost in email



It's only removed if sudo doesn't send mail. It still warns if it's relevant.


This is correct, and was added back a few weeks later in https://github.com/sudo-project/sudo/commit/9757d29a24ac1872...


Isn't it leaking detail about internal policy about whether incorrect sudoing is getting reported or not though?


This is a pretty short diff and it clearly does NOT do that, unless you're saying they went back later in another commit to add this. They removed the message in all situations. The string "This incident will be reported" has been removed from the source code; it could not possibly print that message now.



Is there more to the change than the linked commit? Because if not, looking at the code change I don't see how you could possibly be correct. There is no additional logic/branching that could be checking whether sudo sends mail or not, just a string change.


It was added back in a later commit but only prints if the mail is configured.


Nice, thanks that's very useful info


This doesn't seem to be correct.


I feel like that warning comes right out of the era of multi-user machines with unprivileged shell accounts. That era is largely gone. Today, someone, possibly a less knowledgeable user, runs sudo on their single user laptop that they completely own outright, and may get confused who they're being "reported" to.


Funny if you live in a free country

Potentially terrifying if you don't


To themselves of course. That's pretty clear.

But there is a renewed focus on corporate laptops to remove admin rights on windows. Not really because the user is not being trusted, but because malware has a lot more options for bypassing EDR/antimalware and persistence when it runs with admin rights.

I'm sure this will come to Linux too at some point.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: