Live data from Hacker News

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

github.com

181–190 of 302 posts

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

#181
post #143

Earlier quoted context omitted.

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.

That was such a mind blowing experience coming from a DOS background. It would split your terminal horizontally and you could see each other type in real time. Before the days of SMS, and even before the days of instant messengers like ICQ and AIM, I taught the split-screen `talk` command to my girlfriend so we could chat while I was working. We've been married for 20 years now.

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.

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

#182

Earlier quoted context omitted.

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.

OMFG. The currently-active BYU LUG hosts their site on motherfucking Facebook. How the mighty have fallen.

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

#183

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…

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

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

#184

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.

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

#185
post #139

Earlier quoted context omitted.

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?

So we all are ;)

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

#187
post #181

Earlier quoted context omitted.

That was such a mind blowing experience coming from a DOS background. It would split your terminal horizontally and you could see each other type in real time. Before the days of SMS, and even before the days of instant messengers like ICQ and AIM, I taught the split-screen `talk` command to my girlfriend so we could chat while I was working. We've been married for 20 years now.

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

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

#188

Earlier quoted context omitted.

Checking if the alarm is set by seeing if it activates seems like it's not particularly useful.

Not to comment on this particular case, but this is a more useful tactic than it seems at first. Seeing the reaction that an alarm brings can provide lots of useful information for evading future ones.

For some alarms yes. But for one where you won't even know if it activated unless you see the response, and there's little reason for anyone to care about it most of the time... it seems pretty niche.

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

#189
post #183

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…

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.
Post reply on HN