Social media communities really ought to observe a "leave no trace" rule with respect to GitHub and other such spaces. This commit from February 2022 is now as of today littered with a bunch of joke comments from being linked from here and previously somewhere else earlier (based on timestamps).
Remove “This incident will be reported.” from user warnings
141–150 of 302 posts
Re: Remove “This incident will be reported.” from user warnings
#142Social media communities really ought to observe a "leave no trace" rule with respect to GitHub and other such spaces. This commit from February 2022 is now as of today littered with a bunch of joke comments from being linked from here and previously somewhere else earlier (based on timestamps).
> Social media communities really ought to observe a [...] rule
Oh honey....
Re: Remove “This incident will be reported.” from user warnings
#143Funny story. When I was in grad school, the math department office I was in had Linux computers administrated by the department. One day I was goofing in my shared office with a fellow grad student by playing with what resources were available. We were trying sudo and failed with enough silly passwords that we got the "this incident will be reported" message. I confidently told my officemate that these messages were…
I once entered 'sudo echo hi" or something similar on a large HPCC and received an email back from a sysadmin that just said "hello".
There's the talk command on Unix. We used to do a 'who' to find out who're on the system and 'talk' to them.
Re: Remove “This incident will be reported.” from user warnings
#144I was always disappointed it never summoned some grumpy graybeard unix admin from a dark server room basement to give me a chiding lecture.
I got a chiding lecture like that from some skinny UUG-type security admins, by manually shutting down my HP-UX workstation in a university CS lab. I had reached behind it and flipped the power switch. I tried to flip it back on just afterward, to resume my business (lol) but found that my login was blocked with a message...come up to security in room 300-something and talk to us to get your account un-suspended. The…
What does UUG stand for? That's the only acronym that ChatGPT didn't give me a guess for from your comment.
The other guesses were: CDE - Common Desktop Environment, MTC - Missionary Training Center.
GPT is much better than web search for this, I'll say that. It's ability to use context is invaluable.
Re: Remove “This incident will be reported.” from user warnings
#145I was always disappointed it never summoned some grumpy graybeard unix admin from a dark server room basement to give me a chiding lecture.
I would have taken the opportunity to ask them a few questions.
But that’s probably why they don’t come out to lecture.
Re: Remove “This incident will be reported.” from user warnings
#146Earlier quoted context omitted.
I got a chiding lecture like that from some skinny UUG-type security admins, by manually shutting down my HP-UX workstation in a university CS lab. I had reached behind it and flipped the power switch. I tried to flip it back on just afterward, to resume my business (lol) but found that my login was blocked with a message...come up to security in room 300-something and talk to us to get your account un-suspended. The…
What does UUG stand for? That's the only acronym that ChatGPT didn't give me a guess for from your comment. The other guesses were: CDE - Common Desktop Environment, MTC - Missionary Training Center. GPT is much better than web search for this, I'll say that. It's ability to use context is invaluable.
https://www.facebook.com/groups/byu.uug/
This user group was already in place by the time Linux came along, so you had the UUG doing Red Hat boxed set giveaways and such. There was a ton of excitement about Linux and not as much about Unix at that point. Then a bit more proper-Unix excitement when OS X came out.
The other ones are correct.
Re: Remove “This incident will be reported.” from user warnings
#147For 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…
I haven't used journalctl in a while - do you mind explaining how it works with a binary path? Does it report all system logging that came from that executable, as if it were a service file?
The systemd journal logs not only raw strings and priorities (like legacy syslog), but a large number of metadata fields for each message. One of these fields is the name of the executable which generated the message. The command
journalctl /bin/su
journalctl _EXE=/bin/su
Re: Remove “This incident will be reported.” from user warnings
#148Funny story. When I was in grad school, the math department office I was in had Linux computers administrated by the department. One day I was goofing in my shared office with a fellow grad student by playing with what resources were available. We were trying sudo and failed with enough silly passwords that we got the "this incident will be reported" message. I confidently told my officemate that these messages were…
Speaking of interaction with the admin. Back in the days when I was in school, the computer lab ran a Honeywell mainframe with terminals. I wrote a program emulating the logon screen to intercept the username and password of the unsuspecting students logging on and to email them to me. I was going to post the list of all the usernames and passwords at the end of the semester on the wall. I dubbed it the Fishing proje…
That’s quite similar to my story. While at high school, I wrote an innocent program to open the terminals at the nearby college for chat sessions - nothing nefarious. The sysadm saw what I did and realised I could use it to phish passwords. Next time I went to use the computer lab, the terminals were locked down.
Showing my age but this would have been 1984 or so… a remarkably early contribution to security?
Re: Remove “This incident will be reported.” from user warnings
#149Next step is to remove users/groups/sudo from Linux/UNIX entirely. I'm one person using the computer, running software I trust. I don't need it.
I suspect if you look in your passwd file you’ll find lots of users. Does nginx really need to read the files in your home directory?
Very few computers running nginx have human user accounts with more than dotfiles in the home directory. Meanwhile desktops run everything on the same account because defining usable security policies between users is basically impossible.