41–50 of 302 posts
> Could not grab your mouse.
> A malicious client may be eavesdropping on your session or you may have just clicked a menu or some application just decided to get focus.
> Try again.
> [Close]
Earlier quoted context omitted.
It's only removed if sudo doesn't send mail. It still warns if it's relevant.
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.
Earlier quoted context omitted.
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.
Earlier quoted context omitted.
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
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.
Potentially terrifying if you don't
I remember the first time to have this message was at my first time using CERN lxplus during my undergrad. I was worried that people will think I am stupid to try "sudo apt-get" there. It was a mistake as I had several terminal sessions and forgot which one was the local. Anyway fast forward today. I know the answer to the question to whom usually this notification gets sent. They forward it via SMTP server to the pe…
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.
I was always disappointed it never summoned some grumpy graybeard unix admin from a dark server room basement to give me a chiding lecture.
I receive mails from sudo incidents generated by my users, I check the boxes except the gray beard.
Earlier quoted context omitted.
Or you set up your system so mail for root gets redirected to an smtp server with an actual inbox read by actual people
Completely this, I was so confused by OP because naturally this is how my playbooks configure my systems.
In other words, don't think well-configured ansible playbooks are most people's first exposure to linux although it does sound like you're doing things right which is nice to hear
I was always disappointed it never summoned some grumpy graybeard unix admin from a dark server room basement to give me a chiding lecture.
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 issue leading to the frantic shutdown goes as follows:
I had been browsing some of JWZ's online journals in Netscape...the old about:jwz trick.
Within those pages, there's a linked audio clip of the fake *rgasm scene from "When Harry Met Sally".
I clicked on the link not realizing what would happen, and of course this passionate audio clip played at more or less full volume to a computer lab full of university students from China.
(They were extremely "I didn't notice that" about the whole thing, but I was beet red and frantically scanning the room for anyone who I could possibly nervously laugh with...)
Back then Netscape didn't show any audio controls that I could find anywhere when clips like that played, which was also a really frustrating part of this. I guess it just handed off the audio to some process which I could have found via `top` if I had the time.
There was also an internal speaker, nothing with a manual volume control. Great!
Anyway, I went upstairs, got my lecture about other people who could have had sessions terminated while working on the same workstation, got the login back, and fortunately none of the Chinese students seemed to have let my er..._BYU_ CS security admins...know about the situation in the lab. lol.
(No longer a practicing Mormon; still think CDE is cool)
Edit: Just for the memories...at the same time, I had a PT job doing university IT support on a Novell network, and we supported, among other places (the MTC, the laundry, Creamery--PHEW those amazing chocolate malt shakes--but not so phew the time the creamery's huge 1K+ gal. milk vats leaked and there was a foot of standing milk in our PCs there, etc.), the married student housing computer labs.
Colloquially labeled by my boss and others as the "rabbit hutches"...
This was still pretty early days for the web, and I remember periodically getting frantic voicemails from newly-married folks.
A common version of the voice message would be something like, "Hi, uh...I was in the married student housing lab...trying to book airline tickets for my husband to fly home and see his mom...anyway (tearful quivering voice starts)...russian porn came up I guess? I mean I am just guessing...uh, so anyway...(crying harder, phew)...the lab assistant gave me your number, and here's my number, if we need to talk about this or anything, call me I guess?"
I can't imagine what those students must have felt when the lab assistant just shrugged their shoulders regarding "what to do about this" and gave them somebody's office number to call. Up the chain with you!
Gestapo-level perceptions would always tend to kick in at that point...and you had to maintain an ecclesiastical endorsement to continue studies there, so this was a pretty big deal. Anything involving porn was always at the potentially-terminate-your-entire-university-experience level.
(Often the calls to those labs were pretty funny though. Like a toddler put a dorito inside of a CD-ROM drive, bring your hemostat, things like that. Afterward we'd get a Jamba Juice, or get a free cafeteria meal from a really nice food-services manager, chat about Everquest, etc.)