A “Texas man” named “Lu”.
Someone did that at Cisco. As far as I heard, the company never admitted what happened. Took down their conferencing system and messaging systems. Took them a month or so to get their customers fully back online.
Most guys I have met from Texas spell their name Lou differently. And that is usually the first name, not the last.
Eventually, someone should hire this guy for something good. He definitely has talent.
Early probation or parole where he has to work to protect America.
Hence why the swamp is so desperate to get fired bureaucrats back in to their office. Even if it is just for a few weeks they can do tremendous damage.
hang`em high. screwing everybody is not the right way to accept the hand you are dealt.
I never understood why people expect that a particular place of employment is a lifetime commitment. Presumably he got paid for his time there - no need for malice and sabotage.
How about be thankful for the opportunity that was given you rather than bitter about it ending?
There’s a reason why most IT people are escorted out the building when they put their two week notice in.
Not saying you SHOULD do something like this of course, but if you were, the worst thing you could do is set it too trigger as soon as you are fired. You’ll automatically be suspect #1. The correct way to go about would be to set some sort of virus that would kick in say six months down the road, by that time you’ll be totally forgotten by the company.
I left the USS Dwight D Eisenhower when it was in the shipyard (about 1987). There was a welded down file cabinet in my division office with enough space for me to place a raw egg under the bottom drawer. I’m sure that it remained there intact until the ship finally moved. Not sure how they got rid of the smell.
The loss of work time for all employees affected, translated to idle manpower costs, would have to be exponentially greater than the $5,000 in damages.
I designed an OLTP system in 1992 that was FAR above what my coworkers understood. I spent the next 5 years working on it, and teaching others how it worked, but when I left in ‘97 they started bubble gum and toe-nailing things together. I got a refresher on how things were running a few years ago, and it was BADLY bastardized in ways that made things barely work, and that were against my original design. So, I guess I unintentionally did the same thing as this guy, just with knowledge instead of a logic bomb.
When I retired, it activated a kill switch. Our report server ran its jobs under my userid which was de-activated. I could not change it to another person without their password. It was on someone’s list to do.
.
With *NIX, simple enough to do, even without access to a personnel database.
There are lots of one-line commands that will crash the OS. Some also will corrupt all the data in the doing. They teach some of these to junior admins so they know what NOT to do.
So create a daily cron job as the trigger. It tests whether File X has been ‘touched’ in the last 30 days. If the file hasn’t been touched in 30 days, invoke the corruption routine.
First thing every morning on reporting to work, open File X to reset its ‘last touched’ date. If you don’t come to work for 30 days, the cron job takes for granted you want the place burned down and has at it.
Maybe he got moved around cause he was smart, but had a lousy attitude...
Don’t Windows “updates” and enhancements do the same kind of things to our computers?
Its been done: https://www.computerworld.com/article/1353402/computer-saboteur-sentenced-to-federal-prison.html