Slashdot Mirror


Former Sysadmin Accused of Planting 'Time Bomb' In Company's Database (bleepingcomputer.com)

An anonymous reader writes: Allegro MicroSystems LLC is suing a former IT employee for sabotaging its database using a "time bomb" that deleted crucial financial data in the first week of the new fiscal year. According to court documents, after resigning from his job, a former sysadmin kept one of two laptops. On January 31, Patel entered the grounds of the Allegro headquarters in Worcester, Massachusetts, just enough to be in range of the factory's Wi-Fi network. Allegro says that Patel used the second business-use laptop to connect to the company's network using the credentials of another employee. While connected to the factory's network on January 31, Allegro claims Patel, who was one of the two people in charge of Oracle programming, uploaded a "time bomb" to the company's Oracle finance module. The code was designed to execute a few months later, on April 1, 2016, the first week of the new fiscal year, and was meant to "copy certain headers or pointers to data into a separate database table and then to purge those headers from the finance module, thereby rendering the data in the module worthless." The company says that "defendant Patel knew that his sabotage of the finance module on the first week of the new fiscal year had the maximum potential to cause Allegro to suffer damages because it would prevent Allegro from completing the prior year's fiscal year-end accounting reconciliation and financial reports."

143 comments

  1. Backup, anyone? by Anonymous Coward · · Score: 3, Insightful

    Seriously, why would it even be an issue? Critical code and data, but not backed up?

    1. Re:Backup, anyone? by Anonymous Coward · · Score: 5, Insightful

      You think a malicious sysadmin wouldn't know to target the backups as well?

    2. Re:Backup, anyone? by roc97007 · · Score: 2

      Or at least, have the code delete itself.

      --
      Oliver's law of assumed responsibility: If you're seen fixing it, you will be blamed for breaking it.
    3. Re:Backup, anyone? by dougTheRug · · Score: 1

      It took them two weeks to find it - after which the damage seemed to have been done.

    4. Re:Backup, anyone? by TechyImmigrant · · Score: 2

      A good sysadmin would have a job.

      --
      I should use this sig to advertise my book ISBN-13 : 978-1501515132.
    5. Re:Backup, anyone? by davester666 · · Score: 1

      No, because a good sysadmin would like to eat something besides mac&cheese, and the company prefers to pay wages that would require you live with your parents rent free, and on your "special night" you can afford to spring for mac&cheese...for yourself.

      --
      Sleep your way to a whiter smile...date a dentist!
    6. Re: Backup, anyone? by Anonymous Coward · · Score: 0

      Maybe he knew the backup aren't usable. What he didn't know, the program was fixed after his resignation

    7. Re:Backup, anyone? by thegarbz · · Score: 1

      I don't think a malicious vindictive sysadmin has thought through any part of his life or what he is about to do. I don't credit these people with much in the way of brains.

    8. Re:Backup, anyone? by Anonymous Coward · · Score: 0

      I read enough response about backup, recovery, MAC spoofing, etc. Has anyone every thought of just disabling his accounts? If they knew he was gone or had left, they should have shut down all unknown accounts and changed the passwords of any shared accounts.I wonder if they found and recently created accounts or are the focused only on his second laptop. How about assessing the authentication methods used in house?

    9. Re:Backup, anyone? by TechyImmigrant · · Score: 1

      No, because a good sysadmin would like to eat something besides mac&cheese, and the company prefers to pay wages that would require you live with your parents rent free, and on your "special night" you can afford to spring for mac&cheese...for yourself.

      So leaving and messing with the database gets you better food that mac & cheese. I'm not seeing your logic.

      --
      I should use this sig to advertise my book ISBN-13 : 978-1501515132.
  2. Pretty Obvious What the Timebomb Is... by segedunum · · Score: 5, Insightful

    They're using Oracle.

    .....and, backups??! But of course, that's a silly question.

    1. Re:Pretty Obvious What the Timebomb Is... by Anonymous Coward · · Score: 0

      Oracle is the time bomb? DUH!

    2. Re:Pretty Obvious What the Timebomb Is... by Anonymous Coward · · Score: 0

      Of all the knocks on Oracle I have seen on Slashdot (most of which are completely valid), I have never seen an insinuation that their products are not reliable. I do not believe that is one of their weaknesses.

    3. Re:Pretty Obvious What the Timebomb Is... by Anonymous Coward · · Score: 0

      It didn't blow up the database on April 1st. The problem was discovered 2 weeks later, presumably when things didn't add up. Then, they searched the backups to find out what and when it happened.

      Of course, Oracle has a variety of option$$ to protect or monitor against that in the first place.

    4. Re:Pretty Obvious What the Timebomb Is... by Anonymous Coward · · Score: 3, Interesting

      Of all the knocks on Oracle I have seen on Slashdot (most of which are completely valid), I have never seen an insinuation that their products are not reliable. I do not believe that is one of their weaknesses.

      Oh, it's reliable alright.

      You can count on being reliably fucked as as customer at any given time.

      And that's just dealing with the software audit mafia. Forget actually patching the fucking thing and not breaking all kinds of shit in the process.

    5. Re:Pretty Obvious What the Timebomb Is... by Thelasko · · Score: 5, Funny

      They're using Oracle.

      Seriously. If they were using SAP he would have never figured out how to sabotage it.

      --
      One of our competitors trademarked the term "hypothesis". From now on, we will call them "boneheaded ideas".
    6. Re:Pretty Obvious What the Timebomb Is... by Anonymous Coward · · Score: 0

      So, how do we know this wasn't an Oracle bug to begin with?

    7. Re: Pretty Obvious What the Timebomb Is... by Anonymous Coward · · Score: 1

      When I think of Oracle and 'time bomb', I think of getting locked in with a good deal, then getting screwed years down the road with increased licensingâ costs and audits. I do think the software is reliable though.

    8. Re:Pretty Obvious What the Timebomb Is... by Anonymous Coward · · Score: 0

      Try IBM, SAP, etc and then compare. Even biggies like Google, Amazon, Apple use Oracle. So do MIT and Harvard. Never mind. They are all stupid.

    9. Re:Pretty Obvious What the Timebomb Is... by gravewax · · Score: 2

      SAP is actually the easiest of all to sabotage, just hire a SAP consultant.

    10. Re: Pretty Obvious What the Timebomb Is... by Anonymous Coward · · Score: 0

      "Try IBM, SAP, etc and then compare. Even biggies like Google, Amazon, Apple use Oracle."

      Amazon is currently migrating what still remains on Oracle to other solutions, the leadership team's goal is to have 0 Oracle databases by the end of 2017. Many big workloads have already been migrated to solutions that use AWS services as building blocks for better scalability and performance than Oracle can provide.

    11. Re: Pretty Obvious What the Timebomb Is... by Anonymous Coward · · Score: 0

      When I think of Oracle and 'time bomb', I think of getting locked in with a good deal, then getting screwed years down the road with increased licensingâ costs and audits. I do think the software is reliable though.

      In other words, you can count on being reliably screwed for years if you use this software?

      That's one hell of a business plan you've got there. Sounds like a great recipe for success.

    12. Re:Pretty Obvious What the Timebomb Is... by Anonymous Coward · · Score: 0

      apparently you've never used asmlib(has the world's shittiest block device detection code.)

  3. Eletronic fingerprint? by Viol8 · · Score: 5, Insightful

    "Eventually, they traced the unauthorized access to Patel's second business laptop based on the device's "electronic fingerprint.""

    Translation: Someone with a functioning braincell in the IT department googled about MAC addresses and thought maybe they should check the wifi router logs and look for unauthorised access by company issue laptops.

    1. Re:Eletronic fingerprint? by AndroidCat · · Score: 4, Informative
      "return the second laptop because the device was capable of accessing Allegro's IT network"

      It sounds like they depend on the MAC address for access security, and not-a-one-of-them has ever heard of MAC spoofing. (Or a Pingles can for extending WiFi range to off of company property.)

      --
      One line blog. I hear that they're called Twitters now.
    2. Re:Eletronic fingerprint? by Lumpy · · Score: 1

      Second translation: DB admins are pretty inept at IT. It's trivial to change the Mac address.

      Once again proving that those that do evil deed are typically pretty stupid and leave obvious clues.

      --
      Do not look at laser with remaining good eye.
    3. Re:Eletronic fingerprint? by duke_cheetah2003 · · Score: 3, Insightful

      Once again proving that those that do evil deed are typically pretty stupid and leave obvious clues.

      Na, just proves the stupid evil doers are still stupid. We never hear about the smart evil doers. If there is such a thing. :D We'll never know, if they're smart enough.

    4. Re:Eletronic fingerprint? by aaarrrgggh · · Score: 2

      X.509 could also explain it.

    5. Re:Eletronic fingerprint? by Anonymous Coward · · Score: 1

      He wouldn't need to keep the laptop if all he had to do was spoof the MAC address. It sounds like they know more about network security than most Slashdot posters. Though, the articles are never clear on this so who knows. Anyway, what the company primarily at failed was proper asset control.

    6. Re:Eletronic fingerprint? by Stealthey · · Score: 5, Interesting

      Second translation: DB admins are pretty inept at IT. It's trivial to change the Mac address.

      Once again proving that those that do evil deed are typically pretty stupid and leave obvious clues.

      You missed the key point too.

      The anon poster before you had the right idea.

      He wouldn't need to keep the laptop if all he had to do was spoof the MAC address.>

      If all he needed was the mac address, then he didn't even need the laptop. He could have spoofed the Mac Address. Most likely there was additional network security which is why he needed the laptop. It could be a cert/key etc. too that was on the laptop which he couldn't spoof.

      --
      I am at loss with words...
  4. maybe multiple time bombs by turkeydance · · Score: 1

    and this is the only one to be made public

  5. Re:So many stupid questions by Anonymous Coward · · Score: 5, Funny

    One more stupid question:
    Have you ever worked anywhere before?

  6. Of course Allegro had Backups? by BoRegardless · · Score: 4, Interesting

    Who in the heck was monitoring for changes to Oracle's software? Too many unanswered questions.

    1. Re:Of course Allegro had Backups? by Afty0r · · Score: 1

      RTFA? It specifically mentions backups and how the used them.

  7. Turnabout is fair play by PackMan97 · · Score: 0

    Something tells me the company didn't care what sort of damage they did to Patel's year end financials when they canned him. Turnabout and all that. Maybe next time the company will consider using something as simple as two factor authentication to make something like significantly more difficult.

    1. Re:Turnabout is fair play by Aeros · · Score: 1

      The article said he resigned.

    2. Re:Turnabout is fair play by Anonymous Coward · · Score: 0

      Maybe, maybe not. An intelligent person could put in time bombs and/or untraceable back doors well before they get canned. However, an intelligent person would not commit career/financial suicide by trying to attack their employer. What a moron.

    3. Re:Turnabout is fair play by Anonymous Coward · · Score: 0

      Something tells me the company didn't care what sort of damage they did to Patel's year end financials when they canned him. Turnabout and all that.

      Maybe next time the company will consider using something as simple as two factor authentication to make something like significantly more difficult.

      "Patel resigned from his job in 2016" - in big, blue serify fontyness.

    4. Re:Turnabout is fair play by Afty0r · · Score: 1

      RTFA? "Canned him"? There's a pretty big blue paragraph heading stating he resigned. No evidence they canned him.

    5. Re:Turnabout is fair play by Anonymous Coward · · Score: 0

      RTFA?

      "Canned him"? There's a pretty big blue paragraph heading stating he resigned. No evidence they canned him.

      If that is the case, then forget all of the questions related to how the company wasn't monitoring for this kind of change, and failed to protect themselves.

      I want to know why the fuck he chose to attack a company he voluntarily resigned from.

    6. Re:Turnabout is fair play by XXongo · · Score: 4, Insightful

      The article said he resigned.

      In most cases of IT staff leaving a company, the word "resigned" is a euphemism, and should be written in quotes.

    7. Re:Turnabout is fair play by Anonymous Coward · · Score: 0

      Something tells me the company didn't care what sort of damage they did to Patel's year end financials when they canned him.

      Even if they had wanted to damage his financial records, how would the company get access?

      TFA says he was using a company laptop for personal purposes (but with permission) so it's possible the company had put some malware or spyware on it, but article isn't alleging that, nor does it say he was using the laptop for financial records storage.

      What is this "something" that is telling you this wild idea? Something tells me they merely fired him, but took no aggressive action. That's usually how it goes.

    8. Re:Turnabout is fair play by Cajun+Hell · · Score: 5, Funny

      I want to know why the fuck he chose to attack a company he voluntarily resigned from.

      To this day (wow, has it really been 50 years?), I still don't know why Number Six resigned. Perhaps the reason he was kidnapped and taken to The Village, was that the government had serious concerns about what he was going to do next. Until you know why he resigned, it's really hard to guess anything else.

      --
      "Believe me!" -- Donald Trump
    9. Re:Turnabout is fair play by molarmass192 · · Score: 2

      Not disagreeing with you, but I've seen a few people "rage quit". This incident would seem to fit that pattern. On the bright side, at least he didn't walk in with a machine gun.

      --

      Good people do not need laws to tell them to act responsibly, while bad people will find a way around the laws-Plato
    10. Re: Turnabout is fair play by Anonymous Coward · · Score: 0

      If he used a shotgun, pistol or semi automatic machine gun and shot up the place, he'd probably be better off financially, and possibly get a better sentence.

    11. Re:Turnabout is fair play by Anonymous Coward · · Score: 0

      Is it safe to offer a spoiler alert after 50 years? I hope so... He wasn't really "Number 6". If my memory is correct at the end of the series we learned HE was Number 1.

    12. Re:Turnabout is fair play by hokeyru · · Score: 2

      Whatever the circumstances, professionals do not sabotage their former employers (or current employers, for that matter).

      Besides compromising your professional integrity, and risking criminal charges, it's just not work your time. Move on and live your life.

    13. Re:Turnabout is fair play by TechnoJoe · · Score: 1

      He resigned, because he found out what was happening to people who resigned. He was outraged; he wanted to do something about it; and he figured the best way to stop it was to crack it from the inside.

    14. Re:Turnabout is fair play by Anonymous Coward · · Score: 0

      >voluntarily resigned

      This does not equal happy, prosperous, amicable separation. Do you resign from the movie theater when it's such a bad movie, popcorn stale, babies crying in the background... do you leave 'happy' or do you want your money back (or some emotional compensation like a sabatouging review on FB or Yelp)?

  8. Lessons from this are by Anonymous Coward · · Score: 0

    1. All passwords should be reset every 90 days so an ex-employee cant login months later.
    2. Hardware audits should be done regularly (every 6 months or so). If a laptop goes missing it's MAC address should be removed from the "okay to connect to our wifi" list.
    3. Files this important should be backed up like crazy so that one attacker cant possibly get every copy short of dropping nukes at multiple locations.

    Am I missing anything?

    1. Re:Lessons from this are by Joe_Dragon · · Score: 1

      service accounts passwords can be hard to change and in some cases need downtime to change. Also some apps have DB passwords in plain text in the config files.

    2. Re:Lessons from this are by tomhath · · Score: 1

      He didn't log in months later. He left a time bomb that went off months later.

    3. Re:Lessons from this are by Anonymous Coward · · Score: 0

      I have been at my current job ten years. The default password for the local admin account has never changed. That doesn't get you on the company network but still.

    4. Re:Lessons from this are by Hylandr · · Score: 1

      Also all apps have DB passwords in plain text in the config files.

      FTFY.

      Though it's been a weakness for so long you would think someone would have created a means of encrypting connection data like you would sign a certificate signing request for an SSL cert. At least add another hoop to jump through in case site performance wasn't dismal enough.

      --
      ~ People that think they are better than anyone else for any reason are the cause of all the strife in the world.
    5. Re:Lessons from this are by Anonymous Coward · · Score: 0

      I have been at my current job ten years. The default password for the local admin account has never changed. That doesn't get you on the company network but still.

      Same here. My previous company had the same admin password for ALL OUR CLIENTS. (Yeah, they provided IT services to hundreds of businesses.)

      After hiring and firing several employees over 10 years, they finally updated their password. They changed the last character to an exclamation mark instead of a period. And yeah, it was a dictionary word. They were utterly incompetent.

      I got sick of doing everything while the rest of staff refused to learn routing, switching, Linux, BSD, web design, web hosting, etc...and I left. Within 3 months the clients bailed and the business imploded. All their former clients came to contact with me. Several of them said the reason was "you were obviously the only guy who knew anything".

      Hell, at one point they couldn't figure out windows sharing permissions, so they called me to see if I would fix it. I told them my hourly rate was $125/hr (what they charge the client) and they declined. I have chat logs of me asking if they solved it a few days later...and the tech said they just gave everyone 'full control'. After the client found out everyone could access confidential data the company played the "that must have been the former IT contractor" card. Most IT providers I have run into are crooked as hell.

    6. Re:Lessons from this are by Anonymous Coward · · Score: 0

      Also all apps have DB passwords in plain text in the config files.

      FTFY.

      Though it's been a weakness for so long you would think someone would have created a means of encrypting connection data like you would sign a certificate signing request for an SSL cert. At least add another hoop to jump through in case site performance wasn't dismal enough.

      Not true. We've had encrypted database passwords in our application configs since 2001.

    7. Re:Lessons from this are by magarity · · Score: 1

      Am I missing anything?

      Jackasses like this are why:
      4. Anyone who gives notice to quit is immediately escorted (dragged?) out by security while an HR droid packs up their desk of personal items and mails it to them.

    8. Re:Lessons from this are by cyberchondriac · · Score: 1

      At work we just recently had Oracle come in and do a security analysis, and plain text passwords in files was one of their findings, (some, not all files); they have a method to remediate that, as they pointed it out.

      --

      Look back up at my post, now look back down, you're on the Internet. Now look back up. I'm a signature.
    9. Re:Lessons from this are by lactose99 · · Score: 1

      eyaml works very nicely for this

      --
      Fully licensed blockchain psychiatrist
    10. Re:Lessons from this are by Hylandr · · Score: 1

      As far as DevOps or infrastructure as code stuff goes passwords can be obfuscated through the use of encrypted data bags but ultimately the password is going to be in a plain text password file on the storage mechanism of the server like Wordpress or Drupal, etc.

      I am referring to requiring the use of encrypted config files.

      --
      ~ People that think they are better than anyone else for any reason are the cause of all the strife in the world.
    11. Re:Lessons from this are by petermgreen · · Score: 1

      Encrypting client connection data gives little more than a false sense of security. If the client needs to automatically log in then it needs to be able to automatically decrypt the creditials. If the server can do that then most likely so can the sysadmin.

      Accounts used for automatic authentication should have their credentials rotated frequently and the minimum privilages practical to do their job. Unfortunately that is a PITA to do so people often don't :/

      --
      note: i'm known as plugwash most places but i screwd up registering that here somehow in the past and now can't register
    12. Re:Lessons from this are by Hylandr · · Score: 1

      Unfortunately that is a PITA to do so people often don't :/

      Chef, Jenkins, Puppet, Thoughtworks GOCD.

      There's no excuse.

      --
      ~ People that think they are better than anyone else for any reason are the cause of all the strife in the world.
    13. Re:Lessons from this are by Joe_Dragon · · Score: 1

      what about apps where you need to restart them to update the DB password and it's hard to get the downtime to do that. Or there you need to change 4-6 apps at the same time as they are all tied to the same DB?

    14. Re:Lessons from this are by Hylandr · · Score: 1

      This is what the Change Advisory Board is for. Ever heard of a CAB meeting? Sometimes Downtime is mandatory. If you have other deployments that cannot be handled with a rolling update then piggy back during that deploy.

      Also, Since we are most likely dealing with AWS or some other virtualization an entirely new cluster could be rolled out if engineered correctly, and the traffic routed to the new cluster.

      ITIL :
      http://www.bmc.com/guides/itil...

      SAFe:
      http://www.scaledagileframewor...

      --
      ~ People that think they are better than anyone else for any reason are the cause of all the strife in the world.
    15. Re:Lessons from this are by Anonymous Coward · · Score: 0

      A large organization should be using smart cards for logons no passwords allowed especially for sysadmins/dba's. Get a corporate cert sever and certify that no one can "share" common passwords. At least this is how the last company I worked for handled its security. LDAP (Active Directory) can be your friend but if you leave it up to a bunch of high-fiveing pointy haired Ops managers, prepare to be disappointed.

    16. Re:Lessons from this are by AvitarX · · Score: 1

      couldnt the 4-6 apps each use their own user, so they could be updated one at a time?

      --
      Wow, sent an e-mail as suggested when clicking on "use classic" banner, and got a fast response that addressed my msg
  9. RTFA, anyone? by tomhath · · Score: 5, Informative
    FTFA:

    Allegro's IT staff discovered the sabotaged Oracle finance module on April 14, 2016. Ten days later, on April 24, the IT staffers found Patel's malicious code after comparing the current database with a copy from older backups.

  10. They had backups right? by 140Mandak262Jamuna · · Score: 4, Funny

    I am sure a big company like Allegro will have all the critical information replicated in multiple locations. I am sure they restored all the data in a few seconds and laughed at the stupid sys admin. Right? That is how the story should have ended

    --
    sed -e 's/Chuck Norris/Rajnikant/g' joke > fact
    1. Re:They had backups right? by AmiMoJo · · Score: 5, Insightful

      It's not worth posting stories about these amateurs. Everyone knows you don't just delete random stuff, you introduce subtle errors that can be passed off as genuine mistakes, and which take years to fully manifest, way beyond the point where backups can help.

      --
      const int one = 65536; (Silvermoon, Texture.cs)
      SJW, n: "Someone I don't like, and by the way I'm a fuckwit" - AC
    2. Re:They had backups right? by Anonymous Coward · · Score: 0

      The industry wants CHEAP. You can't make a fortune if you have to spend all your profits on redundant systems and redundant staff.

      We want technicians that can solve our problems on low salaries, and that never make mistakes or betray us.

      You technicians need to know your place!

    3. Re:They had backups right? by phantomfive · · Score: 1

      Your homepage is actually really great. There is however a broken link on the front page.

      --
      "First they came for the slanderers and i said nothing."
    4. Re:They had backups right? by OpenSourced · · Score: 1

      Of course, but you keep all your noxious code always in the stack, rendered inactive by a script that you bring in your USB stick, and manually execute every six months. Then when you are no longer there to execute the script...

      Much safer than having to hack the network to delete things and leaving a trail and all that. Of course it's a lot of work, and perhaps your wife is right, and if you had used all that work for the benefit of your company, perhaps they wouldn't have fired you.

      --
      Rome taught me patience and assiduous application to detail. Virtues which temper the boldness of great, general views.
    5. Re:They had backups right? by sinij · · Score: 2

      AmiMoJo, I am pleasantly surprised that you are not entirely zen-like.

    6. Re:They had backups right? by sinij · · Score: 1

      Running script is easy-ish to detect and attribute. Much better is to have it periodically look for something unusual, but plausible, that only you would know to do. Like manual backup or some diagnostic test.

    7. Re:They had backups right? by Anonymous Coward · · Score: 2, Interesting

      An effective (and legal) way of screwing over an employer would be not to automate certain infrequent but mission-critical tasks. Just document what needs to be done (and when) in your well-written and exhaustive handover notes. If you're feeling unkind don't explicitly state why or how to perform such a task (e.g. "purge old logs from the database server instance weekly"). Bonus points if before you leave you pitch a project to automate essential maintenance tasks to your boss, and they shoot it down as a waste of time*.

      When the intern/son of VP/HB1 they decided was a suitable replacement for an experienced sysadmin invariably hasn't followed the handover docs, the server will fill up, run out of space, and shit its pants. And they have nobody to blame but themselves. If they try to pin it on you, just send them the handover doc with the appropriate passage highlighted, and a copy of your consultancy rates if they'd like you to help sort it out.

      I've never done this on purpose, but I know it would work, because every single place I've left has called up a few months later with some dire emergency that could have been easily avoided if they'd just read my handover notes.

      *: this actually happened at a company I was leaving. I'd got a lot of vacation days accrued, and they wanted me to take them during my notice period rather than do the automation project I knew they needed, saving themselves two weeks of pay that they'd otherwise have to tack on to my final cheque. In the end they asked me back a few months after I'd quit, and paid me the equivalent of two months salary to do the project, which was basically just refactoring and gluing together the various crappy shell scripts I'd written over the years and setting up a traffic light status monitor so they could see when things needed looking at. I felt kind of bad for them, but then I remembered the reason I left is that they wouldn't take my advice...

    8. Re:They had backups right? by Anonymous Coward · · Score: 0

      Maybe look at the size change of your $(HOME)/.bash_history every couple months, (return zero if file doesn't exist)? If you are working, the file size should be changing. When you are fired, they either keep your $(HOME) and file size doesn't change, or they delete your $(HOME), size is returned as zero and doesn't change when your script checks it next time.

  11. How... by mhkohne · · Score: 1

    is there a file anywhere with usernames and passwords? Is that jut mis-understanding and he cracked the hashes, or do these guys actually have everyone's password written down somewhere?

    An yea these days, if your shit matters, you need 2FA of some sort.

    Also, apparently, you need the guy who checks in the returned laptops to check serial & model numbers...

    --
    A thousand pounds of wood moving at 300 feet per minute. Don't get in the way.
    1. Re:How... by Kiralan · · Score: 1

      From the article: Patel had access to employee credentials because he was one of the company's senior system administrators, and kept a copy of a file with usernames and passwords on his laptop.

      --
      V for Vendetta: People should not be afraid of their governments. Governments should be afraid of their people.
    2. Re:How... by v1 · · Score: 1

      I don't care if you ARE a senior system administrator, you have NO business having a list of user passwords. You have no business having anyone's password, EVER. There are times we need to connect as a user or login to their network account to fix a problem or test something. When that happens, we reset their password, do our work, hand them over the reset password, and their account has the "must change password immediately at next login" flag set. (A) we never know their password old OR new, (B) we get our work done, (C) they KNOW we were logging into their account for a time (this is important, don't skip it), (D) they immediately regain exclusive authentication to their account, and (E) the entire process is automatically logged from start to finish. It's nothing extraordinary, that's just how you do it. Any company stupid enough to have a plaintext password list for their employees is completely undeserving of anyone's pity when Bad Things(tm) happen as a result. Yeah he shouldn't have stolen your truck, but you really shouldn't have left the keys in the ignition.

      (the entire password reset process is online for the user - we don't just take a new password over the phone, and we state in numerous places in addition to our AUP at the login window that we will never ask you for your password, and if anyone ever does, to report it immediately)

      Of course there were numerous other serious fails in this embarrassing story, but IMHO this was the most disgraceful fail of them all.

      --
      I work for the Department of Redundancy Department.
    3. Re:How... by rossz · · Score: 1

      So much this. The only time I know someone's password is when I set it the first time with a forced change the first time they log in, typically minutes later. I don't want to know anyone's password, nor do I need to know anyone's password.

      When someone leaves, I immediately nuke all of their account credentials, often before they even exit the building.

      --
      -- Will program for bandwidth
    4. Re:How... by angel'o'sphere · · Score: 1

      But, you do know the "password" is not the key to the account?

      As a "sysadmin" I can basically always use your account without you noticing and without knowing your password. How to do that ofc varies from OS.

      --
      Cost free eBook I read (by iBook/Kobo/Amazon/ObookO/Gutenberg etc.): "The Green Odyssey" by Philip Jose Farmer.
    5. Re:How... by v1 · · Score: 1

      But, you do know the "password" is not the key to the account?

      As a "sysadmin" I can basically always use your account without you noticing and without knowing your password. How to do that ofc varies from OS.

      I've seen that feature in directory services, when you go to the directory admin account configuration. "Use directory admin password to masquerade as other user". Basically means the diradmin master password will authenticate ANY account if you check that box. I've never used that before, and we don't have that option where I work now. It's a bad idea. Allowing an admin to access someone's data, okay, they may need to do that. But allowing an admin to login AS a user, so that they can take actions that appear to be done by the user, and everything they do is logged as though it WAS the user, that's dangerous and almost always unnecessary. If I'm having problems reproducing a problem, I'll go to the user who's already logged in and, while they are there watching, do what I need to do. It's important they stay there over my shoulder while I work because no one can question what I did while the User wasn't there because the user was always there. We also have a policy here of obviously turning our view away from a user's keyboard whenever we need them to enter their password for something. We make it VERY obvious that we are not observing their typing.

      A lot of this is "CYA". There's no question whether or not you've done something if it's impossible for you to have done it. "Dave must have logged in as me and emailed that document to the reporter". No, Dave never had your password, and it's impossible for him to login as you. He could only do that if he reset your password to a known value, and then (A) the reset would be logged under his account, and (B) you would know about it because you'd have to reset it back again because Dave would have no way to reset it back to its previous password. If that happened, IT would know and you would know. This works more as a protection for Dave than it does for the User. When you're in a position of power, it's important to maintain your users' trust. And guaranteed accountability is a big part of that.

      I've never seen this feature in a local OS environment. On windows or mac, you as an admin can reset someone's password and then login as them, but as above you have no (easy) way to change their password back to its previous value. So the user would be aware that something had happened, even if they don't know exactly what happened. The problem with a local OS is that a sufficiently skilled nerd could copy down the password hash, reset it, do the nasty, and then restore the previous hash. (I could probably pull that off) But this is far from a turnkey action, requiring a fairly high degree of skill and level of access, and not something the average user should need to worry about. If you have guys regularly mucking with the password hash file, you have much more serious problems to deal with than IT masquerading as users.

      --
      I work for the Department of Redundancy Department.
  12. Obviously the firm had bad data retention by WillAffleckUW · · Score: 1

    That said, how do they know it was said person? This is an accusation, not a proven fact.

    More likely one of the senior execs deleted the files to cover up some theft on their part.

    Never assume.

    --
    -- Tigger warning: This post may contain tiggers! --
  13. Chain of custody much? by Anonymous Coward · · Score: 0

    Guy has a Passwords file of end user logins. Sounds like your financials have no validity right there. Damage done.

    To make this stick you need the following:
    1: Picture of the guys car and his face in the car near the AP being used.
    2: Proove it's the laptop. If you need a WAP Certificate, Client Certificate, MAC, that's reasonable.
    3: You now need to track the connections from the WAP to the oracle server. Every single flow session.
    4: You need to associate the server connection to the user account.
    5: You need to associate the changes to the user account.

    I doubt they'll be able to do that via logs if he was half smart.

    For all they know, he could've sold the laptop to a competitor and they planted the bomb. Perfectly legal to sell corporate secrets to a competitor for any amount of money in the US, by the way.

    1. Re:Chain of custody much? by MichaelSmith · · Score: 1

      But the user account logged in after his employment ended. Then bad stuff happened. That might be enough.

  14. Financial Damages? by wisnoskij · · Score: 1

    How does one calculate the damages a company suffered by being rendered unable to generate financial reports?
    Unless their business is generating financial reports, that does not seem like that would get in the way of producing whatever it is they produce. And if they do not know how much money they have, how can they ever estimate how much they lost?

    --
    Troll is not a replacement for I disagree.
    1. Re:Financial Damages? by Anonymous Coward · · Score: 0

      If they were publicly traded, they can claim that "Goodwill" was hurt when they delayed the release of the 10-Q report and the stock dropped. However, AM is privately held, so it will be next to impossible unless some fund wanted out and this was a good excuse in the contract.

      That means their only hope is to exaggerate the losses in criminal court, because a civil judge would only let them claim labor costs to fix things.

    2. Re:Financial Damages? by dbIII · · Score: 1

      How does one calculate the damages a company suffered by being rendered unable to generate financial reports?

      Part four of this (about half way through it) has an example (about half way through it) of how ridiculous damage estimates for computer crime were "determined".
      http://www.mit.edu/hacker/hack...
      Damage of $79,449 was determined (in itemised detail) for downloading a document that could be purchased in hard copy form for $13.

      Sadly the same sort of reasoning still applies.

    3. Re:Financial Damages? by angel'o'sphere · · Score: 1

      How does one calculate the damages a company suffered by being rendered unable to generate financial reports?
      By the fine they get and by the time/efford they need to recover the data and finally deliver the report.

      --
      Cost free eBook I read (by iBook/Kobo/Amazon/ObookO/Gutenberg etc.): "The Green Odyssey" by Philip Jose Farmer.
  15. Where's the proof? by eaglesrule · · Score: 1

    So the best evidence they have is the MAC address of the wifi adapter of the business laptop that wasn't returned. We all know how immutable that is.

    The article seems merely to be parroting the court documents that were filed by Oracle, leading to a one sided story. Just as likely Patel is being being thrown under the bus for someone else' screwup, or perhaps a case of industrial sabotage. Excuse me if I don't assume anything Oracle is alleging as true.

  16. Why are they suing? by trevc · · Score: 1

    Isn't this illegal hacking? Call the FBI.

    1. Re:Why are they suing? by Gilgaron · · Score: 1

      Lower burden of evidence in civil court, but I'd expect they'll do both.

  17. Not very good at covering tracks. by nuckfuts · · Score: 3, Informative
    FTA:

    Eventually, they traced the unauthorized access to Patel's second business laptop based on the device's "electronic fingerprint."

    By "electronic fingerprint", I suspect they're referring to the MAC address of the laptop's WiFi adapter, in which case the guy is a bit of a noob for not spoofing it.

    1. Re:Not very good at covering tracks. by dbIII · · Score: 1

      Personally I think it smells like insurance fraud by blaming a convenient ex-employee for a fuckup. If it was real I think the police would be very interested and the guy wouldn't just be getting sued.

    2. Re:Not very good at covering tracks. by Anonymous Coward · · Score: 0

      By "electronic fingerprint", I suspect they're referring to the MAC address of the laptop's WiFi adapter, in which case the guy is a bit of a noob for not spoofing it.

      Sure, you can suspect it. And you suspect it because it gives you a sense of superiority and a feeling of being much more intelligent that the stupid noobs.

      Me? I have no fucking clue what their setup is. But my self worth doesn't depend on assuming that everyone else are idiots.

    3. Re:Not very good at covering tracks. by denbesten · · Score: 1

      Simply depending on a MAC address alone would be an amateur move. A talented investigator will not rely on a single fingerprint. Instead, the professional will balance the reliability (e.g. resistance to tampering) and identifiablity of multiple fingerprints. For example, one will search logs for hostnames, UUIDs, usernames, etc. Amongst other things, this is what keeps the professional from getting (too) hung up on concluding that it was the user who's credentials were stolen. I'm also sure that the fact that Patel did not return the laptop after being reminded also helped focus the investigation.

    4. Re:Not very good at covering tracks. by nuckfuts · · Score: 1

      ... you suspect it because it gives you a sense of superiority and a feeling of being much more intelligent that the stupid noobs.

      No, I suspect it because it strikes me as a plausible explanation.

      Me? I have no fucking clue what their setup is.

      Which is perfectly fine, but then why feel the need to chime in?

      But my self worth doesn't depend on assuming that everyone else are idiots.

      Oh, I see, You're making some gigantic assumption about what motivates me and gives me a sense of self-worth. OK.

      For my part, I'm not assuming the guy is an idiot. I'm making an assessment based on the published facts. Merely setting out to do what this guy did, competently or not, is a bit idiotic, don't you think?

  18. Not how it's done ... by CaptainDork · · Score: 3, Insightful

    ... for a sysadmin.

    Know where the logs are and erase the goddam things.

    --
    It little behooves the best of us to comment on the rest of us.
    1. Re:Not how it's done ... by DogDude · · Score: 1

      Nothing in the article said he was a sysadmin. It says he was an Oracle programmer.

      --
      I don't respond to AC's.
    2. Re:Not how it's done ... by Anonymous Coward · · Score: 0

      Maybe you should read the title?

    3. Re:Not how it's done ... by CaptainDork · · Score: 1

      From TFS:

      According to court documents, after resigning from his job, a former sysadmin kept one of two laptops.

      --
      It little behooves the best of us to comment on the rest of us.
    4. Re:Not how it's done ... by thegarbz · · Score: 1

      ... for a sysadmin.

      Know where the logs are and erase the goddam things.

      For a sysadmin who left their job and then decided to vindictively retaliate against his former company, you actually think they have brains?

    5. Re:Not how it's done ... by CaptainDork · · Score: 1

      ... you actually think they have brains ...

      I was speaking from experience, you insensitive clod.

      --
      It little behooves the best of us to comment on the rest of us.
  19. idiots by Anonymous Coward · · Score: 0

    So, they canned a SYSADMIN/DBA and didn't change any of the "root" p/w afterwards?
    idiots.
    I know Oracle Apps rely on WAY too much "root" access to work properly and makes it a nightmare to change those kinds of p/w, but the DB?
    How did they NOT recover company property (the 2nd laptop) or kill the remote access tokens when this guy left? (unless that was HIS JOB.)
    still, idiots.

  20. Unprofessional H1-B Visa holders by Anonymous Coward · · Score: 0, Insightful

    Judging by his name it's pretty clear this guy was a foreign worker. Getting all their data deleted is exactly what this company deserved for hiring H1-B immigrants. It's obvious these unprofessional individuals are likely to resort to these sort of time-bomb tricks after they resign or are laid off.
    Of course, a professional, all-american, disgruntled IT worker would do the right thing and just break into the premises with an assault rifle instead.

  21. PIT recovery by Anonymous Coward · · Score: 0

    The nice thing about Oracle trans/redo logs offer ability to restore previous version of the database to any time in the past so long as your logs are backed up properly.

    Regardless of whether this was incompetence or malice it shouldn't cost 100k to recover unless your IT is grossly incompetent anyway.

    1. Re:PIT recovery by Anonymous Coward · · Score: 0

      Let's see, an IT department that can't account for all of its physical assets is pretty incompetent, I would say.

    2. Re:PIT recovery by Anonymous Coward · · Score: 1

      A few years ago I worked for a large S/W development company that was in the process of being aquired. As part of the due diligence they needed to do an audit of all their PCs. They couldn't account for roughly 25,000 machines.

      It's not as bad as it sounds, mostly they weren't good at recording which machines had died and were parted out or were put on a shelf somewhere but never properly decommissioned.

      .

  22. an administrator leaves a company by roc97007 · · Score: 1

    An administrator leaves a company. A few weeks or months later, things start to fall apart. This tends to happen even if there's no malicious code involved.

    --
    Oliver's law of assumed responsibility: If you're seen fixing it, you will be blamed for breaking it.
    1. Re:an administrator leaves a company by WillAffleckUW · · Score: 1

      This could also happen if they forgot to renew the software.

      A long time ago, I remember it was fairly common practice, in fact.

      But, hey, I'm sure the relative of one of the execs they hired is good at his job.

      --
      -- Tigger warning: This post may contain tiggers! --
    2. Re:an administrator leaves a company by roc97007 · · Score: 5, Interesting

      "This could also happen if they forgot to renew the software."

      Absolutely. The biggest time bomb of all might be simply to decline to share the file of license renewals. The company starts to feel the results of *that* after the admin is long gone. And all the warning messages go to the admin's closed account, or to a service account that nobody checks since he left.

      The problem is, the results are indistinguishable from the case where the admin passed the information to "transition management" prior to being outsourced, only to have them lose it, so he gives them his spare copy, and they lose that also, and then a few months down the road when appliances and software suddenly stop working, offshore management blames the former admins for the debacle(s).

      Don't ask me how I know this.

      --
      Oliver's law of assumed responsibility: If you're seen fixing it, you will be blamed for breaking it.
    3. Re:an administrator leaves a company by Anonymous Coward · · Score: 0

      His leaving was was therefore a timebomb, therefore he is a criminal hacker.
      Luckily, we still had old logs of his logins, unlike all this critical data that we have lost by his villainous hand.

    4. Re:an administrator leaves a company by WillAffleckUW · · Score: 2

      Probably for the same reason I know that.

      Sigh.

      --
      -- Tigger warning: This post may contain tiggers! --
    5. Re:an administrator leaves a company by Anonymous Coward · · Score: 0

      Yeah I've been bitten by something like that before. That is how I learned the profound meaning of CYA. When departing a company always get a receipt for everything you are returning, even knowledge assets, and keep it in a secure folder for ten years.

  23. The correct term by Anonymous Coward · · Score: 0

    is "dead man switch".

  24. Jail time by JustAnotherOldGuy · · Score: 1

    Hello, jail time. Or prison time, perhaps. Either way it sounds like they have this clown dead to rights.

    --
    Just cruising through this digital world at 33 1/3 rpm...
    1. Re:Jail time by dbIII · · Score: 1

      If it was real yes.
      He's being sued instead of being subject to a criminal investigation. I think that's an indication that there is less going on here than was claimed. If you are going to accuse an ex-employee of a crime and you are confident that they actually did it surely it's time to call the police instead of suing them?
      If they really did have him dead to rights I think you will find that the police would be involved - there is theft in the allegations to start with and it goes on from there into stuff that is punished with years of imprisonment.

      When you have what is asserted as a "cast iron case" that makes sure it avoids going through the normal process it probably isn't (or so I'm told).
      Criminals of this type do exist but this thing smells very fishy.

    2. Re:Jail time by gnasher719 · · Score: 1

      He's being sued instead of being subject to a criminal investigation. I think that's an indication that there is less going on here than was claimed. If you are going to accuse an ex-employee of a crime and you are confident that they actually did it surely it's time to call the police instead of suing them?

      Depends on what you want. If you smashed my car and I had the choice between (a) you going to jail for a year, or (b) you paying for all the damage, I'd want to get paid for the damage (if for some reason no insurance would pay). They might say "it's $500,000 damage, the guy is 40 and can work for another 25 years and pay $20,000 a year for the damage".

    3. Re:Jail time by dbIII · · Score: 1

      Maybe but your example is very different and a little bit contrived.
      This thing's into medieval "weregild" territory where a crime with damage gets paid off. It's not the way crimes are normally dealt with in the west.
      Seriously, if it's as bad as suggested why are the FBI not all over this? They've kicked up a huge fuss over far less in the past.

  25. Re:More likely scenario by Anonymous Coward · · Score: 0

    Someone realized they might still have the old MAC address in their logs just as management was breathing down their necks about those vaunted backups they just never bothered with.

  26. Re:So many stupid questions by SharpFang · · Score: 4, Insightful

    The other anon is right: in the real world, unless your employer is NSA or something of comparable caliber, as an admin you have access to everything - whatever you don't have access to, you can obtain, without the employer's knowledge.

    The only defenses against rogue admins companies really have is to have more loyal admins, and not to piss admins off. Plus threat of lawsuit if the admin fails to cover his traces after going rogue. Essentially, you can only try to reduce damage after the attack, you can't prevent the attack.

    And to have anything "better", you have to spend so much on security, that unless security is your *product*, you'll be creating losses.

    --
    45 5F E1 04 22 CA 29 C4 93 3F 95 05 2B 79 2A B2
  27. Revenge best served cold by Anonymous Coward · · Score: 0

    Technical mistakes aside, revenge plan itself is highly flawed. Why is such rush? Set the time bomb for 2018. Even better, make it gradual - where it erases one entry very periodically and randomly. IRS is a lot more dangerous than any data loss. Make it look like it was done by CFO for added complications. Also, instead of accessing it after the fact, having it trigger after keep alive failed. This way you don't actually have to do anything but not be there.

  28. Re: So many stupid questions by Anonymous Coward · · Score: 0

    I provided an encrypted file (TC, old now but whatev) on a restricted share point. I notified HR and the CEO that anything I/IT was not supposed to have access to should go there. Medical, tax, HR docs go there.

    HR set the password and the CEO got a copy on paper from HR. I have documentation saying I can't fix, recover or reset that password if it is lost.

    Last year they added space since it was getting bigger.

  29. Let go of your hate. It's not worth it. by SumDog · · Score: 1

    This is one of those cases where people really need to learn to let their anger go. I'm sure this guy thought he was smart; that he could take precautions. Maybe he even avoided all the security cameras. Maybe it was one ticket sitting in a provisioning system that said that laptop was last on his desk. No matter how well you think you've covered your tracks, in companies that big, there will be a record.

    I'm reminded of the kid who sent a bomb threat via Tor to get out of something at his University. They didn't trace the message back to him. They noticed he was the only one on campus using Tor at that time.

    If you want to fight injustice; talk to some reporters; blow some whistles -- that's one thing. Maybe you could even help people that way. But revenge isn't wroth it. Even if you think you can get away with it. Just take a deep breath, remember humanity will all be extinct one day and that life goes on. People who are full of hate will lead miserable lives.

  30. so... by Anonymous Coward · · Score: 0

    who pissed in his cornflakes?

  31. Is it real? If so why not criminal charges? by dbIII · · Score: 1

    Is it real? If so why not criminal charges?
    It really looks a lot like trying to blame an ex-employee for a fuckup If this was real there is a long list of law enforcement types that would be very interested.

  32. Found his profile by AnthonywC · · Score: 2

    https://www.linkedin.com/in/ni... Although I'd consider that there is a possible chance that they were actually hacked instead.

  33. Re:So many stupid questions by Anonymous Coward · · Score: 0

    Still, there is no justification for this:

    Patel had access to employee credentials because he was one of the company's senior system administrators, and kept a copy of a file with usernames and passwords on his laptop.

    Nobody should ever have somebody else's plaintext password. An admin needs to be able to generate and revoke passwords, not know them. And of course much less after leaving the company. This company deserves what happened.

  34. Sometimes in Italy... by Anonymous Coward · · Score: 0

    There is a curious tradition: if you have something not so conform to actual norms
    an incident may happen ("evidence" got stolen, burned due to electrical accidents,
    vandalism, floods like a broken pipe etc).

    Of course I do not know NOTHING about that case but one other options is that
    the fired guy is only an "excuse" to justify some "delay" o irregular data...

    Sorry for my bed English.

  35. Re: So many stupid questions by SharpFang · · Score: 1

    How did you know IT didn't keep a keylogger on any of the PCs that accessed it?

    --
    45 5F E1 04 22 CA 29 C4 93 3F 95 05 2B 79 2A B2
  36. Re:So many stupid questions by SharpFang · · Score: 1

    "An admin needs to be able to generate and revoke passwords, not know them."

    "Doesn't need" or "Shouldn't" versus "Can't".

    If you have control over the process of setting the passwords, you can have the passwords. You shouldn't and you're not supposed to need to, but who's to stop you, and who will ever know?

    --
    45 5F E1 04 22 CA 29 C4 93 3F 95 05 2B 79 2A B2
  37. Bonus points ... by angel'o'sphere · · Score: 1

    ... if the Sysadmin sabotaged the back ups, too.

    Sorry, stories like this are just ridiculous. A guy who knows his business surely knew that the company has back ups. And a "End of Year" is usually not calculated over the last 365 days, but over the last 11 or 12 "end of month" and the last 1, 3 or 4 or 5 "end of weeks". Depending how and when you make "the end of month".

    --
    Cost free eBook I read (by iBook/Kobo/Amazon/ObookO/Gutenberg etc.): "The Green Odyssey" by Philip Jose Farmer.
  38. Re:So many stupid questions by FictionPimp · · Score: 1

    Most companies have no problem auditing their accounting teams, they should do the same with their IT teams.

  39. Re:So many stupid questions by Whorhay · · Score: 1

    I'm always amused by the importance that people place on having a security clearance from the government, like it's a badge of pride. They seem to have this belief that they've been investigated and found to be super trustworthy people. Like an official certification of worthiness. In reality the whole purpose of a security clearance is to ensure that a person isn't already or likely to be vulnerable to blackmail, paltry bribes, or a bout of guilty conscious. And of course, despite that whole process, people are just people and even the NSA has historically made errors in this area, Snowden being the most obvious example.

  40. Re:So many stupid questions by SharpFang · · Score: 1

    The audit will find cases of incompetence or laziness. It would be very hard for it to find cases of actual subversion, especially if the admin has enough time to hide all the evidence off-site. Never mind his "booby traps" blowing up upon discovery by the auditor, and blaming the auditor for breaking the system.

    --
    45 5F E1 04 22 CA 29 C4 93 3F 95 05 2B 79 2A B2
  41. Not Sure ... by Anonymous Coward · · Score: 0

    Not sure if he is arrogant or just really stupid.

  42. Moral of the story by Anonymous Coward · · Score: 0

    Don't fuck with your IT people - especially those with any admin/root privileges to your systems.

    Case in point one job - set up an admin "backdoor" to the company's Exchange server with some system-sounding name to it, turned off all logging that would possibly implicate me, quit on good terms (even though I hated the place and my narcissistic boss). So I had an ax to grind. Enjoyed reading the CEO's e-mail for several months after I left and even leaked some shit to the local media. CEO left shortly thereafter. That he wasn't indicted was a miracle - but he got the message.

    Another job, rotated daily backups through my car's glove compartment since we had nothing off-site. One co-worker who I was fucking on the side blew the whistle to the feds, who sent an FBI agent knocking on my front door a week after I left on their terms (not mine). Handed her the tapes. CEO was gone in a few months and company shut down within a year

    Again - don't fuck with your IT people... especially when said IT person has the keys to the kingdom and company leadership airs their dirty laundry on the company's e-mail servers. I walk, I talk.

  43. This sounds familiar... by kraffay · · Score: 1

    http://www.marketwatch.com/sto... "I suppose that as the case of the programmer, Rajendrasinh B. Makwana, is brought out into the open we'll discover whether he's just a disgruntled programmer irked at being let go by Fannie Mae in October, or someone with more sinister intentions. It was only a fluke, according to all the reports Friday, that a malicious piece of code was found on the Fannie Mae FNM, -6.82% servers. It was designed to go off Saturday and erase all the data and screw up the company. It was placed there by Makwana, an Indian national and former Fannie Mae contractor, according to a federal indictment. If it was part of some greater scheme, then we can assume that on Jan. 31, the date his program was supposed to kick in, a slew of computer networks will go down. Generally speaking, this sort of thing is more of an inconvenience than a catastrophe."

  44. Re:So many stupid questions by FictionPimp · · Score: 1

    Well I guess the best thing to do then is nothing. Just know the admin is all powerful and pay him 6 figures.

  45. Re:So many stupid questions by SharpFang · · Score: 1

    The right thing is to have competent people perform the hiring, hire a couple competent admins, and treat them well.

    They don't go rogue "for teh lulz".

    --
    45 5F E1 04 22 CA 29 C4 93 3F 95 05 2B 79 2A B2