zlacker

[return to "IoT hacking and rickrolling my high school district"]
1. jimt12+1C[view] [source] 2021-10-12 23:40:06
>>revico+(OP)
Working in IT/tech for school district is the worst. My experience from many years ago - around 2002, I think:

1. First day on the job, email to boss: "Hey, the computer lab at Springfield High has a ton of known security flaws that are begging to be exploited."

2. Reply, 1 week later: "Sorry, we don't have any money for that. Just keep everything up-and-running."

3. 3 weeks later the computer lab at Springfield High got "hacked". All the computers displayed a popup window that said, "Miss Krabappel is a dyke!" (sorry for the offensive language)

4. Next day, email from boss: "The computer lab at Springfield High was hacked! Figure out how to fix this and make sure it doesn't happen again!"

5. A few days later Miss Krabappel filed to sue the school district. The local newspaper picked up the story.

6. Email from boss, in full panic mode: "I need you to figure out who hacked the computer lab at Springfield High so we can report him to the police!"

7. A week later an independent consulting firm was brought in to help identify the person behind the "hack". I heard they were paid $50K and found nothing. However, the kid got ratted out when he told all his friends. (It wasn't Bart Simpson! ;) )

8. Several weeks later: meeting to discuss working with a consulting firm that's gonna fix all the security issues because the current staff (me and my team) lacks the skills.

9. About 6 months later, I quit.

◧◩
2. acidbu+Bd1[view] [source] 2021-10-13 06:17:11
>>jimt12+1C
I 'worked' for my own high school's IT dept, a few hours a week, as a student. It was an amazing experience working with those guys. I learned so many things, from how to punch, terminate, and run cables to how to set up a Ghost image and deploy it en masse across the district.

One day one of the old macs was showing the frowny face in a in-session classroom. Boss sent me down there with specific instructions: "pull out the hard drive and beat it really hard with the handle of this screwdriver". I was like: "?" and he was like, "just do it".

So I go down there and let myself in, trying not to interrupt the class. I climb behind the computer on a cart and pull out the HD. I beat it with the handle, like a good 10 times. Of course this got the class all riled up. I blushed, but told them this was normal operating procedure. Plug it back in and it works. I was (secretly) as amazed as everyone else in the class.

Back in the IT office, I say it worked. IT boss smiles and nods. I ask how. Well as it turns out some of those old hard drives used a vegetable oil based lube that seizes up if it's not used for a while. So if you bash it it un-seizes and starts turning again.

Anyway great times, fun memories. We all got our CompTIA A+ certifications at the end, but don't ask me what IRQ number is for the parallel port these days.

◧◩◪
3. shwoop+jb2[view] [source] 2021-10-13 14:25:28
>>acidbu+Bd1
I believe the term for this is ‘percussive maintenance’
◧◩◪◨
4. nemosa+Us3[view] [source] 2021-10-13 20:42:27
>>shwoop+jb2
In the Navy, we called it “mechanical agitation” it raised fewer eyebrows than “I hit it with a wrench and it started working again.”
[go to top]