Earlier quoted context omitted.
That seems pretty stupid. While they're at it, why not update the SSH warning banner with a list of what we do and don't log on this system. As a courtesy to their adversary. This sudo message has been the same since the dawn of time. There is literally no reason to correct it. This is the one place you don't want to be pedantic, leaking security configuration via stderr.
something like 99% of computers with sudo installed are single-user machines where the only effect of the warning is to scare people and it's only been the same since people started to switch to sudo in the late 90s; su never printed such a warning
Remove “This incident will be reported.” from user warnings
71–80 of 302 posts
Re: Remove “This incident will be reported.” from user warnings
#72Thank goodness. That was a terrible message. I remember my very first experience with unix was setting up Red Hat 3.0.3[1] at work for a small internet company in like 1997 and getting that message and just not knowing what on earth to do. There was noone in my company who could help me and all I had was a unix book from my local library which didn't even cover linux (but I sort of thought it would be helpful). [1] W…
"This incident will be logged" may have been better.
Re: Remove “This incident will be reported.” from user warnings
#73Can someone share even one story where sudo reporting these "incidents" was helpful? This feature seems to come from a world where elite hackers simply repeat the same sudo command over and over hoping it will eventually work.
> Can someone share even one story where sudo reporting these "incidents" was helpful? No, not a single one.
Re: Remove “This incident will be reported.” from user warnings
#74For those wondering where the reports go, under systemd-based linux distributions ideally you can get them with this: sudo journalctl /bin/sudo Historically speaking however the sysadmin with access to the 'mail' command would be able to run that and see mail delivered to root@localhost for these reports. I think at least OpenBSD still does things this way [1], but they moved away from sudo YEARS ago now [2] [1] http…
Or you set up your system so mail for root gets redirected to an smtp server with an actual inbox read by actual people
Re: Remove “This incident will be reported.” from user warnings
#75Re: Remove “This incident will be reported.” from user warnings
#76Yes, it's important that things be clear. Hopefully we do something about man pages next, they are way too obfuscated.
Re: Remove “This incident will be reported.” from user warnings
#77Can someone share even one story where sudo reporting these "incidents" was helpful? This feature seems to come from a world where elite hackers simply repeat the same sudo command over and over hoping it will eventually work.
Re: Remove “This incident will be reported.” from user warnings
#78Earlier quoted context omitted.
That seems pretty stupid. While they're at it, why not update the SSH warning banner with a list of what we do and don't log on this system. As a courtesy to their adversary. This sudo message has been the same since the dawn of time. There is literally no reason to correct it. This is the one place you don't want to be pedantic, leaking security configuration via stderr.
something like 99% of computers with sudo installed are single-user machines where the only effect of the warning is to scare people and it's only been the same since people started to switch to sudo in the late 90s; su never printed such a warning
Re: Remove “This incident will be reported.” from user warnings
#79Re: Remove “This incident will be reported.” from user warnings
#80So according to the comments it isn't actually gone, just the wording updated and now dependent on if you have actually set up the mailer to report it somewhere https://github.com/sudo-project/sudo/commit/9757d29a24ac1872...
That seems pretty stupid. While they're at it, why not update the SSH warning banner with a list of what we do and don't log on this system. As a courtesy to their adversary. This sudo message has been the same since the dawn of time. There is literally no reason to correct it. This is the one place you don't want to be pedantic, leaking security configuration via stderr.