Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Remove “This incident will be reported.” from user warnings

github.com

Post reply on HN
Print view View original

191–200 of 302 posts

Re: Remove “This incident will be reported.” from user warnings

#191

Post by antognini »

hoodmane wrote: post #77
Buttons840 wrote: post #46

Can 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.

Yes. More or less the first time I used Linux was on a fedora workstation at my desk at MIT. The very nice sysadmin down the hall sent me an email just a bit later saying "We see you were trying to install x program. We installed it for you." I understand that this is a very rare experience but the first time I saw that message, a helpful person was actually looking at these reports.

It sounds like you were able to successfully run sudo, just with a somewhat longer latency.

Re: Remove “This incident will be reported.” from user warnings

#192

Post by JasonFruit »

urbandw311er wrote: post #166
pram wrote: post #12

I was always disappointed it never summoned some grumpy graybeard unix admin from a dark server room basement to give me a chiding lecture.

Can’t believe nobody has reposted this yet: https://xkcd.com/838

I just assumed they went to Ken Thompson directly.

Re: Remove “This incident will be reported.” from user warnings

#194

Post by noisy_boy »

ww520 wrote: post #143
stilley2 wrote: post #132

Earlier quoted context omitted.

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.

I remember that one of the financial banking software we were using had an internal chat that was basically using "write"(?) underneath to send messages to another users terminal (it was running on Sun Solaris I think).

Re: Remove “This incident will be reported.” from user warnings

#195

Post by NoZebra120vClip »

judge2020 wrote: post #189
Aeolun wrote: post #183

Earlier quoted context omitted.

So did you have root access? I can’t figure out if you attempt to su all the system accounts worked or not.

Nowadays /etc/passwd is world-readable and passwords are in /etc/shadow but perhaps /etc/passwd used to store the hashed passwords as well.

I, of course, did not have root access or any access that I shouldn't have had.

/etc/passwd indeed stored the hashes in SVR3, and there was no such thing as /etc/shadow. I was naive enough not to understand hashes, and so I figured that those jumbled letters in the file had to be the actual passwords, and if "*" was in an entry then "*" was, of course, the password! Why didn't it work?!!?

Re: Remove “This incident will be reported.” from user warnings

#196

Post by lakomen »

themodelplumber wrote: post #49
pram wrote: post #12

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 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…

I miss those times, thanks for reminding

Re: Remove “This incident will be reported.” from user warnings

#198

Post by ww520 »

gwerbret wrote: post #187
ww520 wrote: post #181

Earlier quoted context omitted.

The one program truly blew my mind at the time was Netrek - the first networked multi-player realtime graphical space fighting game. I've wasted so much time late into the nights playing the game in the lab instead of doing coursework. The admin came to the lab from time to time and said we're hogging the workstations with the game and banned the game during daytime.

> The one program truly blew my mind at the time was Netrek - the first networked multi-player realtime graphical space fighting game. Anything like mtrek? It's still around [0], and even over telnet [1]. 0: https://mtrek.com 1: telnet://mtrek.com:1701

It's a fast paced multi-player space battle game with a top down graphic 2D view. It's like Command and Conquer, with each unit controlled by a different player.

https://www.youtube.com/watch?v=bQkDhwo7qNQ

Re: Remove “This incident will be reported.” from user warnings

#199

Post by notatoad »

ww520 wrote: post #184
NoZebra120vClip wrote: post #172

Alright, did I tell my college sysadmin story already? This is the perfect place to drop it. 1990, freshman in college, Pascal class on AT&T Unix SVR3 3B2 cluster named "earth", "wind", and "fire". We'd just learned our way around "vi" and how to "uvapc" our Pascal source into a.out. I discovered anonymous ftp, and "make", and I quickly rose to become the gaming king of Pascal class. I had ularn, nethack, megs and me…

Schools are supposed to be the place where students can break things and break rules. It's part of the education.

learning that if you get caught you're going to be held accountable for your actions is also part of the education.

it's not as if they executed OP. telling a kid to stop screwing around is pretty reasonable.

Re: Remove “This incident will be reported.” from user warnings

#200

Post by kragen »

Gigachad wrote: post #177
TaylorAlexander wrote: post #71

Earlier quoted context omitted.

Reminds me of when I was younger and my mom and my brother were using a windows computer. They got the message “an illegal error has occurred” and my mom called me to ask if they had broken the law.

I almost shit myself the first time I saw X Screensaver.. It has to take the prize for worst UX ever.

do you mean the bsod screensaver

sometimes people also complain about xscreensaver's lock screen because it doesn't use a widget library, but the alternative lock screens can often be crashed through bugs in the widget libraries they use

Post reply on HN