Einhander Sn0m4n wrote:I did several things I found in Schoolstoppers Handbook (search the forum, I posted my 'improved' version in HoS). Phucking with the computers is phunny, although using viruses it generally a Bad Idea™. Just ask Teekid...
HAHA, you should see some of the shit my friends and I did back a couple years ago... Totally harmless really, but funny, though it had the IT bunch shitting their pants and spending a week figuring out how the hell to fix the problem, and they knew who did it, just I was not too co-operative, and neither was the prof involved in it.
Let's see, the long list: (just so you all know, I have been "retired" from my hobby for about 3 years now)
Making $50 off of a bet with the WinNT server prof who claimed his NT/98 dualboot was perfectly secure, and that even if I could get into it, it would take me more than 5 minutes... Let's see: floppy disk with an NTFS emulator and a password file decryption proggie... Went in, located the administrator password file, changed the password, restarted and logged into NT as if I owned it. He lost $50 to it, and I had not had the $50 to pay him if I had not gotten in. (of course if you have already done it like a dozen times that week, you are not too worried)
Changing the entire color scheme of Win2K pro in the Cisco networking lab to totally black on black, they had to reload the systems because they were too stupid to realize they could fix it by feel alone, like I could. (they should have realized this when it was only my system on the end which would work every day, whereas the others were "dead", and after the class, mine would be "dead" as well.)
Taking a screenshot of the desktop of said Win2K machines, setting it as background, and then turning off icons in display properties... This tripped up more than a few of the average idiot (ab)users in that class, and about 90% of the IT department. Several of these were reloaded because the idiots didn't know how to administrate their computers.
Router loop in the 5 Cisco routers in the room, these were configured exactly like the network used in the Cisco curriculum. A to B, B to C, C to D, D to E, E to A... This could have been fixed almost instantly by disconnecting ONE router, granted I had locked out console on ALL of them. They started their diagnostics by dismantling the classroom's network architecture, long before they even *thought* the problem was in the routers... The first clue should have been when the server and console comps could not be used to access the routers, and the tracert and ping commands gave back erroneous responces... *snicker* What a bunch of idiots, I loved fucking with the minds of those ITs, all 200+ of'em. (btw, the Cisco curriculum was written by a roomfull of crack-baited monkeys on typewriters, and that's on a good day)
Leeched the entire A+ course data off of the main server with my laptop.
Several hundred hours of gameplay in a locked lab, which was supposed to be open.
Password protected dedicated Quake 2 server on the main faculty server, they couldn't get rid of it until they rebooted the server, which at that time was not possible since it would have taken down the WHOLE faculty network.
Batchfile "virus" in the faculty e-mail server after I was fired from the IT department (long story, I was actually not fired because of my antics, but because of politics, and we wonder why I went to war with the admins in the school, since they did slander me rather badly in this process), which was set up to flood all the e-mail boxes of all the faculty members on that server with over 20,000 e-mails (read: outlook express going down like a brick instantly on all systems and the server locking up), from what some friends told me, that thing is still there nearly 5 years later, and 2 years after I left that college, which means their e-mail is *still* cocked up. (btw, for those interested in the text contained in the message: "This is what happens when you terminate someone for something they did not do, you reap the consequences of what your corrupt administration has done to me on account of their politics and disregard of their own rules. -PhaZe")
And the number of times I simply leeched the proggies on their servers, used their bandwidth for downloads, or gaming.
Nevermind in JHS that I used to break the Mac network almost daily.
My friends were responsible for scaring a librarian to the point she thought she would have an attempt on her life. (photoshopped picture of her face superimposed on a picture of hitler doing the "heil hitler" pose, which was then put (via use of the IT department's own security/remote admin utility) as desktop on all the comps in the library, and as the background on the campus website.) I still have no idea how they pullt that off. It was hillarious though, since the "silence nazi" thing was a joke specific to that group of people, we always got in trouble for making too much noise in the library computer labs, even if no one was in them, though we never got in trouble for watching DVDs and playing games for hours on end. Luckly I can't take credit for the whole scare thing, but it is hillarious.
I gave my friends some critical knowledge for how to get into the computers that the library installed "DeepFreeze" on, and delete the image file and program so the system could actually take settings again. Nothing like idiot ITs forgetting to turn off "boot from floppy" in bios. 'Nuff said.
Also nothing like said idiot ITs literally trashpactoring tens of thousands of dollars worth of perfectly good, relatively modern computer hardware, including dozens of servers and CD-rack servers. All because they were excess inventory. This is where some of the problems showed up initially btw.
Also, one thing the ITs hated about my friends and I, the 5 of us were doing at least 3/4 of the repair and maintenence work (unpayed) that all roughly 200 of them were supposed to do. The only reason we didn't do more was because we did not have the codes to get into the server rooms, but last I heard one of them did get into a server room finally, by using a decoder on a broken open code-lock, probably one of the designs from my team in the electronics class.
The there's the "railgun incedent", my team in the electronics class constructed a small coilgun based on one of my designs (incedentally a simple sketch on my notes when I got bored of the lecture), on a test fire after we fixed the polarity-switching bug on the end coil, we put a nail thru the blackboard, the cinderblock wall behind, 2 interior walls, and embedded it into the far concrete wall of the building. Maintenence was not thrilled... On the public test of the thing, we used a big elm tree in the courtyard as the target (thinking it would get stuck in the soft, wet wood), in front of several of the higher ups, and the dean of the department (a friend of mine at the time btw) I shot another nail right thru the tree and into the concrete wall of the building about 30 feet away. Grounds was most displeased about having to repair their tree... (btw, by saying "I shot it", I am meaning that I was the one who pushed the button, it was mounted to a wheeled cart due to the computer systems controlling the actuation of the coils.)
Funny thing is, I was well liked at that college by pretty much everyone in power, just not the student "government" or the VP of student services, or the IT department. The battle with the student "government" was my Waterloo btw. However, I look at the, at the time, horrid outcome of that event as being a major turning point in my life, without it, right now I would have had my degree in electronics and would (possibly) be posting this from a ship in the Persian Gulf, as per my plans at the time. Now I am going for a dual major in a university for electrical engineering and CS.
Funny how the worst events in one's life can often be the most important for good things to happen.
