That's pretty funny. I worked at a unix shop and occasionally got a kick out of things like the following, if I ever saw one of my buddies logged in at the same time as me:
echo 'Terminal overheating, please blow on screen' > /dev/tty0
Saying “sup” with `net send`
21–30 of 144 posts
Re: Saying “sup” with `net send`
#22I had fun with fork bombs on the VAX/VMS machine at uni. Till the day it ran too quickly for me to stop it. Walk of shame to the CSO to own up and for them to terminate the run-away processes on the Sysop console.
Re: Saying “sup” with `net send`
#23we used to do similar with the Mac's ability to speak using the command 'say'. we'd ssh into a computer we knew someone to be sitting and have it 'say' something while using their name. at least, until one day, the 'say' app was not longer available!
Us too. And if the sound was off, we could just turn up the volume with `osascript` commands!
Re: Saying “sup” with `net send`
#24I don't quite recall how I did it but I have a similar story of ejecting disc trays across my HS and school district. something with novell iirc
Re: Saying “sup” with `net send`
#25Heh. If you used the underlying windows api calls, you could spoof the sender. Something I discovered when I did just that, in the Windows 2000 days. Combine it with a for loop and you could generously message everyone on the LAN with little effort. There's a reason why everyone around me turned off the net service after a while...
I did something like this, also on Windows 2000, when I was in high school. It definitely surprised some teachers....
I also discovered that our student IDs and PINs were based on our birthdays, though I was not creative enough to come up with an amusing use of student logins.
Re: Saying “sup” with `net send`
#26I was worried for them, glad it worked out. I wouldn't be so sure about this statement: "now that I’m a grownup I know that [...] we wouldn’t have gotten in very much trouble anyway."
Unfortunately this was the type of thing that would get students banned from the computers, or only allowed to actually use the computers on Friday to do their computer science work (like my friend Dave).
Speaking of NET SEND specifically, I went to a vendor for training once (circa 2000) and they mentioned someone who had recently come for training and was sent home because they had used NET SEND * there. I wonder what their employer thought of that.
Either me or a friend has at some point (in the 80s or 90s as minor students) been: kicked out of computer lab, had notes posted in the library that we are not to "hone our programming skills", kicked out of the Supercomputer Challenge[1], been told (second-hand) we're "a security risk" by the government, been put specifically under remote monitoring by the teacher, lectured, sent to the principle, had the police sent to their house, been told we "probably have an FBI record" and "are putting their parents' jobs at risk" over similar levels of playing around with computers that they let us use, not even trying to do anything particularly "hacker (cracker)"-like.
[1] https://supercomputingchallenge.org/22-23/index.php (Not this specific year obviously. More like 30 years ago.)
Re: Saying “sup” with `net send`
#27Had 3.5 weeks of excel classes in school, completed everything in 2 days and spent the rest of the time playing quake or annoying the ones not finished with net send in loops. Now that I think about I'm not sure this classroom of computers were on their own broadcast network or not, but they were running an older version of windows that didn't block net send by default while others had a newer version.
Re: Saying “sup” with `net send`
#28Same series of events happened at my school.
1. Discover net send
2. Discover net send *
3. Get in trouble for using net send *
The next step was discovering telnet and the schools smtp server.
Re: Saying “sup” with `net send`
#29This brings back memories.
My favorite discovery was that the "scheduled tasks" folder was shared on every computer in our school. This meant you could do the net send * bomb from a friend / enemies computer, and get them in trouble.
The other fun one was Borland C++ 6 had a limit on how wide the code window could be -- you could only horizontally scroll so far. However, you could hold down tab for a few seconds, then write something like cout<<"logout next time"; in their code. Unless you knew the trick, you'd never find the code afterwards -- you couldn't scroll to the right far enough due to the limitation of the viewing window.
Re: Saying “sup” with `net send`
#30Same series of events happened at my school. 1. Discover net send 2. Discover net send * 3. Get in trouble for using net send * The next step was discovering telnet and the schools smtp server.
Same here. However we discovered that the windows service "messenger" had to be re-enabled on the target machine to make this work again. So we'd sneak into a gullible person's computer, log in (each one of us was an admin, yay!), run "net start messenger" and were back in action!