Slashdot Mirror


Rough Justice For Terry Childs

snydeq writes "Deep End's Paul Venezia sees significant negative ramifications for IT admins in the wake of yesterday's guilty verdict for Terry Childs on a count of 'denial of service.' Assuming the verdict is correct, Venezia writes, 'shouldn't the letter of the law be applied to other "denial of service" problems caused by the city while they pursued this case? In particular, to the person or persons who released hundreds of passwords in public court filings in 2008 for causing a denial of service for the city's widespread VPN services? After all, once the story broke that a large list of usernames and passwords had been released to the public, the city had to take down its VPN services for days while they reset every password and communicated those changes to the users.' Worse, if upheld on appeal, the verdict puts a vast number of IT admins at risk. 'There are suddenly thousands of IT workers all over the country that are now guilty of this crime in a vast number of ways. If the letter of the law is what convicted Terry Childs, then the law is simply wrong.'"

418 comments

  1. If I were taking an IT Admin position... by Phrogman · · Score: 5, Insightful

    I think I would want to draft up a very clear - and legally binding - agreement that I would want my superiors in management to sign on behalf of the company. It would spell out in specific details, the security policies, security review process, enforcement etc. It would absolve me from prosecution unless I violated any of the very specific rules that were listed. If my superior changed, they would have to sign the document when they took up their position etc.

    I wouldn't likely get the job, they'd hire someone who wasn't so paranoid, but I don't think I would want to take a job where if someone in management decided to break the rules, and I tried to apply those rules for the sake of ensuring I didn't violate the trust that had been placed in me, then I wasn't liable for prosecution either way, like Childs was.

    Now, he could have handled things differently I am sure, but he might have been prosecuted either way from what I have read so far. I would like more details in an objective report on the situation.

    --
    "The first time I got drunk, I got married. The second time I bought a chimpanzee, after that I stayed sober" Arian Seid
    1. Re:If I were taking an IT Admin position... by Anonymous Coward · · Score: 2, Interesting

      It's really not that complicated... You have a boss who makes the rules, if your boss later tells you to break the rules then you do it. If someone higher up on the chain of command than your boss asks you to break a rule you might ask them to ask you formally (via your boss) but then you still do it. If your boss tells you to break a rule that he set, and security is compromised, you wouldn't be liable (as long as your have the request is documented).

    2. Re:If I were taking an IT Admin position... by SteveFoerster · · Score: 5, Insightful

      I wouldn't likely get the job, they'd hire someone who wasn't so paranoid

      That's crazy -- who wants a system administrator who isn't paranoid?

      --
      Space game using normal deck of cards: http://BattleCards.org
    3. Re:If I were taking an IT Admin position... by SanityInAnarchy · · Score: 4, Insightful

      You have a boss who makes the rules, if your boss later tells you to break the rules then you do it.

      Just like Enron's accountants?

      Sorry, no. If your boss later wants to change the rules, there's likely a procedure in place to do so, but they can't simply do that by fiat. That's the whole point of having a policy in the first place.

      --
      Don't thank God, thank a doctor!
    4. Re:If I were taking an IT Admin position... by blankinthefill · · Score: 1

      Apparently San Francisco doesn't.

    5. Re:If I were taking an IT Admin position... by RichardJenkins · · Score: 3, Informative

      I understood that they had a set of policies for 'user-level' passwords (which this was not classed as) saying things like 'never diclose your password, even to your boss' and another set of policies for 'system-level' passwords, which these passwords were classed as. The policies for 'system-level' passwords say they must be stored in a centrally managed database: a policy that Childs violated by keeping them in a way only accessible to him. Under your model (assuming the above is correct) you wouldn't be absolved from prosecution in this case, because Childs hadn't followed procedures related to 'system-level' passwords.

      It's all rather moot though, there is a systemic problem in any organisation which lets its IT be run in a way where someone can hold it hostage like this. The real lesson here is that institutional incompetence can lead to individual criminal liability.

      If you're an IT admin working in the States then it's your geographic (not professional) situation that's putting you at risk of going to jail for something stupid like this.

    6. Re:If I were taking an IT Admin position... by __aasqbs9791 · · Score: 5, Insightful

      Changing the rules isn't always the same as breaking the law. If you boss tells you to never give out passwords, and then asks you for a password, and when you refuse says he's changing that rule, it is whole different thing than your boss ordering you to break a law regarding financial accounting laws. Especially if that boss was the owner of the company (which isn't the case in either your example or Childs, of course.

      Though I've seen so many different things on this case I'm not sure where I stand. It seems to depend on the specifics. If the rules were such that it actually said he couldn't release the passwords except to the Mayor himself in person then I'm probably on his side. But otherwise someone like the Mayor likely does many things by proxy, so he may have just been acting the fool (to quote Judge Joe Brown). The devil's in the details I guess.

    7. Re:If I were taking an IT Admin position... by Darinbob · · Score: 1

      An agreement like this could not absolve you of criminal prosecution, it would only prevent (or discourage) a civil lawsuit. If a district attorney thinks you committed a crime, you can't just produce a note signed by your employer saying it's ok...

      However in some cases this is useful. Ie, if you have a work supplied laptop (lucky you), then it could be a good idea to list when you're allowed to take it home without it being considered stolen property, and how much time you have to return it after being laid off, etc.

      But passwords are not property, so there's nothing to return, especially if they only exist in your head on not on a piece of paper. I'm still baffled that you can be criminally prosecuted for not talking.

    8. Re:If I were taking an IT Admin position... by Anonymous Coward · · Score: 4, Insightful

      Just like Enron's accountants?

      If you're not comfortable doing what you're told, then quit. (Or, in the case of Enron, go to the SEC or whatever.) Even if you believe that all people have a right to a job, nobody has a right to a particular job.

      Sorry, no. If your boss later wants to change the rules, there's likely a procedure in place to do so, but they can't simply do that by fiat. That's the whole point of having a policy in the first place.

      It's a great theory, but it's also hopelessly naive. The rules don't apply equally to everyone. It sucks that the world works this way, but it does, and that's never, ever going to change. Behaving as if the rules your boss tells you apply equally to him is an exercise in frustration, and also a good recipe for getting fired. Or, as in this case, sent to jail.

      That's politics, my friend, and any time you have more than two people in a room you get politics. There is no avoiding it. Which is why policies and procedures are worthless. The people who write them can change them any time they choose. They can be enforced selectively or not at all. And you can be accused of not following a procedure, even though you did, because the person interpreting the procedure is the same person who wants to punish you for some other reason.

      Seriously, learn from my experience in corporate America. (Which, I am told, is nothing compared to the politics that goes on in public service jobs, and I'm not even talking about politicians.) This is the way the world works. The good news is that you don't have to be an active participant, and in fact taking the passive approach makes your life easier in many ways. But you do have to be aware of it, and Childs was not. Either that or he very badly overestimated his clout with the mayor (it's probably a combination of the two).

    9. Re:If I were taking an IT Admin position... by turbidostato · · Score: 2, Funny

      "if your boss later tells you to break the rules then you do it."

      Is it needed any more to invoke Godwin's law?

    10. Re:If I were taking an IT Admin position... by Darinbob · · Score: 1

      But how does "violating employer's procedures" manage to get twisted into a felonious crime in the first place? If you break procedures, the worst that should ever happen is you get fired. End of story. Now if after being fired you fail to return company property (car, mobile phone, building keys, laptop, etc) then you could be prosecuted for theft. But that is completely and totally different from not following procedures.

      Failing to follow orders is not a crime! It may be stupid, and you may be sued over it if it causes damages, but it is not a criminal offense. Breaking a contract is a civil matter, and that's the most that failing to follow procedure should be.

      Basically prosecutors are very good at finding laws that you broke if they decide that they want to keep you in jail. Since the prosecutors work for the employer in this particular instance, the employer probably said something like "I don't care what it is, find something that will stick and put that bastard in jail for making us look stupid."

    11. Re:If I were taking an IT Admin position... by westlake · · Score: 0, Flamebait

      It would absolve me from prosecution unless I violated any of the very specific rules that were listed.

      The geek isn't always very good at distinguishing between civil and criminal actions. The question then becomes prosecution by who and under what set of rules.

      The computer networks that sustain the city of San Francisco belong to the city of San Francisco. No court can allow them to be held hostage to any single individual. Not the system administrator. Not the mayor. Not anyone.

               

    12. Re:If I were taking an IT Admin position... by Nadaka · · Score: 1

      He was already fired, how can he quit for being asked to break the law? And yes, in asking for the password in the way they did, his supervisors where the ones breaking the law.

    13. Re:If I were taking an IT Admin position... by green1 · · Score: 1

      As long as the new rules don't break any laws, and everything you do complies with the rules in place, and you get all of the communications in a traceable/logable format, It's not your problem.

      If he asks for the password and there is no written law or rule that contradicts this, get him to submit the request in writing and then give it to him, if it turns out that it was a bad decision, it was HIS decision (and you can prove it) and it's not your problem.

      If you strongly disagree with his request you can advise him of why, and you can escalate it to a higher level, but in the end, it's not your decision to make, get everything in writing and you're covered if things go wrong.

      And if this sort of thing becomes routine, maybe you should consider if the company is really a good "fit" for you.

    14. Re:If I were taking an IT Admin position... by green1 · · Score: 4, Insightful

      If, after you've been fired, you refuse to disclose the passwords necessary for your successor to do your job, then it is no longer something they can simply "fire" you for, (as you no longer work there) so it becomes something you need to take to court, not "theft" in this case, but "denial of service" because his action of refusing to release the passwords denied them access to administer those systems.

    15. Re:If I were taking an IT Admin position... by amirulbahr · · Score: 2, Insightful

      You don't serve your boss. You serve the same stakeholders that your boss serves. It would be both morally and legally wrong to, for example, collude with your boss to defraud the company. The line is not as clear as GP makes out.

    16. Re:If I were taking an IT Admin position... by timmarhy · · Score: 1, Flamebait

      the owners of the equipment are asking for the password to their own gear, explain how the fuck that's breaking the law, and i want to see the section quoted as to what law it is.

      --
      If you mod me down, I will become more powerful than you can imagine....
    17. Re:If I were taking an IT Admin position... by timmarhy · · Score: 1, Troll
      i'm still baffled this idiot managed to turn a simple and reasonable request into jail time. he was sacked, why did he fucking care if they had the password, it's their system after all.

      even if it was a case of him thinking lives were in danger, he could always just claim he didn't remember them.

      --
      If you mod me down, I will become more powerful than you can imagine....
    18. Re:If I were taking an IT Admin position... by LurkerXXX · · Score: 4, Insightful

      The problem is, you want someone who is paranoid AND smart. The guy was incompetent. If you are in charge of vital machines passwords, you make sure the passwords are written down and stored in a secure location (like a bank safety deposit box, etc) and available to an authorized person in case you are hit by a bus, etc. This wasn't done. If it had been done properly, he wouldn't be facing any jail time or even charges.

    19. Re:If I were taking an IT Admin position... by bws111 · · Score: 1

      He wasn't prosecuted for not talking, he was prosecuted for denying the city access to it's own systems. Have could have prevented that prosecution by talking, but didn't. He also could have prevented prosecution by properly registering the passwords, but didn't do that either. However, there certainly are cases where you can be prosecuted for not talking. For instance, not reporting that you know a crime is planned. Or not filing a tax return.

    20. Re:If I were taking an IT Admin position... by SteveFoerster · · Score: 1

      Good point, you'll get no argument from me on that.

      --
      Space game using normal deck of cards: http://BattleCards.org
    21. Re:If I were taking an IT Admin position... by fractoid · · Score: 1

      If someone higher up on the chain of command than your boss asks you to break a rule you might ask them to ask you formally (via your boss) but then you still do it. If your boss tells you to break a rule that he set, and security is compromised, you wouldn't be liable (as long as your have the request is documented).

      This is excellent advice. As long as it's clear that you're acting under orders at all times, and what you're doing is legal, you take no personal liability. You can do it under protest if you think it's stupid or destructive, but if your boss says "switch that power supply from 240v mode to 110v mode" then in the end, he takes responsibility for the resulting loud bang.

      Of course, you still have to obey the law. You can't steal a car or kneecap someone and then get off with "da boss says do it, so I do it". More relevantly, you can't withhold data or property from the police if they have the proper warrant. If I had sole access to vital infrastructure, and a government official or law enforcement agent wanted me to give them access, I'd take the issue to my boss and let them duke it out. If I *was* that boss, then I would take the issue to a lawyer to see whether I could legally withhold the information. That's what the chain of command (and ultimately, legal consultation) is for - to make, and take responsibility for, high level policy decisions.

      --
      Rampant carbon sequestration destroyed the Dinosaurs' tropical paradise. I'm here to help repair the damage.
    22. Re:If I were taking an IT Admin position... by PopeRatzo · · Score: 0, Flamebait

      think I would want to draft up a very clear - and legally binding - agreement that I would want my superiors in management to sign on behalf of the company.

      Better still, sysadmins need to get unionized.

      Then, employers at least have to think twice before fucking with you. Until they do organize, they're not going to be treated as well as waste disposal workers (garbage men).

      But that would require sysadmins to be able to work together for a common good, and sysadmins generally don't like to work with anyone, especially other sysadmins.

      --
      You are welcome on my lawn.
    23. Re:If I were taking an IT Admin position... by celle · · Score: 2, Insightful

      "the owners of the equipment are asking for the password to their own gear"

      They are not the owners of the equipment, the public is or their representative -- the currently elected jackass of the week. I would guess that's the mayor. Childs called it right. Childs bosses are under the same policy as Childs and don't have the authority to change it without following standardized procedures from their higher ups and letting Childs know about it and acknowledge the change.

    24. Re:If I were taking an IT Admin position... by Vellmont · · Score: 4, Insightful


      That's crazy -- who wants a system administrator who isn't paranoid?

      I don't want system administrators who are paranoid. I want system administrators who understand what risk is, what the real risks are, and are able to weigh one risk against another. Being paranoid usually entails the inability to weigh risks, since you think "everyone is out to get me". Anyone who can't weigh risks against another is a fool.

      --
      AccountKiller
    25. Re:If I were taking an IT Admin position... by SteveFoerster · · Score: 1

      You're absolutely right. But I was actually trying to be funny, and "risk management" wasn't as catchy a punchline. :-)

      --
      Space game using normal deck of cards: http://BattleCards.org
    26. Re:If I were taking an IT Admin position... by Zerth · · Score: 2, Informative

      And when the person replacing him mucked things up, do you think they might not assume he sabotaged things?

      Considering the ineptitude the new staff has shown, I can see why he would have been concerned.

    27. Re:If I were taking an IT Admin position... by slick7 · · Score: 1

      There seems to be more to this than we are led to believe.
      Political issues in the workplace never look at both sides equally.
      In time the truth will be out.

      Time wounds all heels.

      --
      The mind conceives, the body achieves, the spirit manifests.
    28. Re:If I were taking an IT Admin position... by darkpixel2k · · Score: 1

      If, after you've been fired, you refuse to disclose the passwords necessary for your successor to do your job, then it is no longer something they can simply "fire" you for, (as you no longer work there) so it becomes something you need to take to court, not "theft" in this case, but "denial of service" because his action of refusing to release the passwords denied them access to administer those systems.

      If I am fired, and then my boss realizes that he hasn't taken the proper steps (not saying this is the case with Childs) of making policies for documenting configurations and/or passwords, along with providing time during work-hours to document that information, he doesn't get them. I'm fired after all, and he doesn't get my free labor. I will be happy to provide him with the information though at my contracting rate of 1.5 times my normal pay.

      --
      There's no place like ::1 (I've completed my transition to IPv6)
    29. Re:If I were taking an IT Admin position... by HungryHobo · · Score: 1

      Of you can get stuck between a rock and a hard place where the company rules say you can't give your password to your superior, your superior want it and if you give it to them then you're handing out access credentials to unauthorized people(possibly illegal) or denying access(possibly illegal)

    30. Re:If I were taking an IT Admin position... by jgreco · · Score: 3, Insightful

      Which is where this gets all goofy; he's already been fired, but he's expected to do *work* for them, in the form of enumerating passwords and associating them with what systems they're for and how to use them and how to get access to the systems in order to use them, etc.? Documentation of that sort could be very lengthy and quite a bit of work to write up.

      If he had gone out binge drinking and incapacitated himself for a day after being fired, would this be considered "denial of service?"

      If the city wished to be able to have unimpeded access to their network after firing the person who apparently held the only set of electronic master keys to the system, why wasn't it their responsibility to make sure that they had those keys - before firing him?

      There are multiple failures on both sides of this issue, but in the end, the city (a large entity that presumably has many lawyers and expertise in dealing with human resources) has punished the employee (an individual who appears to be eccentric but probably harmless, and probably less-than-fully-informed about the legal aspects to it all). When considering the city vs the individual, the city had all the resources, but royally screwed the pooch, and yet it's still the individual left picking up the tab.

      His boss should be the one heading to jail.

    31. Re:If I were taking an IT Admin position... by darkpixel2k · · Score: 3, Insightful

      It would absolve me from prosecution unless I violated any of the very specific rules that were listed.

      The geek isn't always very good at distinguishing between civil and criminal actions. The question then becomes prosecution by who and under what set of rules.

      The computer networks that sustain the city of San Francisco belong to the city of San Francisco. No court can allow them to be held hostage to any single individual. Not the system administrator. Not the mayor. Not anyone.

      Really? What if you boss says 'setup that new server' and you say 'Yes sir'. You follow the standard practice of giving it a secure password because it's connected to the internet. Then you say to your boss "We really need a place to document the password". Your boss gives you no reply and immediately sends you out to your next assignment. There's also no formal documentation system in your organization. After a few weeks of being scheduled on assignments non-stop from 8 AM until 5 PM, you get fired. Whose fault is it that your boss doesn't know the password? Should you be required or forced to work for free for a few hours to cough up passwords because of a failing of your boss?

      --
      There's no place like ::1 (I've completed my transition to IPv6)
    32. Re:If I were taking an IT Admin position... by jedidiah · · Score: 2, Insightful

      > You have a boss who makes the rules, if your boss later tells you to break the rules then you do it.

      Except it isn't quite like that.

      Whenever I see one of these "Mad Max" style posts, I wonder if these people have ever been employed anywhere.

      In all likelihood, your boss doesn't create policy. He enforces it just like you do. He doesn't make the
      rules either. He also doesn't get to break them arbitrarily.

      Piss off the boss or break the rules? That's certainly a dilemma to show what kind of man you are.

      --
      A Pirate and a Puritan look the same on a balance sheet.
    33. Re:If I were taking an IT Admin position... by fractoid · · Score: 2

      In that case you simply take it up the food chain. Transparency is your best friend. Your boss is demanding a password that your standard operating procedure says you're not allowed to give him? Ask for a meeting between you, your boss, and his boss. Explain the situation and ask for authorisation. Keep going up the hierarchy until you're talking to someone who has the authority to override the rule which is preventing you from giving out the password. Then, if they say to do it, they take responsibility. If they say *not* to do it, they STILL take responsibility.

      --
      Rampant carbon sequestration destroyed the Dinosaurs' tropical paradise. I'm here to help repair the damage.
    34. Re:If I were taking an IT Admin position... by BitterOak · · Score: 1

      If, after you've been fired, you refuse to disclose the passwords necessary for your successor to do your job, then it is no longer something they can simply "fire" you for, (as you no longer work there) so it becomes something you need to take to court, not "theft" in this case, but "denial of service" because his action of refusing to release the passwords denied them access to administer those systems.

      Fine. Take them to court in a civil suit, asking the judge to order the employee to give up the passwords. Why does it need to be a criminal case? Why does someone need to go to jail over a password dispute? Even if Mr. Childs was in the wrong (and I don't know enough about the case to make that determination either way) I don't see why failure to disclose passwords to your boss should be a crime, especially when there was some ambiguity surrounding the correct security policy. I don't think there was any malicious intent on Mr. Childs' part, at worst it was poor judgment or a misinterpretation of security policy.

      --
      If I can be modded down for being a troll, can I be modded up for being an orc, or a balrog?
    35. Re:If I were taking an IT Admin position... by Anonymous Coward · · Score: 0

      what if you forget. It's bullshit. you shouldn't even have to answer to your former employer.

    36. Re:If I were taking an IT Admin position... by Vellmont · · Score: 5, Insightful

      I guess I don't find it funny because I know paranoid system administrators, and they do indeed suck at what they do.

      --
      AccountKiller
    37. Re:If I were taking an IT Admin position... by ImNotAtWork · · Score: 2, Insightful

      Child's may have called it right but he should have used his attorney, if he even used one, more strategically the moment he was arrested. Everything should have been proxy-ed(sp?) through his attorney. Or his attorney just grossly mismanaged access to his client. IANAL but I can see the obvious.

      --
      open source sub sim. I might start coding again for this. http://dangerdeep.sourceforge.net/contribute/
    38. Re:If I were taking an IT Admin position... by timmarhy · · Score: 0, Troll

      Child's boss is a public servant delegated the job by the mayor. that's how government works. what you think the mayor handles everything personally? how much more of a thinking fail can you have...

      --
      If you mod me down, I will become more powerful than you can imagine....
    39. Re:If I were taking an IT Admin position... by Idiomatick · · Score: 0, Troll

      Maybe... but they had access to the machines... so he wasn't really fucking them over. Even an incompotent IT guy would know that it isn't a big deal.

    40. Re:If I were taking an IT Admin position... by timmarhy · · Score: 1, Troll

      your all missing the point by a wide margin. if someone else screws up, why would child's care. if you read into the story you'll actually see the guy was a fucking control freak, that was his only concern.

      --
      If you mod me down, I will become more powerful than you can imagine....
    41. Re:If I were taking an IT Admin position... by Anonymous Coward · · Score: 0

      It may be just me, but if I get fired from a job and THEN my ex-boss would call up and demand I do my job or disclose any other information that was part of my job, I'd hang up. If I've been fired, that means my ties to that company were severed. So long and thanks for all the fish. (barring any signed NDAs or the like, of course.)

      It's the boss's / company's fault for not asking the passwords/other information BEFORE firing the guy. Stupid is as stupid does, but you should NOT be able to sue someone else on the account of YOU being dumb.

    42. Re:If I were taking an IT Admin position... by yuna49 · · Score: 2, Insightful

      It's really not that complicated... You have a boss who makes the rules, if your boss later tells you to break the rules then you do it.

      Or you resign.

    43. Re:If I were taking an IT Admin position... by yuna49 · · Score: 1

      That's politics, my friend, and any time you have more than two people in a room you get politics.

      The Marquis de Condorcet, Lewis Carroll, Duncan Black, Anthony Downs, Kenneth Arrow, and William Riker would be thrilled to hear you say that! Things get even more interesting when you have more than two alternatives among which to choose!

    44. Re:If I were taking an IT Admin position... by Anonymous Coward · · Score: 0

      That isn't entirely true. Those passwords can be reset.

    45. Re:If I were taking an IT Admin position... by Nyder · · Score: 1

      If, after you've been fired, you refuse to disclose the passwords necessary for your successor to do your job, then it is no longer something they can simply "fire" you for, (as you no longer work there) so it becomes something you need to take to court, not "theft" in this case, but "denial of service" because his action of refusing to release the passwords denied them access to administer those systems.

      Seems to me the boss should get the passwords before he fires the person.

      --
      Be seeing you...
    46. Re:If I were taking an IT Admin position... by julesh · · Score: 1

      I think I would want to draft up a very clear - and legally binding - agreement that I would want my superiors in management to sign on behalf of the company. It would spell out in specific details, the security policies, security review process, enforcement etc.

      A contract cannot override legislation. If the legislation is badly designed, there is nothing that can be done about this except changing the legislation. As I understand it, Childs did have written procedures and did follow them. My reading of the situation is that the problem is that he was expected to apply common sense that when the organization of the layers of beaurocracy above him changed and he started receiving instructions via a superior in a different department that he should actually follow them, rather than ignore them as against written policy. It seems he understood that the person giving him the instructions was authorized to do so by somebody directly superior to him, but refused on the basis that the person wasn't on the specific list of people who had the authority. The written policy was out of date, based on an old structure, and he was expected to adapt rather than stick to it.

    47. Re:If I were taking an IT Admin position... by jimicus · · Score: 3, Insightful

      Agree entirely. From what little we've heard, it sounds like there was plenty of opportunity for Childs to avoid this. On several occasions he was asked to divulge the passwords and like a petulant child he just kept saying "No. Want the mayor".

      While I don't have any inside knowledge of the case, it seems to me the sensible thing to do would have been to explain to his lawyer the quandary (give the passwords : criminal offence, don't give the passwords : criminal offence) and have the lawyer whip up some sort of agreement whereby the passwords could be handed over and Childs would be let go with no further action. Hell, by all accounts he was offered almost exactly this opportunity by the police - so it's not like it never occurred to anyone.

    48. Re:If I were taking an IT Admin position... by jimicus · · Score: 1

      If I am fired, and then my boss realizes that he hasn't taken the proper steps (not saying this is the case with Childs) of making policies for documenting configurations and/or passwords, along with providing time during work-hours to document that information, he doesn't get them. I'm fired after all, and he doesn't get my free labor. I will be happy to provide him with the information though at my contracting rate of 1.5 times my normal pay.

      In that case, not only are you denying access to their systems but your are implicitly admitting that you can still give them access to their systems (you're happy to provide him the information, therefore we can safely assume you have it) and using extortion (you want to be paid - and paid more than you otherwise would have earned) to rectify the situation.

      IANAL but if your former employer is of a mind to report you to the authorities I really can't see that ending well.

    49. Re:If I were taking an IT Admin position... by Aceticon · · Score: 2, Interesting

      I think the overall issue is that you can't take an IT Admin position working for the a Local, State or Federal public entity in the US since you're damned if you do (give the passwords) because of laws and regulations and damned if you don't since they'll take you to court and have you convicted anyway.

      Either stay away from those positions or ask for a significant premium on your salary/rate to cover the legal risk.

    50. Re:If I were taking an IT Admin position... by fredmosby · · Score: 1

      Documentation of that sort could be very lengthy and quite a bit of work to write up.
      That assumes he didn't already have the passwords written down somewhere. If we're talking about more that a small number passwords I seriously doubt he memorized all of them.

      ...has punished the employee (an individual who appears to be eccentric but probably harmless...
      You must mean besides the harm he's already done.

      His boss should be the one heading to jail.
      For not checking to make sure the passwords were in their possession before firing an employee? That doesn't sound like a felony to me.

    51. Re:If I were taking an IT Admin position... by SlashDread · · Score: 2, Insightful

      The paranoid ones arent neccisarily good, but the good (security) admins are paranoid.

    52. Re:If I were taking an IT Admin position... by nosferatu1001 · · Score: 1

      Sounds like criminal negligence to me to NOT have your critical system passwords stored independently of the ONE person in charge of the systems.

    53. Re:If I were taking an IT Admin position... by zippthorne · · Score: 2, Insightful

      People were asking for the passwords. People who may even have had the authority to have them. However the only person who Terry was certain legitimately represented the owners that he would be able to identify was the Mayor, to whom he gave the passwords.

      How hard is this to understand? I guess very, since it seems Terry has had a difficult time explaining it, or assuming it was obvious.

      --
      Can you be Even More Awesome?!
    54. Re:If I were taking an IT Admin position... by Anonymous Coward · · Score: 0

      Which is where this gets all goofy; he's already been fired, but he's expected to do *work* for them, in the form of enumerating passwords and associating them with what systems they're for and how to use them and how to get access to the systems in order to use them, etc.? Documentation of that sort could be very lengthy and quite a bit of work to write up.

      Oh, come on. Telling your former employer what the passwords are when you're fired is "work" just as much as returning your keys is under the same circumstances.

      Long write-ups may be a different issue, but that's not what we're talking about, is it? Again, when you give back your keys, you don't provide a detailed list of which key is for which lock, either: you just hand them back. Similarly, when your former boss asks "what's the root password for the servers" so he can give it to the next IT admin guy, you don't write a comprehensive document detailing how to administrate these systems. You merely hand out the password.

      Childs may have been right not giving the password to anyone while he was still employed. Afterwards, what he did was petty and unnecessary, and he's got only himself to blame for his trouble.

    55. Re:If I were taking an IT Admin position... by jgreco · · Score: 3, Interesting

      If you've never built a large network, it's easy to underestimate what I'm saying. It's not just the passwords, but also how to use them. This isn't like sitting down in front of a Linux box and logging in. It probably includes needing to know the topology of the network, such as "if jonesville router 1a is down, its console is connected to the aux port on jonesville router 1b, but to get to that when the routing protocol has imploded, you might need to first dial in to the out-of-band modem on barton router 2a, ssh over to barton router 1b, then use the link address of jonesville router 1b to ssh to, then connect up to the console port."

      As for harm, what actual harm did he actually do? Did he down the entire network? Did he allow criminals access to their network? Take a look at the "harm" claimed and see what portions of it you can actually attribute to him INSTEAD of the city.

      His boss can head to jail for the very same reason he is; his boss caused denial of service by failing to guarantee that the city had unimpeded access to the network. What's good for the goose is good for the gander and all that.

    56. Re:If I were taking an IT Admin position... by Anonymous Coward · · Score: 0

      The hit by a bus policy doesnt nessicarily mean having to write your admin passwords down, it just means having someone that can recover it incase you are hit by a bus. Moreover the city should have saw to it that some one had administrator before they completey terminated him. its a lose lose deal

    57. Re:If I were taking an IT Admin position... by Assmasher · · Score: 2, Funny

      Ahhh... The Nuremberg defense.

      --
      Loading...
    58. Re:If I were taking an IT Admin position... by cowboy76Spain · · Score: 1

      He would not be working, he would be returning the access to the systems to his ex-employer. Just like returning a work cell phone or laptop.

      --
      Why can't /. have a rich-text editor? Editing your own HTML is so XXth century.
    59. Re:If I were taking an IT Admin position... by HungryHobo · · Score: 1

      So just to be safe you'd probably be safest to go all the way to the top of the food chain.
      Just to be safe and certain that the person in question has the authority required.

    60. Re:If I were taking an IT Admin position... by tibman · · Score: 1

      I think this is the best answer. But if the cops are called before you can get a meeting, you could be forced into Childs' situation.

      --
      http://soylentnews.org/~tibman
    61. Re:If I were taking an IT Admin position... by jgreco · · Score: 1

      Again, what duty to your EX-employer do you have?

      A work cell phone or laptop is physical property, easily and trivially returned. It is entirely unlike data, which can be copied. The laptop has to be in the employee's hands in order to be useful, and by definition must be out of the employer's possession in order to be used. Further, in many places, all you do for laptop or cell phone is confiscate them as the employee is being escorted out, or let them know that their final paycheck will be docked for the replacement amounts if they fail to return the items.

      So let me give you a more comparable situation.

      You're working for the hottest game manufacturer on the planet, because they saw some promise in your skills and you had some great ideas about how to implement the engine for their next jewel. One day, your employer finds you are spending most of your working hours surfing porn on the Internet. Angry, your boss fires you. Then he realizes that the product he's tasked with developing is reliant on the game engine, and that with you gone, so is the expertise to finish development of the game engine. So he ...

      1) Is out of luck because he fired your sorry butt?

      2) Should take you to court and sue you to produce the information in your head?

      This is not meant to be a strict parallel to the Childs case, but rather an example of how this is not a trivial case. This sort of stuff happens all the time, by the way, and the normal answer is generally "none of the above." It's usually

      3) Offer to hire you on as a temp contractor, generally at insane rates, for the hours needed in order to get a coherent brain-dump.

      In this case, though, it sounds like 3) would not have worked. What they probably should have done is:

      4) Sucked it up, paid a few experts to start walking through the system node-by-node, resetting everything to a known state. There are always plenty of out-of-work network jocks.

    62. Re:If I were taking an IT Admin position... by pizzap · · Score: 1

      It's really not that complicated... You have a boss who makes the rules

      Not everybody has a boss. Especially in large government organizations it might be difficult to find your boss. If you're a department head, or project lead it's more a question of who is in charge of what.
      In a complex organizational structure sub-systems often fight against each other for control of key infrastructure and personnel.

    63. Re:If I were taking an IT Admin position... by Lunix+Nutcase · · Score: 1

      If I am fired, and then my boss realizes that he hasn't taken the proper steps (not saying this is the case with Childs) of making policies for documenting configurations and/or passwords, along with providing time during work-hours to document that information, he doesn't get them. I'm fired after all, and he doesn't get my free labor. I will be happy to provide him with the information though at my contracting rate of 1.5 times my normal pay.

      You do realize that is extortion and you'd be in a whole mess of shit for doing so, right?

    64. Re:If I were taking an IT Admin position... by david_thornley · · Score: 2, Interesting

      The boss can change the rules the boss makes, within limits imposed by law and corporate policy. There may be rules from higher up that your boss must obey. For example, if corporate policy is that nobody tells anybody else their password, the boss has no right to demand your password.

      Now, if you're in a position where your boss demands something that's either illegal or against corporate policy, after you've explained it, you've got a problem. I'd probably ask for the request in writing. That may not be the correct thing to do politically, but I'm not all that good at office politics. Other people may have better ideas.

      --
      "When you have eliminated the unacceptable, whatever is left, however improbable, must be the truthiness" - Holmes
    65. Re:If I were taking an IT Admin position... by Anonymous Coward · · Score: 0

      Since you pretty much say that keeping data isn't theft, what if an employee working for Microsoft or Apple or any large development house has an employee who makes a copy of their entire source repository, and takes it home so he can "find ideas."

      Since you have no duty to your ex-employer, what is to stop you from showing that repository to someone else...

    66. Re:If I were taking an IT Admin position... by Golddess · · Score: 1

      And if the POTUS asks you to break the law, you do it.

      Wait, what?

      --
      "I'm not sure I like the fugnutish tone you used in your post!" -RogL (608926)-
    67. Re:If I were taking an IT Admin position... by jgreco · · Score: 1

      That, again, is different. In the case of passwords, short of getting out a scalpel and cutting out sections of your brain, there's no way NOT to "keep the data." I still remember passwords from many years ago. None of them do me any good and there is no value to me remembering them, but I remember them regardless.

      Do you forget who your co-workers were, what their e-mail addresses were, where they sat, what their phone extensions were, etc., just because you leave your job? Do you need that data? Can you voluntarily forget it?

    68. Re:If I were taking an IT Admin position... by GooberToo · · Score: 1

      In that case, not only are you denying access to their systems but your are implicitly admitting that you can still give them access to their systems

      Or you can argue THEY created an environment whereby THEY ensured the inability to administrate their own systems whereby then are then demanding free labor to satisfy the requirements they refused to pay for in the first place.

      At the end of the day, the city is clearly negligent and/or incompetent.

    69. Re:If I were taking an IT Admin position... by darkpixel2k · · Score: 1

      In that case, not only are you denying access to their systems but your are implicitly admitting that you can still give them access to their systems (you're happy to provide him the information, therefore we can safely assume you have it) and using extortion (you want to be paid - and paid more than you otherwise would have earned) to rectify the situation.

      IANAL but if your former employer is of a mind to report you to the authorities I really can't see that ending well.

      There is nothing extortionate about requiring payment for services. If your former boss called you up and said "Hey--can you come in this weekend and help us move office furniture?", would you do it for free? No. If my boss failed to provide time for documenting important information, a policy, and/or a system for documenting the information, that's his problem. If I am required after being fired to do a job he should have done, I will be asking for payment. And no, not thousands of millions of dollars (which would be extortionate), but simply my regular overtime rate.

      --
      There's no place like ::1 (I've completed my transition to IPv6)
    70. Re:If I were taking an IT Admin position... by darkpixel2k · · Score: 1

      You do realize that is extortion and you'd be in a whole mess of shit for doing so, right?

      You do realize that people have a right to be paid for their labor?

      I'm not talking about charging thousands or millions of dollars for giving them passwords, but I am talking about getting paid my normal overtime rate to document information that should have been required by policy. I have worked in a place where they were so 'busy' trying to get the 'next big project' finished that they completely skipped the part about documenting the servers and systems from the previous project. That's not my fault, and to ask me to do it for free would be wrong.

      Like I said, I'm not charging $50,000 for a password--that would be extortionate. It it literally takes me 25 minutes to write down all the passwords I can think of, I'm billing them for 25 minutes of my time.

      --
      There's no place like ::1 (I've completed my transition to IPv6)
    71. Re:If I were taking an IT Admin position... by Coren22 · · Score: 1

      "Password Policy"
      As such, all County employees (including contractors, vendors, and temporary staff with access to County systems) are responsible for taking the appropriate steps, as outlined below, to select and secure their passwords.
      All system-level passwords (e.g., root, enable, NT admin, application administration accounts, etc.) must be changed on at least a monthly basis"
      "Do not share County passwords with anyone, including administrative assistants or secretaries.

      All passwords are to be treated as sensitive, confidential County information.

      Here is a list of things to avoid
      -Telling your boss your password.
      -Talking about a password in front of others.
      -Telling your co-workers your passwordwhile on vacation."

      http://www.sfgov.org/site/uploadedfiles/dtis/coit/Policies_Forms/CCISDA_security.pdf

      --
      APK likes to ask for responses to the same things over and over. Maybe he just likes the responses?
    72. Re:If I were taking an IT Admin position... by Zerth · · Score: 1

      Having read what Chilton(the juror posting here) has said about it, I can agree that Childs completely screwed up. Regardless of what I feel about the ineptitude of the rest of the City employees, he handled this badly.

      Guess the Reiser Rule came true here. Give a geek the benefit of the doubt and he'll probably have committed the crime.

    73. Re:If I were taking an IT Admin position... by Coren22 · · Score: 1

      I have heard it said previously, but have not seen any sources for it. Supposedly there was a password database, but Childs was let go between changing the passwords and the database getting updated.

      --
      APK likes to ask for responses to the same things over and over. Maybe he just likes the responses?
    74. Re:If I were taking an IT Admin position... by berashith · · Score: 1

      except the gander has a better lawyer.

    75. Re:If I were taking an IT Admin position... by Anonymous Coward · · Score: 0

      Oh come on all you babies. They guy deliberately locked up the whole IT system on purpose.

      He didn't follow orders to give up the password and/or unlock the systems, and the only thing that convinced him to do so was some time in a jail cell.

      Showing support for this guy merely exposes your technological bigotry.

    76. Re:If I were taking an IT Admin position... by Anonymous Coward · · Score: 0

      You never know. Maybe his "will" had the passwords in it.
      Sounds like something a paranoid person would do.

    77. Re:If I were taking an IT Admin position... by Lunix+Nutcase · · Score: 1

      You do realize that people have a right to be paid for their labor?

      You have no right to lock the owner of the system out of his property and then hold it ransom and demand payment to unlock it.

      Like I said, I'm not charging $50,000 for a password--that would be extortionate.

      No, it would still be extortion no matter what you were charging. If you think such an argument would hold up in court, you are either extremely ignorant or stupid. The only thing you'd be winning is a one-way ticket to Federal Pound-me-in-the-ass prison.

    78. Re:If I were taking an IT Admin position... by sjames · · Score: 1

      It sounds a lot more like a civil matter to me. Sue them, not prosecute.

      Of course, the correct procedure is to implement a continuity policy where key passwords are sealed into envelopes to be opened by your successor should you be hit by a bus. For fairness, if the envelope is ever missing or opened, the admin is not to be held responsible for any resulting problems. (Of course, passwords should be changed and a new list sealed in an envelope). Ideally though, nobody should bear sole responsibility for a system. There should always be at least two, each of whom has the password. That might not work for a small company, but surely a city IT department has enough people for that.

      Too often, what happens is something needs to be kept reasonably secret and secure and suddenly people get carried away with their frustrated 007 fantasies from childhood and start treating the admin password for the receptionist's PC like nuclear launch codes. This leads to procedures designed for security at any cost, including routers with no saved configuration and passwords not written down, even in a sealed envelope in a safe.

      There are two sides of security and only one gets any attention. We all know the part about making sure that unauthorized people can't access a system. The other part is making sure a duly authorized person CAN access the system.

    79. Re:If I were taking an IT Admin position... by Dragoness+Eclectic · · Score: 1

      No, bunion-head, the 13th Amendment supercedes any and all "denial of service" laws. You CANNOT force a person to work for free. Period.

      --
      ---dragoness
    80. Re:If I were taking an IT Admin position... by sjames · · Score: 1

      Changing the rules isn't always the same as breaking the law. If you boss tells you to never give out passwords, and then asks you for a password, and when you refuse says he's changing that rule, it is whole different thing than your boss ordering you to break a law regarding financial accounting laws.

      Unless, of course, that password would allow your boss to have administrative access to BOTH audit logs. So sometimes changing the rules IS breaking the law. It's a bit grayer when you merely know he's a blabbermouth and golfs regularly with the people who already have legitimate access to the other audit log.

      Either way, if the boss isn't willing to change the written rules in writing, it's never a good thing.

      Unfortunately, the jury has done a fine job of closing up the last little escape hatch for a perfect Catch 22. Law enforcement, especially at the federal level has made it clear they are willing to go after people under orders from above (sometimes as scapegoats where the people above mysteriously avoid consequences for the orders they gave) the police don't want to hear about your boss's policy violation until after everyone is incriminated and now you can be prosecuted for taking your marbles and going home too.

      Note that I'm fairly sure Childs' handling of the situation was far from ideal, but being socially and politically awkward isn't supposed to be a crime.

      Personally, when I am asked to transfer administrative authority, I write the password down along with a note urging that it be changed immediately. I keep a copy of the note for myself with the password blacked out. I then delete any copy of that password I might have. The note is handed over to the highest person in the hierarchy I work with for distribution to my successor.

    81. Re:If I were taking an IT Admin position... by flibuste · · Score: 2, Insightful

      It's really not that complicated... You have a boss who makes the rules

      Oh yeah. With your logic, here is a small sample of what can happen and the sweet consequences that follow.

      • 1939-1945, and the extermination camps.
      • Vietnam and the killing of hundred thousands of innoncent farmers by 'enlightened people' from some political party.
      • CIA contractors and US soldiers in Guantanamo, and waterboarding.

      I reckon my examples are a little extreme, but the sheep mentality such as yours causes more troubles than it solves problems.

    82. Re:If I were taking an IT Admin position... by westlake · · Score: 1
      it seems to me the sensible thing to do would have been to explain to his lawyer the quandary (give the passwords : criminal offence, don't give the passwords : criminal offence) and have the lawyer whip up some sort of agreement whereby the passwords could be handed over and Childs would be let go with no further action.

      The job of a judge looking at a case "in equity" is to find a fair and workable solution to problems where pride and pedantry get in the way of common sense.

    83. Re:If I were taking an IT Admin position... by MikeBabcock · · Score: 1

      Good thing you're A/C. I'd put your name on my do-not-hire list.

      Go work for a spammer. They'd appreciate your work "ethic".

      --
      - Michael T. Babcock (Yes, I blog)
    84. Re:If I were taking an IT Admin position... by westlake · · Score: 1

      Which is where this gets all goofy; he's already been fired, but he's expected to do *work* for them

      Is this really all that goofy -

      or are there other jobs in other industries where termination is as much a process as a singular event:

      On-going cases or projects that need to be formally closed or transferred. Company property that needs to be inventoried and returned, and so on.

    85. Re:If I were taking an IT Admin position... by jgreco · · Score: 1

      Generally speaking, if projects or cases need to be formally transferred, you do that process by hiring the replacement *first* and then having the process proceed for a week, month, or even a year - while the soon-to-be-ex-employee is still working. Labor laws do not make an exemption for this. Further, if you're my employer and you tell me you're outsourcing my job to India, and I can expect that my next six months of employment will consist of the process of transferring, there is very little that you can do if I wish instead to give my two weeks notice and say that I've been feeling the urgent need for a vacation for some time.

      Returning company property is a ten minute affair, and the last time you did it, you were probably still on the clock. Transferring the accumulated knowledge of a project is generally a lot more, at least for any high value employee. That's why it's Real Super Important for management to make sure that documentation is generated as the project proceeds. You never know when Terry Childs will be hit by an out-of-control bus or other catastrophe.

    86. Re:If I were taking an IT Admin position... by jimnorcal · · Score: 1

      That's crazy -- who wants a system administrator who isn't paranoid?

      Apparently the city of SF does.

    87. Re:If I were taking an IT Admin position... by darkpixel2k · · Score: 1

      You do realize that people have a right to be paid for their labor?

      You have no right to lock the owner of the system out of his property and then hold it ransom and demand payment to unlock it.

      There is a difference between actively locking an owner out of a system by going in, changing passwords, refusing to document them, and holding them hostage for money.

      If my boss doesn't have a documentation system for tracking this information, and refuses to give me time to document the system--that's not my fault. He has made a choice to lock himself out of the system. I do what my boss says. If he says "There's no time for that now, get on to the next assignment." I do it. If he fires me, he's not my boss anymore. If he asks me for a password after I'm fired, he's not my boss anymore--but I'd be glad to be a temporary employee (at time-and-a-half) and work for him again and give him the password.

      No, it would still be extortion no matter what you were charging. If you think such an argument would hold up in court, you are either extremely ignorant or stupid. The only thing you'd be winning is a one-way ticket to Federal Pound-me-in-the-ass prison.

      You can NOT force someone to work without pay, that's slavery. The courts may indeed decide to send people to prison over that--but it doesn't make it 'right'. The courts use to allowed slavery in this nation. Was it right? No.

      --
      There's no place like ::1 (I've completed my transition to IPv6)
    88. Re:If I were taking an IT Admin position... by Cramer · · Score: 1

      Umm, no. According to city policy docs, there was/is a "system access" password database. However, Childs reportedly never put any FiberWAN passwords in the system (certainly not correct ones at any rate.) And he openly refused to give anyone else access -- it's this part that has him on the way to prison. After being locked up, he agreed to give his password only to the mayor in person. (likely the only compromise his lawyer(s) could get him to agree to.)

    89. Re:If I were taking an IT Admin position... by Cramer · · Score: 1

      What part of return ALL city property do you not understand? The system passwords ARE city property as much as printed network diagrams, business cards, cellphones, etc. Passwords may not be something that can be returned in the same maner as a cellphone, but that doesn't make them any less of an asset.

    90. Re:If I were taking an IT Admin position... by jgreco · · Score: 1

      What part of "this is a dispute about who was authorized, by the city's own policy, to receive those assets" do you not understand?

      You don't hand your cellphone and laptop to the cleaning guy as you're departing the building.

      Further, the whole point here is that this is a catastrophic management failure. An employee was allowed to build this thing that only he had keys to, and management just sat around. Apparently not managing anything.

      Being reliant on an employee to "return" your "asset" if you suddenly decide you want it does you no good if the employee has been killed by a runaway bus, is simply forgetful, or gets into a disagreement about who's authorized. Any competent IT department has policies and procedures in place to handle this sort of thing.

    91. Re:If I were taking an IT Admin position... by sldghmr · · Score: 1

      Only thing I know for sure related to this story is I wont be applying for Terry's old job. Seems like a bad case of the Bob's over there.

    92. Re:If I were taking an IT Admin position... by Cramer · · Score: 1

      He wasn't handing over anything to the "cleaning guy". He was asked to give other people access. He was asked to hand over his access (as it was the only one) and refused. On a phone call with God knows who listening, sure, respectfully decline and hand them over in person to known people. If the COO (boss's boss who does get to say who is authorized) asks for the passwords with HR and police in the room, refusing is a bad idea. And there's nothing to suggest he was being ordered to reveal sensitive information to anyone other than the COO -- i.e. write the passwords down and hand them to the COO. After all, that's exactly what he did with the mayor.

      the whole point here is that this is a catastrophic management failure

      Yes. Yes, it is. He doesn't deserve to be a felon or spend years in jail. The city managers should be taking some of the heat for letting this mess happen in the first place. Specifically, his boss played into his ego by letting him be the network god. I can see Childs' side... the network is his creation; he's put a lot of time an energy into it, and doesn't want to see it ruined. He sees the "reassignment" as a prelude to firing him, and knows they cannot do that while he holds all the cards.

      Paranoia. Panic. And a change in the free rein he's had for years. "caused him to panic into error", to quote The Princess Bride.

  2. Not trying to be a troll here, but... by andrewme · · Score: 4, Insightful

    Not trying to be a troll here, but... and maybe I'm not understanding the whole case correctly. I've followed the articles on Slashdot for a while. In my opinion: if the city hires you, you are subservient to the city. You do not give passwords to your inferiors. Ever. You do, however, give passwords to your superiors when asked. Always. They hired you, after all. They are your bosses. If I hire a security guard for my building, he'd damn well better give me the key if I decide to fire him, or if I get locked out, or both. You don't hide data from your superiors, plain and simple, however *technologically* less advanced they might be. Maybe the city is making a mountain out of a molehill; I'm really not qualified to comment on that, since I don't know as much about the case as some of the people on here will. Honestly, though, my original point: you get hired by someone, you do what they want to do, provided it isn't illegal. I highly doubt that giving someone the password or passwords to their own systems would have been the wrong thing to do.

    1. Re:Not trying to be a troll here, but... by Monkeedude1212 · · Score: 3, Informative

      The only Superior he was supposed to give the password to is the Mayor. He was only supposed to do that in an environment deemed secure enough for no one else to get the password. He complied with that. He is basically being sued into oblivion because he didn't want the secretary, the press, and/or anyone else getting a hold of the password.

    2. Re:Not trying to be a troll here, but... by George+Beech · · Score: 4, Insightful

      No that's a twist on what happened to suit the ideas of slashdot. What happened was he was locked up and said "I'll only give these passwords to the Mayor" Now what he was required to do by the state policy was provide the passwords to Information Security for inclusion in the central password management database due to them being production passwords. He obviously did not do this as none of this would have happened if he did.

    3. Re:Not trying to be a troll here, but... by blair1q · · Score: 3, Insightful

      Well, no.

      The rules made it so he could insist on giving the passwords only to the Mayor and only in a secure situation.

      He used that as an excuse.

      It's pretty clear from all I've read that he really was holding the city hostage because he was disgruntled at the changing employment situation, and in the process he prevented city personnel from accessing data they needed to do their jobs.

      The Jury was sympathetic that the city acted like idiots once it all started, but they were also cognizant that he wasn't completely blameless in what followed.

      So, in reality, when the rules say not to give the password to your boss, you don't. And when they say not to give the password out over unsecure communications, you don't. But you also don't make a pest of yourself; you take the initiative to find a way to get the password to the right person in a secure manner.

    4. Re:Not trying to be a troll here, but... by Attila+Dimedici · · Score: 1, Informative

      So, you get hired by Joe Schmoe. He gets fired. John (the guy in the next cubicle) comes in and tells you that he has been given Joe's job, your fired, and he wants you to give him all the company passwords that you have. What do you do? Oh yeah, when John did this, he came into your office with three people you have never met.
      That is what happened to Terry Childs.

      --
      The truth is that all men having power ought to be mistrusted. James Madison
    5. Re:Not trying to be a troll here, but... by Anonymous Coward · · Score: 0

      Your point is pretty valid, However, it speaks volumes to the fact that you must have never worked in public service.

      when a person get's a job with a public body, and is promoted up in charge of a project, it's often interesting to see how people deal with the trust others place in them.

      in this case, Terry personally felt that the people that had hired him to do this job were not qualified to have the information that they already had access to. Whether it be because he had observed them doing things he felt were underhanded or just decided that he felt superior to them, is what was up for debate.

      He may have handled the situation incorrectly, but he likely had a very valid reason for doing what he did.

      Most of us in IT always know there's always the next project. Sometimes we mess up though!

    6. Re:Not trying to be a troll here, but... by FooAtWFU · · Score: 1

      I appreciate this as the first well-reasoned, moderate opinion on the situation I've read that's not supporting Childs. If I had mod points I'd use them.

      At the same time, we should all appreciate that unless we've gone to great lengths to become informed on the matter, our "everything you've read" (particularly in the newspapers) could easily have been the machinations of an administration which, as you put it, "acted like idiots once it all started" and were more interested in petty office-politics than anything else. (After all, they're the ones with the best access to the press).

      --
      The World Wide Web is dying. Soon, we shall have only the Internet.
    7. Re:Not trying to be a troll here, but... by beakerMeep · · Score: 4, Insightful
      People keep saying this but where's the proof? I haven't seen any evidence of such a policy. But I admittedly have only been partially following the case.

      From: http://www.ktvu.com/news/23283217/detail.html (emphasis mine).

      Childs reportedly had a fractious relationship with some of his coworkers, attorneys on both sides said. He testified at trial that he never intended to harm the network but said that other employees, including his supervisors, were not qualified to have the passwords. Childs claimed he was merely following established industry guidelines for password protection. "You do not ever give up your username and password," Childs said.

      That doesn't sound like you make it sound. Industry guidelines are not the same as company/government policy.

      To be honest I think the Slashdot community is wrong to defend this guy. He sounds like an ego-maniac driven not by security, but by the sys-admin God complex. However, that's just what I think, and I could be wrong. Sans the full transcript of the trial it's really hard to say what happened. I'd love for groklaw to take a look at it too. They probably need a break from SCO shenanigans. :)

      --
      meep
    8. Re:Not trying to be a troll here, but... by sribe · · Score: 1

      Well, in my case, everything I've read has been on /. so I've got the opposite problem, I know that my information about the case is probably (wildly) biased in favor of Childs. One the one hand, I really cannot see what crime he was guilty of. On the other hand, prosecutors are not generally as vindictive, and juries not as stupid, as people here like to believe.

    9. Re:Not trying to be a troll here, but... by greenbird · · Score: 1

      in the process he prevented city personnel from accessing data they needed to do their jobs.

      From everything I've read about the case this simple isn't true. From what I've read at no time were any network services disrupted. It was just that no one could access the equipment to make changes.

      --
      Who is John Galt?
    10. Re:Not trying to be a troll here, but... by Anonymous Coward · · Score: 0

      Rules for sharing passwords:
      1) Never share passwords.
      2) (Experts only) Never share passwords.

    11. Re:Not trying to be a troll here, but... by Skarecrow77 · · Score: 2, Interesting

      "I'm sorry John, you know I can't give that out without confirmation. Did Bob (Joe Schmoe's boss)authorize this? By the way, Why am I being fired, and who are these people?"

      Doesn't that work?

    12. Re:Not trying to be a troll here, but... by Wyatt+Earp · · Score: 1, Troll

      I've worked in the public sector a while and what I learned is - if the agency head(s) ask you to do something job related, even if it's against the policy that's printed out, you do it.

      If the superintendent of a school district says - "Whats the password for root on the server?" You tell them.

      I have zero sympathy for Childs, he took ownership of something that didn't belong to him, sure he designed it, but it was bought and paid for by the City of San Francisco, and he turned into a control freak. When someone higher up the food chain started poking around "his" stuff he got whacky and tried to stand up to one of the biggest cities in the US. Well guess what, you will lose that fight.

    13. Re:Not trying to be a troll here, but... by Wyatt+Earp · · Score: 1

      You skipped the part where you chase Jill Schmoe into her office and threaten her.

    14. Re:Not trying to be a troll here, but... by Anonymous Coward · · Score: 0

      In my opinion: if the city hires you, you are subservient to the city. You do not give passwords to your inferiors. Ever.

      Really? So, how does a lowly user get a password to log in? Think a little bit before making blanket statements.

      Further, sometimes you DELEGATE IT admin tasks to other employees, even if they report to you. And sometimes, they need admin passwords to do the work you assign to them.

      You do, however, give passwords to your superiors when asked. Always.

      Really? SF had a written policy on passwords. The written policy was NOT to give passwords to ANYONE, even if they are your superior, unless they are specifically authorized to have those passwords.

      And no, under the policy your superior does not automatically have the authority to authorize themselves to have those passwords.

      you get hired by someone, you do what they want to do, provided it isn't illegal. I highly doubt that giving someone the password or passwords to their own systems would have been the wrong thing to do.

      Correct. But who is the "SOMEONE"? The employer is the city of San Francisco, which has a large number of employees, with many different levels of access, trust, and responsibility. As part of that, there is a password policy which lays out which of the city employees should have IT passwords, and under what circumstances they can be disclosed and to who they can be disclosed.

    15. Re:Not trying to be a troll here, but... by plover · · Score: 1

      It's easier to have a fair trial when it's not as public as this. Juries and prosecutors have less reason to be biased.

      --
      John
    16. Re:Not trying to be a troll here, but... by Attila+Dimedici · · Score: 1

      See, you refused to give him the password, you are now a criminal.

      --
      The truth is that all men having power ought to be mistrusted. James Madison
    17. Re:Not trying to be a troll here, but... by nomadic · · Score: 1

      So, in reality, when the rules say not to give the password to your boss, you don't. And when they say not to give the password out over unsecure communications, you don't. But you also don't make a pest of yourself; you take the initiative to find a way to get the password to the right person in a secure manner.

      The copy of the rules I've seen was aimed at the average, everyday users, not IT staff, and simply meant that if you're in, say, accounting, you don't give your personal password to your boss. The IT department is different, and Childs wasn't withholding his personal password, but rather passwords to city systems.

    18. Re:Not trying to be a troll here, but... by Anonymous Coward · · Score: 0

      More like:

      You get hired by Joe Schmoe. He gives you the company policy on passwords. The policy includes not revealing them to anyone except the CEO.
      Later, Joe (or his replacement) comes to you and demands the passwords. You refuse, as policy says you can only hand them to the CEO.

    19. Re:Not trying to be a troll here, but... by Anonymous Coward · · Score: 0

      And not following industry guidelines still leaves you open to charges of negligence or even assisting an attack.

    20. Re:Not trying to be a troll here, but... by Anonymous Coward · · Score: 1, Insightful

      It's one thing to not give anyone your password. It's another to refuse to create new accounts for people who are clearly authorized to request just that, which is what he did. He didn't just refuse to provide his password, he refused to provide access.

    21. Re:Not trying to be a troll here, but... by Sycraft-fu · · Score: 4, Insightful

      Also they weren't asking for HIS username and password, they were asking for THE username and password. There is a difference as any competent sysadmin should know. I won't give up my password to any systems here at work. Policy requires that I do not. However my password is only for my accounts. There are other accounts I have the password for, that are not mine, share accounts. There would be root on the UNIX systems, the local administrator account on the Windows systems, the enable password on the switches, the SA password on the DB server, and so on. There is only one of those accounts (and in the case of things like root, can only be one). It isn't my password on them, it is a password all the IT staff share. That password isn't something I can change to one only I know and refuse to give out, I'd get in trouble for that.

      Big, big difference. Had the city said "We want your password to log in to your personal e-mail account and bank account," well ya, I'd be supporting him for saying no. However they wanted the system passwords for various devices and services that have but one master password. If those passwords were the same as his personal password that is bad security practice on his part, however there is still a solution: Change the passwords and give them the new ones (or change the password on your account).

    22. Re:Not trying to be a troll here, but... by Skarecrow77 · · Score: 2, Insightful

      Nope, you never refused a thing. You reittereated what he already knew, or should know.

      You don't say "No I will not do that". You say "I will do that as soon as I can confirm that I am allowed to."

      Semantic difference, for sure, but the law is all about semantics and how things are worded/phrased. If it wasn't, we wouldn't need lawyers.

    23. Re:Not trying to be a troll here, but... by parcel · · Score: 3, Informative

      I've worked in the public sector a while and what I learned is - if the agency head(s) ask you to do something job related, even if it's against the policy that's printed out, you do it.

      In my experience (private sector, financial industry) that results in immediate termination of your employment. And that isn't theoretical, I'm aware of two instances at my current company. In both cases they had security guards escort them off the premises.

    24. Re:Not trying to be a troll here, but... by TENTH+SHOW+JAM · · Score: 4, Informative

      If the superintendent of a school district says - "Whats the password for root on the server?" You tell them.

      No you don't. Ever. You say "Go to the safe and get them yourself. Don't forget to sign the register." When Superintendent bleats that it is needed NOW! your answer is to point them to the safe. Terry Childs did not put the passwords in the safe and deserves to go down for that.

      --
      A sig is placed here
      To display how futile
      English Haiku is
    25. Re:Not trying to be a troll here, but... by biryokumaru · · Score: 3, Informative

      Here is the policy. I believe the relevant section (page 32) only really applies to user passwords, not system-level stuff.

      --
      When you're afraid to download music illegally in your own home, then the terrorists have won!
    26. Re:Not trying to be a troll here, but... by nomadic · · Score: 1

      The only Superior he was supposed to give the password to is the Mayor. He was only supposed to do that in an environment deemed secure enough for no one else to get the password

      Can you provide a cite to this rule?

    27. Re:Not trying to be a troll here, but... by Khyber · · Score: 2, Insightful

      "but it was bought and paid for by the City of San Francisco"

      Excuse me, it was bought and paid for by THE PEOPLE OF SAN FRANCISCO.

      Paid through our tax money, which also means it was paid for through *HIS* tax money.

      --
      Still waiting on Serviscope_minor to wake up to fucking reality and realize that Jessica Price isn't going to fuck him.
    28. Re:Not trying to be a troll here, but... by MushMouth · · Score: 5, Informative

      According to the network engineer who was a juror on the case (so I am guessing that he knows far more details about it than you or I)....
      He didn't refuse to just give his "password" but to give any access at all to the core routers, removed any way of password retrieval without doing a full system reset, and would not provide the configurations to these routers.

      On top of that, there were emails and witnesses that made it appear that Childs was doing this all to make it such that only HE had access.

    29. Re:Not trying to be a troll here, but... by ObsessiveMathsFreak · · Score: 1

      In my opinion: if the city hires you, you are subservient to the city. You do not give passwords to your inferiors. Ever. You do, however, give passwords to your superiors when asked. Always.

      Gainful Employment does not mean you have joined some kind of army, even if your employer is the Government. Though I understand a lot of American managers are actually ex-army, so perhaps the US view of management is coloured by this somewhat.

      --
      May the Maths Be with you!
    30. Re:Not trying to be a troll here, but... by TENTH+SHOW+JAM · · Score: 2, Informative

      What Tony should have said is "The passwords are in the secure password repository. Look it up yourself." The problem is that he couldn't say that because it was a lie to. He dug his own hole.

      --
      A sig is placed here
      To display how futile
      English Haiku is
    31. Re:Not trying to be a troll here, but... by biryokumaru · · Score: 1

      Also known as assuming Jill Schmoe is a criminal attempting to use social engineering to gain illegal access to a municipal government's network because she's asking for passwords to systems without providing any kind of valid authorization for the rights to said passwords.

      But, hey, she's a girl and he's a guy. Obviously he was the only conceivable threat in this situation.

      --
      When you're afraid to download music illegally in your own home, then the terrorists have won!
    32. Re:Not trying to be a troll here, but... by John+Hasler · · Score: 1

      I agree that the guy screwed up and deserved to be fired and maybe even sued, but sending him to prison is ludicrous.

      The lesson I see here is never take a job with government (or at least not with the city of San Francisco).

      --
      Warning: this article may contain humor, sarcasm, parody, and perhaps even irony. Read at your own risk.
    33. Re:Not trying to be a troll here, but... by jollyreaper · · Score: 1

      Not trying to be a troll here, but... and maybe I'm not understanding the whole case correctly. I've followed the articles on Slashdot for a while. In my opinion: if the city hires you, you are subservient to the city. You do not give passwords to your inferiors. Ever. You do, however, give passwords to your superiors when asked. Always. They hired you, after all. They are your bosses

      I've mostly avoided this kind of horseshit but here's an example for you, real life. A senior VP of the company was having huge battles with management and was on his way out. The grapevine did not know of this, they really played it close to the vest. So I had no idea there were problems. He asks me how to get his information out of his personal directories on the server and onto his laptop. (Yes, he's a VP. They're really that stupid.) Given that this is a direct request from a superior, I ask if he just wants a copy. No, he specifically wanted everything moved. I told him that this violated our policy on "thou shalt not store important stuff you don't want to lose on a laptop." He told me that wasn't a concern here. So, not able to disobey a direct order, I showed him how to do it. His directory was scrubbed clean. But immediately thereafter I went to shadowcopy and restored a copy of the last save into the IT forensics folder. This didn't seem kosher and I wanted to make sure we had a nice, clean copy in case of shit hitting fans.

      It was a huge mess and there were lawsuits after he left but we were protected from any of the backsplash. But this was so typical of poor communications in the company. They would fire employees and not let IT know about it for a week. Employees with remote access to the big ol' important database of things we don't want people to fuck with if they're disgruntled. They'd fire employees over the phone without bothering to get back equipment. Fortunately, we kept records so when management wanted to know where a given laptop was, we could tell them who forgot to pick it up at termination.

      In retrospect, I don't see a good solution for our sysadmin here. He stuck by his guns and got fucked. But if he handed over the passwords in clear violation of company policy upon a direct and illegal order, he could also be prosecuted. I could see getting fired for it -- people get fired for bullshit reasons all the time -- but jail time is simply out of line.

      --
      Kwisatz Haderach
      Sell the spice to CHOAM
      This Mahdi took Shaddam's Throne
    34. Re:Not trying to be a troll here, but... by Anonymous Coward · · Score: 1, Informative

      Um, it clearly says "the scope of this police includes all personnel who have or are responsible for an account... on any system.... This clearly is not limited to "user passwords" only.

      page 34 specifically says to "avoid"
      - giving your password over the phone to anyone
      and
      - telling your boss your password

      Two of the things they tried to get him to do.

    35. Re:Not trying to be a troll here, but... by publiclurker · · Score: 1

      No, actually, you are just being a troll, and a fairly poor one at that.

    36. Re:Not trying to be a troll here, but... by hacksoncode · · Score: 2, Informative

      The County policy stating that you are to avoid giving your password to your boss *explicitly* says that it applies both to user-level passwords, and to system level passwords such as root, network admin passwords, etc.

    37. Re:Not trying to be a troll here, but... by nurb432 · · Score: 1

      . You do, however, give passwords to your superiors when asked. Always. They hired you, after all. They are your bosses.

      Depends on the polices in place, and when the government is involved, laws are also factored in. It may not be as simple as you wish it to be. Where i work you don't give passwords out to ANYONE, even the security team. If they need access, they change yours but you are forbidden by policy to give yours out.

      Similar rules exist for data distribution. Sometimes even your boss isn't authorized to see the data you are. ( but, sometimes they are.. )

      --
      ---- Booth was a patriot ----
    38. Re:Not trying to be a troll here, but... by ClosedSource · · Score: 2, Interesting

      I'm perplexed why some people on Slashdot who are so willing to trash the performance of their fellow geeks, rally around one who is charged with a crime.

      If we assume this guy is innocent of a crime without knowing the facts, why can't we assume everybody else is competent until it is proven otherwise?

    39. Re:Not trying to be a troll here, but... by Darinbob · · Score: 1

      Being fired and escorted off the property is a far far better thing than going to jail for 5 years.

      This case is absolutely NOT about failing to follow orders. That is not a crime for civilians. Even in messed up California law. One article said "computer tampering" which seems silly, and the other said he was convicted of "denial of service". I don't know which particular law this is, or what the letter of the law states because of which the jurors felt they had to convict.

      Now failing to follow orders is what started the whole mess of course. And continual failure to follow orders could cause actual crimes to occur as a side effect. But failure to follow orders by itself did not get him into jail.

      The point of the article referenced above is that there was a felony conviction for "denial of service" when it doesn't seem like there was much actual loss of service.

    40. Re:Not trying to be a troll here, but... by Jah-Wren+Ryel · · Score: 4, Insightful

      No you don't. Ever. You say "Go to the safe and get them yourself. Don't forget to sign the register." When Superintendent bleats that it is needed NOW! your answer is to point them to the safe. Terry Childs did not put the passwords in the safe and deserves to go down for that.

      I disagree. The decision to put passwords in a safe in the first place is above his pay-grade.
      It seems nobody instructed him to do so, so you can't blame him for not following a procedure that didn't exist.
      If anything, the blame lies on his superior(s) who failed to adequately implement a "sysadmin gets hit by bus (or fired)" plan.

      --
      When information is power, privacy is freedom.
    41. Re:Not trying to be a troll here, but... by X0563511 · · Score: 1

      Because at slashdot: Me > You > The System

      --
      For large sets, this will be our guide even unto death, for the LORD will work for each type of data it is applied to...
    42. Re:Not trying to be a troll here, but... by Anonymous Coward · · Score: 0

      I understand your point. But I left a job once and was asked for my password. I gave it to my supervisor.
      I got a call the next day from someone I knew in security( a friend) asking me what the hell I was doing, they could see me active on the network. I told them I wasn't on their network no freakin way, I told them I had given my password to my boss as he requested in exit interview.
      He then told me that I wasn't supposed to give out the password to anyone as per policy. I didn't realize or think about it applying to me, because I was 50 ft from the door and never coming back.
      My supervisor still works there. So I guess nothing ever happened to him.

      So in large organizations like this a fuzzy line gets created. You can go with the flow or be an anal asshole (according to your peers).
      To be honest I've worked in various organizations and security was never taken very seriously, except for one. They were very serious, you got caught in the hall without ID you were escorted out of the building right then and taken to security. [They not only had uniforms and badges they carried guns] Then your supervisor had to come and sign you back in. Three violations and you were out for good. There were other means fo getting violations, but that was one I got caught on.
      They were also fairly sophisticated about computer security. I know one guy got a violation because he had stored a password in a keystroke function. The only thing I could think of is that someone saw him use it and reported him.
      When it came to dealing with a security policy that was the only place I liked, because you always knew it was going to be enforced and security reported to know one in that building. Not only were they roaming the halls/offices by day , they were checking desks at night.

    43. Re:Not trying to be a troll here, but... by LurkerXXX · · Score: 4, Insightful

      Sorry, No. It's the job of any competent admin to make sure necessary passwords are safely stored in a location where they are available to others they will be needed by in the case he is hit by a bus. It's not above his pay grade. It's a minimum common sense necessity obvious to anyone who should be allowed to run production systems and call themselves a sysadmin.

    44. Re:Not trying to be a troll here, but... by Anonymous Coward · · Score: 0

      I was in a very similar situation once. The fact remains he didn't comply. He assumed the people in that room weren't worthy/qualified/etc. on his own. As an administrator he should have given the password once asked by a superior, that instant. Here's the reason. Although he feels they were not qualified, in fact he was not qualified to vet those personnel in the room and on the phone in the room. He had no idea what the meeting was for and it is not his job to determine that. He had no idea if those people already signed/agreed not to disclose contents of the meeting. He is not an investigator but an administrator. He should have given the password and left, documented the situation, and waited for further orders.

      If you haven't already encountered similar situations already as an administrator you will. The fact is even though administrators wield immense power with regard to the network and data within, they must always remember they need to do what they are told. Administrators are often paranoid and should be. But there are always many things going on in a company/government institution/etc. that they are not privy to, and should never be. In fact because he was not invited to the meeting initially as a participant but as a technical adviser shows he was not qualified to be in the meeting himself. The advising part is simple, they needed the password. Done. They needed nothing more from him at that time.

      In fact I can imagine the meeting concerned something far more serious than he imagined. There very well could have been and maybe still is an internal or external investigation going on involving any of a myriad of scenarios involving local law enforcement officers maybe even federal investigators.

      In my case the CEO needed passwords to the entire network. I was hesitant just like him, thinking to myself, "this is odd". My mind was racing with scenarios. I gave the passwords to the CEO. Months later I realized something much more serious was going on and in fact the CEO and other managers were savvy enough to keep me out of it. They "purposely" distanced me from the investigation.

      Not everyone is out to get you or the network you are administering. Do your job, do not hinder your boss in their job.

      I hope he thought about this since then. I hope you do as well as an administrator.

    45. Re:Not trying to be a troll here, but... by Anonymous Coward · · Score: 0

      Hey! Sometimes listening to "Your Boss" or "The guy in charge" isn't always the smart or right thing to do. Example: suppose you were the president of a country and were flying in a plane, and you wanted to land. The pilot says "Hey, its not safe" but as president you declare: "You are my employee. I demand that you land now!" And so, ...according to you... the correct thing to do is land. Well, good for you then, the pilot landed. Mind you, the pilot, the president and everyone else died, but at least the pilot was blindly obedient.

    46. Re:Not trying to be a troll here, but... by sconeu · · Score: 1

      Because, by definition, until the verdict came in, he *WAS* innocent.

      --
      General Relativity: Space-time tells matter where to go; Matter tells space-time what shape to be.
    47. Re:Not trying to be a troll here, but... by bit01 · · Score: 1

      He didn't refuse to just give his "password" but to give any access at all to the core routers, removed any way of password retrieval without doing a full system reset, and would not provide the configurations to these routers.

      On top of that, there were emails and witnesses that made it appear that Childs was doing this all to make it such that only HE had access.

      I find that highly suspect. No responsible admin would do that. Plus his suspicious behavior when they tried to audit him.

      Given Childs early criminal record I wonder whether he configured those routers to sniff city net traffic and sell/use the resulting info but the city couldn't prove it so they went for the lesser charge?

      ---

      Open source software is everything that closed source software is. Plus the source is available.

    48. Re:Not trying to be a troll here, but... by Anonymous Coward · · Score: 0

      If we assume this guy is innocent of a crime without knowing the facts, why can't we assume everybody else is competent until it is proven otherwise?

      We have learned, sometimes the hard way, that making such an assumption is not only foolish, but can also result in otherwise avoidable disasters. We have also learned that incompetent people make plenty of invalid accusations when it comes to technical problems, because they need someone else to blame rather than themselves. People in IT are often at the receiving end of these accusations, since they're often the first to be contacted by this frustrated user. It's typically during that first contact when they start looking for someone else to blame.

    49. Re:Not trying to be a troll here, but... by Anonymous Coward · · Score: 0

      On the other hand, prosecutors are not generally as vindictive, and juries not as stupid, as people here like to believe...

      My understanding is that, in the USA, that depends on whether the prosecutor (or his boss) is up for re-election, and whether it's a case with a sufficiently high profile for the affected elected official to believe it affects their chances for re-election.

    50. Re:Not trying to be a troll here, but... by Anonymous Coward · · Score: 0

      There is a big difference between being a jerk at the office and committing a felony.
      His employers made up a bunch of crap to turn one thing into the other.
      Frankly, I'd like to see them investigated and prosecuted for the false statements they made to the police, the FBI, and the media (at least one of which is *also* a crime).

    51. Re:Not trying to be a troll here, but... by Anonymous Coward · · Score: 0

      He didn't refuse to just give his "password" but to give any access at all to the core routers, removed any way of password retrieval without doing a full system reset, and would not provide the configurations to these routers.

      This is an important point that all the Slashdotters defending him keep completely missing. They keep saying that he was doing what any responsible admin would do.

      However, the simple fact is that he was the only person in the world who had access to the network.

      The only one. Think about that for a minute. He's mortal. He could get hit by a bus on the way to work one day and die instantly. Then, absolutely no one would have access to the network. No one.

      This is what's known as a "single point of failure". Under no circumstances is this ever a good network admin practice. Period.

    52. Re:Not trying to be a troll here, but... by Anonymous Coward · · Score: 1, Insightful

      It's old hat for security types to tell you to never record your passwords anywhere, and completely unrealistic.
      I've talked to many places that had issues due to improper control of passwords.
      I'm not going to go over what happens when everybody and their dog has access to the password.
      I will mention that nobody is going to be there and available 24/7/256, so relying on one person is also going to backfire, eventually.

      My suggestion has always been to keep a mandatory password log kept in two separate physical secured locations.
      That means it's in a safe, not joes desk. That also means it's in a different building, preferable at a different site at least across town, if at all possible.
      As to the safe, there must be a limited number of personnel, minimum of 2 other than the admin, with the ability to get it.
      (You have no idea how many companies lost access to their network when a building flooded/burned/power outage/etc because their password log was stored in joes desk in the affected building and their usual head admin was on vacation skiing in prague or whatever and couldn't be reached by any communications for at least 4 days.)

      Stuff happens you never expect. If you've got appropriate contingency plans to C.Y.A. then it might not seem like a big deal to other people. But if you don't have your anti-murphy shield, it's gonna hit the fan with multiple truck loads. Guess who's going to be the fan... This kind of stuff can and does kill companies, even when they live through it somebody is whining about the nuclear reaming they just got.

      As to the whole Terry Childs thing, it's gotten really distorted by the various sides, but it does sound like somebody didn't cover their backside properly before things blew up, and other people that had no idea what they were doing stuck their size 14s in where they didn't belong. And yes, I expect my admins to be paranoid network nazis, and would want all politicians and bureaucrats to stay the hell away from IT under any circumstances.

    53. Re:Not trying to be a troll here, but... by ppanon · · Score: 1

      You forgot:
      The policy also states that you are supposed to provide system passwords for inclusion in a central secure passwords DB.
      You don't convey the system passwords that you know on to the security department either through ignorance, incompetence, or by reading and wrongly believing too many BOFH humour articles that indicate it would provide job security.
      When you refuse to provide the passwords, you try to hide behind a security policy which you actually had violated. Because of your intransigence, it eventually goes to court where the jury sees past your bullshit and finds you guilty.
      I wasn't in the courtroom so I don't know what the Jury heard (and neither does anybody else on Slashdot) but it sure looks to me like the guy got nailed for trying to be the BOFH instead of a professional systems administrator. His first clue that things weren't going to work out for him was his lack of a PFY minion.

      --
      Laissez lire, et laissez danser; ces deux amusements ne feront jamais de mal au monde. - Voltaire
    54. Re:Not trying to be a troll here, but... by jedidiah · · Score: 0

      The fact that he failed document the password properly is not a crime.

      Neither is his unwillingness to hand that password over to someone explicitly disallowed by corporate policy.

      All of the morons on here trying to justify a 5 year prison sentence are just grasping at straws.

      You don't get 5 years in prison for being a jerk to your boss.

      --
      A Pirate and a Puritan look the same on a balance sheet.
    55. Re:Not trying to be a troll here, but... by jedidiah · · Score: 1

      > rally around one who is charged with a crime.

      This is not Soviet Russia. Just because the DA decided to accuse him of something,
      it doesn't automatically mean that we all assume that he is guilty and should be
      sent to a gulag. First and foremost, there should be a real examination of whether
      or not at crime has infact occured.

      No crime occured.

      A man's employer simply decided to get vindictive and had the means to do so.

      Childs should have been fired if his performance was considered unacceptable
      and that should have be the end of it.

      This is yet another non-crime where the consequences are wildly out of balance.

      --
      A Pirate and a Puritan look the same on a balance sheet.
    56. Re:Not trying to be a troll here, but... by eosp · · Score: 1

      Yes, yes, yes. Even if he was not found guilty, the failure to document this stuff (even for the more innocent reason of getting hit by a bus) should make this guy unemployable in IT for the rest of his life.

    57. Re:Not trying to be a troll here, but... by Anonymous Coward · · Score: 0

      The policy also states that you are supposed to provide system passwords for inclusion in a central secure passwords DB.
      You don't convey the system passwords that you know on to the security department either through ignorance, incompetence, or by reading and wrongly believing too many BOFH humour articles that indicate it would provide job security.

      Cites on these points?

    58. Re:Not trying to be a troll here, but... by Eskarel · · Score: 1

      if the agency head(s) ask you to do something job related, even if it's against the policy that's printed out, you get the request in writing and then do it.

      There fixed that for you.

    59. Re:Not trying to be a troll here, but... by Eskarel · · Score: 1

      No, of course not.

      However, failing to document the passwords and then refusing the release the passwords to the owners of the system because he thought they didn't deserve to have them should make him unemployable in IT(and for that matter almost any job requiring an element of trust) for the rest of his life regardless of any convictions or lack thereof.

      It doesn't really matter if he's convicted or not, if I give you the keys to the office and then you get fired and refuse to return those keys, you are untrustworthy and unreliable and don't deserve to be given keys again until and unless you can prove that you've changed.

      This guy was a control freak and an asshole, he essentially sabotaged his employer by not storing any service level passwords(as he was obligated to do by policy) and then refusing to turn over those passwords. It's no different than a logic bomb or any other angry departing gift a sys admin might give. The fact that they ought to have checked to see if the passwords really were in the system and sacked his ass much earlier if he'd refused to do so doesn't really enter into it.

    60. Re:Not trying to be a troll here, but... by Anonymous Coward · · Score: 0

      They still weren't qualified to have them. He still was only allowed to hand them over to the mayor.

    61. Re:Not trying to be a troll here, but... by Nyder · · Score: 1

      Not trying to be a troll here, but... and maybe I'm not understanding the whole case correctly. I've followed the articles on Slashdot for a while. In my opinion: if the city hires you, you are subservient to the city. You do not give passwords to your inferiors. Ever. You do, however, give passwords to your superiors when asked. Always. They hired you, after all. They are your bosses. If I hire a security guard for my building, he'd damn well better give me the key if I decide to fire him, or if I get locked out, or both. You don't hide data from your superiors, plain and simple, however *technologically* less advanced they might be. Maybe the city is making a mountain out of a molehill; I'm really not qualified to comment on that, since I don't know as much about the case as some of the people on here will. Honestly, though, my original point: you get hired by someone, you do what they want to do, provided it isn't illegal. I highly doubt that giving someone the password or passwords to their own systems would have been the wrong thing to do.

      Here's a hint.

      DO NOT FIRE SOMEONE BEFORE YOU GET BACK ANYTHING THEY HAVE OF THE COMPANIES.

      You say, hand me your keys, once they do, then fire them.

      I'll tell you something, if I work for you and you fire me, chances are i'm not going to be happy about being fired. So if you come to me after that asking for something back, i'm not going to make your job easier, you just fucking fired me.

      Seriously, what the fuck do they expect?

      --
      Be seeing you...
    62. Re:Not trying to be a troll here, but... by Nyder · · Score: 1

      No you don't. Ever. You say "Go to the safe and get them yourself. Don't forget to sign the register." When Superintendent bleats that it is needed NOW! your answer is to point them to the safe. Terry Childs did not put the passwords in the safe and deserves to go down for that.

      I disagree. The decision to put passwords in a safe in the first place is above his pay-grade.
      It seems nobody instructed him to do so, so you can't blame him for not following a procedure that didn't exist.
      If anything, the blame lies on his superior(s) who failed to adequately implement a "sysadmin gets hit by bus (or fired)" plan.

      totally agree. It was the city's fault for now having a backup plan.

      Sheesh, people die everyday, if Terry Childs had died, then the city would of still been with out passwords and only had it's self to blame.

      In fact, Terry Childs is being punished because the city failed to provide a work around system in case they lost their admin.

      --
      Be seeing you...
    63. Re:Not trying to be a troll here, but... by Nyder · · Score: 1

      People keep saying this but where's the proof? I haven't seen any evidence of such a policy. But I admittedly have only been partially following the case.

      From: http://www.ktvu.com/news/23283217/detail.html (emphasis mine).

      Childs reportedly had a fractious relationship with some of his coworkers, attorneys on both sides said. He testified at trial that he never intended to harm the network but said that other employees, including his supervisors, were not qualified to have the passwords.

      Childs claimed he was merely following established industry guidelines for password protection.

      "You do not ever give up your username and password," Childs said.

      That doesn't sound like you make it sound. Industry guidelines are not the same as company/government policy.

      To be honest I think the Slashdot community is wrong to defend this guy. He sounds like an ego-maniac driven not by security, but by the sys-admin God complex. However, that's just what I think, and I could be wrong. Sans the full transcript of the trial it's really hard to say what happened. I'd love for groklaw to take a look at it too. They probably need a break from SCO shenanigans. :)

      So, we are wrong because the city didn't make any backup plans for network passwords in case of something bad happening?

      Thats all this comes down to. San Franisco got butthurt because they stupidly didn't have copies of the networks passwords anywhere, but with the IT admin.

      I'd be suing the city if I was Terry Childs

      --
      Be seeing you...
    64. Re:Not trying to be a troll here, but... by Nyder · · Score: 2, Insightful

      Also they weren't asking for HIS username and password, they were asking for THE username and password. There is a difference as any competent sysadmin should know. I won't give up my password to any systems here at work. Policy requires that I do not. However my password is only for my accounts. There are other accounts I have the password for, that are not mine, share accounts. There would be root on the UNIX systems, the local administrator account on the Windows systems, the enable password on the switches, the SA password on the DB server, and so on. There is only one of those accounts (and in the case of things like root, can only be one). It isn't my password on them, it is a password all the IT staff share. That password isn't something I can change to one only I know and refuse to give out, I'd get in trouble for that.

      Big, big difference. Had the city said "We want your password to log in to your personal e-mail account and bank account," well ya, I'd be supporting him for saying no. However they wanted the system passwords for various devices and services that have but one master password. If those passwords were the same as his personal password that is bad security practice on his part, however there is still a solution: Change the passwords and give them the new ones (or change the password on your account).

      You miss the point. They should of had a copy of THE password to the system somewhere safe. They didn't. they failed. And they blamed Terry Childs for their fuck up.

      --
      Be seeing you...
    65. Re:Not trying to be a troll here, but... by Anonymous Coward · · Score: 0

      We're not defending him because we think "oh he's a nice guy." We're defending him because we don't want to live in a world where "not being a nice guy" gets you thrown in jail. The whole point is that this law could be used against almost any one of us if someone with a little more authority decides they don't like us. And that's wrong.

    66. Re:Not trying to be a troll here, but... by mpe · · Score: 1

      The Jury was sympathetic that the city acted like idiots once it all started, but they were also cognizant that he wasn't completely blameless in what followed.

      Actually the situation with the jury is strange. Since a juror was replaced, how could the replacement juror possibly have been competent? Also this sounds like a fairly elaborate form of "jury tampering".

    67. Re:Not trying to be a troll here, but... by Jah-Wren+Ryel · · Score: 1

      It's a minimum common sense necessity obvious to anyone who should be allowed to run production systems and call themselves a sysadmin.

      Sure it is, which is why his boss should never have allowed him - or anyone else - to work on the network for all those years without requiring it.

      On one hand you've got people faulting him for not doing what the boss said because his boss is the ultimate authority and yet the only reason he's taking the fall here is because the guy with the ultimate authority didn't apply it correctly in the first place.

      --
      When information is power, privacy is freedom.
    68. Re:Not trying to be a troll here, but... by Hognoxious · · Score: 1

      Did the requestors get fired too?

      --
      Confucius say, "Find worm in apple - bad. Find half a worm - worse."
    69. Re:Not trying to be a troll here, but... by LurkerXXX · · Score: 1

      No. The bosses of sysadmin's aren't always computer folks, they are often biz-admin types and don't have a clue what needs to be done. If those basic policies aren't in place, it's his job to try to get them put in place. If he had wanted to set that up that policy and his boss had blocked it, THEN it would be his boss's fault. Since he's not claiming that as a defense, the blame falls squarely on his shoulders.

    70. Re:Not trying to be a troll here, but... by bruce_the_loon · · Score: 1

      City personnel were assigned to take over the running of the FiberWAN network. He was informed of this and refused to grant them access to the network. Whether he felt they were incompetent or not, he had no authorization under any policy or law to do this. Therefore he was preventing those individuals from doing their jobs.

      You can pluck at semantics all day long, it doesn't undo the fact that other people were assigned by management to take over the running of the network and he actively denied them the access needed to do this.

      --
      Trying to become famous by taking photos. Visit my homepage please.
    71. Re:Not trying to be a troll here, but... by Anonymous Coward · · Score: 0

      Better security guards escorting you off of company grounds than police officers escorting you to prison.

    72. Re:Not trying to be a troll here, but... by thegarbz · · Score: 1

      Were the requesters in a position to make, alter, or administrate the request? Were they knowledgeable enough to know what they were asking? Just because someone is in a higher pay bracket does not necessarily make them an expert in your field. Actually quite often it means that they do end up in the position where they should not be dealing with specifics but rather guiding policy instead. If you don't have the balls to stand up to a request that is against written company policy then you deserve to get fired, and there's no reason the requester should. I have had one case where the request was one that really shouldn't be carried it out. I eventually carried it out, but only after sitting in an office for 20 minutes while the requester wrote and signed a letter assuming all liability of the request.

    73. Re:Not trying to be a troll here, but... by Rary · · Score: 1

      The fact that he failed document the password properly is not a crime.

      Neither is his unwillingness to hand that password over to someone explicitly disallowed by corporate policy.

      Actually, the fact that he denied access to authorized users is a crime, specifically CA 502(c)(5). See this for more information:

      Specifically, he denied computer service to an authorized user without permission. The specific act here was not providing access to the FiberWAN routers and switches upon the request of the city's COO. For the permission part, he did not have any permission from anyone to not provide that access. We looked through the evidence for anything that would indicate that he had permission to deny access to an authorized user, but there was no such evidence. There was evidence, however, that it was part of his job duties to provide that access to authorized users.

      I don't know if 5 years is justified (note that he will probably be released shortly with time served), but there is little doubt that he broke the law, and even that he did so knowing exactly what he was doing.

      Also see this article which interviews the Slashdot poster who happened to be on the jury.

      --

      "You cannot simultaneously prevent and prepare for war." -- Albert Einstein

    74. Re:Not trying to be a troll here, but... by Anonymous Coward · · Score: 0

      No, sysadmins do not create policy in an organization. They implement policy.

    75. Re:Not trying to be a troll here, but... by Anonymous Coward · · Score: 0

      Strictly speaking, it's generally a good idea on sensitive systems to ensure they can only be locally accessed by console and disable password retrieval. Also, once again, I think the most important point of this case is he was fired BEFORE any information was requested from him. If I don't work for you company, and I'm not in a mood to do favors, you don't get anything from me. If you want something from me, you should have thought of that before you fired me. And I'm not saying that just as an IT person, but in general. It's utterly ABSURD to expect Mr. Childs to give them ANY assistance after they've already fired him.

      I know I don't just fart rainbows and router configs, and I definitely would never stash something of that nature which is sensitive and not personal anywhere where it would be accessible outside the company offices, so I think it's ludicrous and unrealistic to expect him to either A) Do work documenting systems or B) Present them with information they have a responsibility to have and keep on file, both after they've already fired the man.

      It's his supervisor's fault for not having the passwords kept in a centrally managed database with the master password in a death envelope in a safe. Regardless of whether policy stated that you should put passwords in a database, did his supervisor EVER audit that database? Did they audit it before firing him? No? Well, they're idiots.

    76. Re:Not trying to be a troll here, but... by greenbird · · Score: 1

      He was informed of this and refused to grant them access to the network. Whether he felt they were incompetent or not, he had no authorization under any policy or law to do this. Therefore he was preventing those individuals from doing their jobs.

      You can pluck at semantics all day long, it doesn't undo the fact that other people were assigned by management to take over the running of the network and he actively denied them the access needed to do this.

      You seem to be the one plucking at semantics. At no time were any services disrupted by his actions. There are no semantics there. It's a simple fact. He refused to turn over the passwords to people he had no knowledge as to whether they were authorized to have those passwords. Evidently you don't work in security. That is something you DO NOT do. Lets see, your getting fired from your job. So you give out the keys to the kingdom to anyone and everyone who asks for them? That seems a more prosecutable offense than refusing to provide them except to someone you KNOW is authorized to have them. Say he gives the passwords to this room full of people because they claim they're authorized to have them and one of them logs on and takes down a network whether intentionally or through incompetence. Gee, you think the city would have been ok with that? Do you know what social engineering is? There was no emergency. Everything was functioning fine. Therefore you follow good security practices and wait to give the passwords to someone you KNOW is authorized to have them. There may have not been a written or formal policy stating such but there is still a loosely defined set of good practices for security. And giving out passwords willy nilly doesn't fit into them anywhere. Basically what happened here is a man is being sent to jail for following good security practices and trying to protect the very systems he's being sent to jail for supposedly disrupting. Good security REQUIRES a fairly high level of paranoia.

      --
      Who is John Galt?
    77. Re:Not trying to be a troll here, but... by berashith · · Score: 1

      24/7/256

      yup, i miss all my government job holidays too.

    78. Re:Not trying to be a troll here, but... by mpe · · Score: 1

      I was in a very similar situation once. The fact remains he didn't comply.

      Such a situation can be very much one of "between a rock and a hard place".

      He assumed the people in that room weren't worthy/qualified/etc. on his own.

      So he should have assumed, in the absence of any evidence, that they were.

      As an administrator he should have given the password once asked by a superior, that instant.

      Which in a (slightly) different situation would result in being instantly fired.

    79. Re:Not trying to be a troll here, but... by Actually,+I+do+RTFA · · Score: 1

      Being fired and escorted off the property is a far far better thing than going to jail for 5 years.

      Being fired and escorted off the property is far far better than being fired and escorted to jail for five years. But if they were fired from a financial institution over a ethical/security breach I doubt they'll be able to get another job in that industry. For some people and for some industries, they would rather spend five years in jail and work when they got out in their chosen field then be exiled from it forever.

      --
      Your ad here. Ask me how!
    80. Re:Not trying to be a troll here, but... by psm321 · · Score: 1

      Except that your company happens to have a written policy requiring that for security purposes, keys to the safe can only be handed to the CEO. (Imagine you're at a bank and the policy is that only specially trained tellers or the CEO can have safe keys, not any random middle managers). Others have posted links to the specific policy documents here, which everyone seems to be ignoring.

    81. Re:Not trying to be a troll here, but... by sicapo · · Score: 1

      Terry Childs got what he deserves for disobeying his superior's orders. Now get off my lawn you in-subordinated workers...

    82. Re:Not trying to be a troll here, but... by Jah-Wren+Ryel · · Score: 1

      His boss knows enough to ask him for the password, so clearly he knows enough to institute a policy for password escrow.

      --
      When information is power, privacy is freedom.
  3. Actually by Monkeedude1212 · · Score: 1

    They just made our jobs easier.

    Hey, you want the password? yeah its p@ssw0rd. Tell your friends!

    Before you know it, it'll be written into the next Windows shell and you won't even have to enter it anymore. No more managing passwords and user accounts and all the stuff that makes IT frustrating.

    [/sarcasm ]

    1. Re:Actually by Infiniti2000 · · Score: 1

      No more managing passwords and user accounts and all the stuff that makes IT frustrating.

      DOS?

    2. Re:Actually by Monkeedude1212 · · Score: 1

      Where do you work that DOS is the prefered OS across the entire company?

    3. Re:Actually by jgoemat · · Score: 1

      How did you get my /. password?!?!

    4. Re:Actually by Areyoukiddingme · · Score: 1

      San Francisco.

    5. Re:Actually by John+Hasler · · Score: 1

      > Hey, you want the password? yeah its p@ssw0rd. Tell your friends!

      Violating policy by giving passwords to people who are not authorized to have them? Obviously computer fraud and abuse. Off to prison you go.

      --
      Warning: this article may contain humor, sarcasm, parody, and perhaps even irony. Read at your own risk.
    6. Re:Actually by biryokumaru · · Score: 1

      Don't worry, when someone types in your password, it's all starred out for them. Only you can read it. See, here's what mine looks like: hunter2.

      --
      When you're afraid to download music illegally in your own home, then the terrorists have won!
    7. Re:Actually by Antique+Geekmeister · · Score: 1

      You could just use Subversion. Look in your ~/.svn/auth/ directory for every HTTPS site you access with Subversion.

    8. Re:Actually by Anonymous Coward · · Score: 0

      We are still running DOS/360 and see no reason to change now.

  4. Re:In the by Monkeedude1212 · · Score: 0, Offtopic

    What what?

  5. The World's Largest DDOS by Anonymous Coward · · Score: 0, Informative

    originates from here.

    I hope this helps your lawsuits from DDOS.

    Yours In St. Petersburg,
    Kilgore Trout

  6. Sorry, but this dude had it coming. by Zexarious · · Score: 2, Interesting

    He broke the law and he's going to do a few years in prison for it. I don't understand what the big deal is? Should I have sympathy for him because he is a sysadmin?

    Justice system did exactly what it was designed to do, rehabilitate criminals and deter others from doing crimes.

    Next time, is he going to deny people access who deserve that access because of some ideological nonsense? Doubt it.

    Though he probably will never get hired in IT again, not just because he is a felon, but because you google his name and there it is, him keeping passwords away from his ex-employer.

    1. Re:Sorry, but this dude had it coming. by Anonymous Coward · · Score: 0

      He broke the law and he's going to do a few years in prison for it. I don't understand what the big deal is?

      The gist is:
      He was given certain rules to follow as part of his job. One of those rules said he was not to divulge the passwords except in certain circumstances to certain people. His supervisor (who was not one of those people) ordered him to turn over the passwords. He refused.
      (If I am wrong in my summary, please correct me.)

      If the above is correct, he did nothing wrong.

    2. Re:Sorry, but this dude had it coming. by Anonymous Coward · · Score: 0

      Yes. Every situation regarding IT policy and network security operates as cold and inhuman as the law states. No one ever puts emotion or sacrifice into what they are doing in IT and to do so would be prohibited. Right?

      The law often attempts to account for the human elements of emotion and self-preservation, but almost always fails.

      The fact that powers that be let Childs build a network that became "his baby" shouts that they deserve this blame just as much as him. And upon viewing the political and assinine behavior of those above him, he did everything in his power to keep that system up and running. Which, from his point of view, would probably break if he divulged that informtion.

      Did Childs go about it wrong? Obviously. He should have got legal involved and immunity the moment he gives those passwords to anyone else, since he created that network. To claim that 2-5 years in prison is valid for this situation is absurd. Probation, yes. Actual prison, and loss of freedom for what amounts to a internal political fuckup and power plays? Utter BULLSHIT!

      If you think this situation deserves his loss of freedom, I hate to think what actual crimes and punishment standards you have.

  7. Heading this off--see link to juror by Anonymous Coward · · Score: 5, Interesting

    The juror has been interviewed some already, and is even on /.

    I had many bad assumptions myself. But if the juror is being at all truthful...this guy did some bad things.

    @see http://yro.slashdot.org/comments.pl?sid=1633482&cid=32010078

    1. Re:Heading this off--see link to juror by bartle · · Score: 4, Insightful
      Exactly. Quoting from this post on Slashdot:

      As to these configuration backups, Mr. Childs kept these on a DVD he kept with him at all times. Furthermore, this DVD was encrypted and could only be decrypted using his laptop (as the encryption program required not only a password, but access to a specific file that existed on the laptop).

      Can these actions be defended as anything other than job security? Unless someone has reason to think that BengalsUF is getting the story wrong, why is there so much popular defense for this guy?

    2. Re:Heading this off--see link to juror by rufey · · Score: 3, Informative

      If the person mentioned was on the jury, and there is nothing I've read of his to suggest otherwise, I highly recommend reading his recent posts on his slashdot user page: http://slashdot.org/~BengalsUF

      I learned more in 5 minutes about the case than I have over the past 2 years reading Slashdot and news stories. And, as it turns out, most of what I've read up until today has been embellished or simply was an opinion of someone who knew little about the case.

    3. Re:Heading this off--see link to juror by jafiwam · · Score: 2, Insightful

      That sure violates the "what if I get hit by a bus / win the lottery" rule.

      It's also the point at which it makes Childs a jackass that deserves jail over "just doing my job."

      A few minutes of talk and a phone call could have given him sufficient CYA and probably job security to fix what they break. He chose a power trip instead. Let him rot.

    4. Re:Heading this off--see link to juror by mangu · · Score: 2, Informative

      I read that post, and the replies, and it seems to me the jury did it wrong. Particularly this post seems to hit the nail on the head.

      A jury is *not* required to follow instructions to either absolve or condemn, otherwise what would be the meaning of it all? But too many jurors seem to be swayed by the judge's instructions, which should be mere guidelines. It's not the judge's privilege to make a decision in a trial by jury. In this case, the jury seems to have had a very technical interpretation based solely on the prosecution's version of what it means to deny access to a system.

      Terry Childs, if what we read in many reports is true, never denied access to anyone who actually needed to use the system. His only crime was to use his best judgment on who should be allowed to access the passwords. He never denied access to the *system*, he denied access to the *passwords*, which is a different thing. I don't need to give you the keys to my house in order to let you in. I think the jury reached a wrong decision, because the law is very clear on this point.

      It was his managers' duty to ensure that passwords were adequately managed, if they left that kind of decision entirely to Terry Childs then they shouldn't complain if his decisions weren't what they expected. When a manager lets a subaltern have total control of the passwords he cannot complain if that subaltern does exactly what he was ordered to do.

    5. Re:Heading this off--see link to juror by Khyber · · Score: 1

      "Can these actions be defended as anything other than job security?"

      I would do the exact same thing for backup purposes, and since that is sensitive information encryption is preferred.

      In fact, that's *EXACTLY* how I make backups of my important business files.

      --
      Still waiting on Serviscope_minor to wake up to fucking reality and realize that Jessica Price isn't going to fuck him.
    6. Re:Heading this off--see link to juror by ximenes · · Score: 1

      From what I've read (including BengalsUF's comments, which seem to be the only authoritative source for the case), it sounds to me like Mr. Childs was taking extreme security precautions.

      It's been mentioned several times that the network devices were configured to not store their configs in NVRAM or to wipe the configs if password recovery was used. I personally think that is a bit much, but I could see people I've worked with over the years arguing for this in order to prevent the configs from being retrieved by an attacker (and then analyzed and used to attack the rest of the network).

      So once you've gone that far, you have to have a way to legitimately store and reload the configs when the inevitable failure occurs or an update is required. But if you just put the configs in CVS somewhere, then that becomes the security hole people can attack. So encrypting them and requiring multi-factor authentication to access makes a certain amount of sense.

      As I said, I think it's going a bit far, but if you really really really want to ensure security of a critical piece of infrastructure, that's one way to do it. The way Mr. Childs went about it didn't scale beyond him (another common failing in small environments where the team size = 1), and maybe was too limiting to really be practical, but I don't necessarily think it equates to a matter of ensuring job security as has been claimed.

    7. Re:Heading this off--see link to juror by turbidostato · · Score: 2, Insightful

      "In fact, that's *EXACTLY* how I make backups of my important business files."

      Point being that they were not *his* important business files but San Francisco's ones.

    8. Re:Heading this off--see link to juror by turbidostato · · Score: 1

      "As I said, I think it's going a bit far, but if you really really really want to ensure security of a critical piece of infrastructure, that's one way to do it."

      Since that wouldn't pass the bus test, it is not that he "went a bit too far" but that he "went a bit too wrong" on this regard.

    9. Re:Heading this off--see link to juror by green1 · · Score: 2, Insightful

      maybe was too limiting to really be practical, but I don't necessarily think it equates to a matter of ensuring job security as has been claimed.

      there's a simple test for that... If he had suddenly vanished off the face of the earth one day, can the business keep on going without interruption, has he documented all necessary information for someone equally qualified to him to simply step in and maintain what he started.

      The answer here is clearly no, there was no way for someone else to get in to administer those systems because he refused to let the password be known to anyone other than himself. That is not the way ANY successful company operates.

      This was him trying to make himself indispensable, not simply him making things "secure". There always has to be some way for business to continue if any one person vanishes, as such, any essential passwords, backups, etc need to be accessible to a replacement in some way. What that way is will vary by organization, some will have a safe for this information, some will simply make sure multiple people know the information, others will find a letter sealed in an envelope in the bottom of a filling cabinet to be "good enough" but whatever method is chosen it must be followed.

      It sounds like in this case the approved method was a secure database accessible by the sysadmins and management. his refusal to document his passwords and configs in that database are where he crossed the line from "secure" to "self important"

    10. Re:Heading this off--see link to juror by Darinbob · · Score: 2, Insightful

      The defense is probably because the city did some really stupid things and told some lies (or stretched the truth at least). Further there was so little information about what actually happened to justify a criminal proceeding. After all, it's not a crime to be a jerk, not a crime to be paranoid, not a crime to be an idiot, not a crime to not divulge passwords, not a crime to try and get some job security through legal means, etc. It's pretty clear that the city was mismanaged badly and was desperately trying to cover its ass.

      People naturally want to see a good guy and a bad guy in cases like this, and the city did a very good job of portraying itself as the bad guy.

    11. Re:Heading this off--see link to juror by Anonymous Coward · · Score: 0

      It's been mentioned several times that the network devices were configured to not store their configs in NVRAM or to wipe the configs if password recovery was used. I personally think that is a bit much, but I could see people I've worked with over the years arguing for this in order to prevent the configs from being retrieved by an attacker (and then analyzed and used to attack the rest of the network).

      I'm not sure why they bother to NOT store the config in NVRAM (devices do reboot during power trips)

      Assuming I can get access to the device, while it's still running, via the console port or terminal session... If there's a possibility I can get access to the startup config then I'm going to be able to view the running config as well right?

    12. Re:Heading this off--see link to juror by Anonymous Coward · · Score: 0

      ...it sounds to me like Mr. Childs was taking extreme security precautions.

      Being the only one with access to the system isn't an "extreme security precaution". It's a single point of failure.

    13. Re:Heading this off--see link to juror by Anonymous Coward · · Score: 0

      He never denied access to the *system*, he denied access to the *passwords*, which is a different thing.

      Read all of the juror's posts. He clearly states that, in actuality, Childs denied access to the system, not just the passwords. From one of his posts: "He refused to provide access to that network. Not just simply refusing to tell his passwords, but refusing to provide access at all, even configuration backups. Furthermore, he configured the network in a manner which prevented any attempts to access it or reset the passwords, and in a few scenarios those attempts would have even brought the network down."

      It was his managers' duty to ensure that passwords were adequately managed, if they left that kind of decision entirely to Terry Childs then they shouldn't complain if his decisions weren't what they expected.

      They didn't leave the decision entirely to Childs. The passwords were supposed to be stored in a central repository. He refused to put the passwords in that central repository.

      He did everything he could think to do to ensure that no one but him would have access to the network. When he got "reassigned", he refused to hand over the appropriate access information to the person who was assigned to take over administering the system. When they finally arrested him, he was planning to leave the state, still without letting anyone have access to the system.

      Does that sound like a responsible sysadmin to you?

    14. Re:Heading this off--see link to juror by Anonymous Coward · · Score: 0

      Read BengalsUF and you will understand. Till then I'll paraphrase:

      So, here's how it really happened.

      Terry designed this system, he then made sure only he could get access to it.

      Terry Child's is told he's being reassigned.

      It's demanded he provide ACCESS to the system to another user, not his passwords, not sole custodianship, but ACCESS.

      Now the people demanding it were dicks about it, and fucked the whole situation up by pouring lemonjuice on the wound, but they were within their legal rights. A jury of his peers found this to be the case.

      Terry refused, this was not the first time he had done so, and was placed on administrative leave.

      He then went and took out ~$10,000 from his bank account and fled
      --
      Terry Childs was NOT within his rights by not providing that access, and his actions made it extremely difficult to bypass his tamper-proofing. For instance, password recovery was disabled on the devices in the field, which makes sense... But further, he purged the startup config of his core routers, and ran only on running config, his backup plan? A DVD and a hard line modem... These things are all pretty tough to work around from a security perspective (tough, not impossible.) Not to mention, Terry knew full well the cost of the recovery work entailed, since he had designed the system.

      This had nothing to do with passwords and everything to do with access.

    15. Re:Heading this off--see link to juror by Anonymous Coward · · Score: 0

      Indeed. Groupthink fail.

    16. Re:Heading this off--see link to juror by miffo.swe · · Score: 1

      "It's been mentioned several times that the network devices were configured to not store their configs in NVRAM or to wipe the configs if password recovery was used."

      Thats how its supposed to work. Atleast from what they tought me at Cisco CCNA. Having a password reset as the only step between an attacker and the configs (including passwords etc in it) is from a security perspective pretty lame.

      --
      HTTP/1.1 400
    17. Re:Heading this off--see link to juror by xednieht · · Score: 1

      "why is there so much popular defense for this guy?"

      Popular ignorance for this guy would be more accurate. Most do not seem to be familiar with ALL the details, or simply gloss over minor details like this guy was applying his knowledge toward illegal activities.

      --

      Hope is the currency of fools
    18. Re:Heading this off--see link to juror by The+Moof · · Score: 1

      why is there so much popular defense for this guy?

      Honestly, the certain aspects of the media is selling this as Childs being a good sysadmin and refusing to give up a password to a user that just asked, which isn't even close to what actually happened.

      Inflammatory news gets you more hits than actual facts. Just ask Fox.

    19. Re:Heading this off--see link to juror by Anonymous Coward · · Score: 0

      You carry your backups with you instead of say, putting them in a safe or deposit box like a sane person would?

  8. California law by Anonymous Coward · · Score: 1, Interesting

    thousands of IT workers all over the country that are now guilty
     
    of violating a California law? I'll be worried once there's a California state court in New York City.

    1. Re:California law by Khyber · · Score: 1

      Apparently you haven't heard about a Florida community that sued a person in another state for offensive materials and won.

      --
      Still waiting on Serviscope_minor to wake up to fucking reality and realize that Jessica Price isn't going to fuck him.
    2. Re:California law by Anonymous Coward · · Score: 0

      No, I've heard of that. Have you heard of the difference between a civil suit and a criminal prosecution? You might note that nobody's "guilty" in a civil case.

  9. As an IT worker. by Anonymous Coward · · Score: 0

    I learned something very important here in this case.

    NEVER do the right thing. Cover your own ass.

    Doing the right thing rarely pays off. And damm, Now it can get you put in jail.

    Keep your head down, keep your mouth shut, dont make waves, and cover your own ass.
    Cuz nobody else will.

    1. Re:As an IT worker. by Spacepup · · Score: 1

      It's never in your best interest to cover the ass of someone else.

      Especially if they ate a big bean burrito from Taco Bell for lunch.

    2. Re:As an IT worker. by Skarecrow77 · · Score: 1

      You just learned NOW that CYA is job number one for anybody that wants a career in IT?

      Step 1: Document ANYTHING that may ever be contraversial, why you did it, and exactly why the other options were poor choices.
      Step 2: Any time your superiors ask you to do anything, always mention "Per Supervisor Jane Peterson..." in your notes.
      Step 3: Always make sure you have some good generic excises banked in the back of your head why you are not at fault for bad stuff, while still being responsible for the good things. It -will- save your ass at some point over the years.
      Step 4: Make sure you especially keep an eye out for co-workers, and superiors(!) who are potentially likely to use YOU as THEIR CYA excuse. Be wary, and be prepared.

      It doesn't matter if your company administrates servers, publishes novels, writes software or sells shoes. Business is business, and CYA is always important. Disregard

    3. Re:As an IT worker. by Skarecrow77 · · Score: 1

      Last line should read "Disregard at your peril".

      damn too quick on the submit button.

  10. Re: Initiative by Phrogman · · Score: 2, Interesting

    I think they took away the "initiative to find a way to get the password to the right person in a secure manner" when they locked him up in jail and left him there. He evidently requested to see the mayor, and when the mayor arrived, gave him the password. Unless that isn't the way it went, I don't really see what else he could have done.

    Again though, I haven't read a good article that had significant details in it, just crappy links from /. and short articles that had few details. I want a time line, a copy of the relevant rules, links to a transcript of the court sessions etc :P

    --
    "The first time I got drunk, I got married. The second time I bought a chimpanzee, after that I stayed sober" Arian Seid
  11. The sky is not falling. by Anonymous+Psychopath · · Score: 3, Insightful

    Prosecutors, judges and juries all consider intent. Making a mistake is not the same as malicious action. True, there are times when it's difficult to tell. This isn't one of them.

    --

    Eagles may soar, but weasels don't get sucked into jet engines.

    1. Re:The sky is not falling. by phantomfive · · Score: 1

      In other words: it's ok to follow secure procedure and make everyone mad, but don't be a jerk about it. Make sure it is clear why you are doing what you are doing, and be calm.

      --
      Qxe4
    2. Re:The sky is not falling. by Anonymous Coward · · Score: 0

      This is one of them. The biggest difference between Terry Childs doing his job and the bumbling fools who later took down the network is that the bumbling fools fit in perfectly with San Francisco city employee politics.

    3. Re:The sky is not falling. by Ossifer · · Score: 4, Insightful

      In appropriate words: don't lie about you violent past, don't harass the person employed to do your background check, don't give false passwords to keep your boss' boss off your trail, don't admit to your co-worker that you're going to screw over your employer if they fire you, and most of all don't come afterward with the lame excuse of being the only IT God on the planet such that only you could ever possess the keys to the kingdom.

    4. Re:The sky is not falling. by Sycraft-fu · · Score: 1

      In particular you can see that because he gave out bogus passwords. When you read the news stories it turns out he stonewalled, but then finally handed over bogus passwords. Ok well that shows that in fact he intended to deceive people and keep control, not that he was just security concerned.

      If a professor were to come up to me and demand the root password to our servers, my answer would be "no." I wouldn't give them a fake password. Why? Because policy says they can't have it, and that's what I'm following. However if my boss asked for the root password (not that he'd need to, he has it too) I'd give it to him, since he can have it. In neither case would I consider giving a fake password, that is underhanded and counterproductive.

      To me is that right there is what really seals it as a case of him being malicious. He wasn't just concerned and/or misinformed about policy. He knew what he had to do and chose to try and deceive people.

    5. Re:The sky is not falling. by dbIII · · Score: 1

      In appropriate words: don't lie about you violent past,

      Or indeed in posts where you are telling people not to lie - such as the "don't harass the person employed to do your background check" bullshit.
      I know if some unauthorised person was in the office of the person in charge of computer security after hours pulling out their hard drive I'd want to know what they were doing as well, and if that is read as harrassment so be it. I don't know how you think that can be twisted into a "background check".
      I think the lesson is to meekly resign like the former person in charge of computer security did instead of exposing yourself to jackboot tactics of the people that escalated a simple workplace disagreement into a huge drain on taxpayers funds. Does San Francisco really have the money to spend on bullshit such as this?

    6. Re:The sky is not falling. by Anonymous Coward · · Score: 0

      In particular you can see that because he gave out bogus passwords. When you read the news stories it turns out he stonewalled, but then finally handed over bogus passwords. Ok well that shows that in fact he intended to deceive people and keep control, not that he was just security concerned.

      If a professor were to come up to me and demand the root password to our servers, my answer would be "no." I wouldn't give them a fake password. Why? Because policy says they can't have it, and that's what I'm following.

      How about a professor comes up, tells you they are your new boss and demand the password or threaten you with what is apparently a 5 year jail term if you don't give it? Do you violate your security policy, potentially resulting in a denial of service for which you are liable, or do you refuse to disclose the password to someone you do not know is actually authorized to have it, and go to jail for that?

    7. Re:The sky is not falling. by Nyder · · Score: 1

      In appropriate words: don't lie about you violent past, don't harass the person employed to do your background check, don't give false passwords to keep your boss' boss off your trail, don't admit to your co-worker that you're going to screw over your employer if they fire you, and most of all don't come afterward with the lame excuse of being the only IT God on the planet such that only you could ever possess the keys to the kingdom.

      does that include don't say "The best way to make money is to start a religon" then a decade later start up a religon?

      --
      Be seeing you...
    8. Re:The sky is not falling. by Ossifer · · Score: 1

      Or indeed in posts where you are telling people not to lie - such as the "don't harass the person employed to do your background check" bullshit.

      Bullshit? Do your research: SF Examiner Article:

      • "In June of 2008, Childs allegedly confronted an investigator looking into the matter, taking her photograph with his cell phone and harassing her when she showed up at his work area. "
    9. Re:The sky is not falling. by NeoSkandranon · · Score: 1

      "I know if some unauthorised person was in the office of the person in charge of computer security after hours pulling out their hard drive I'd want to know what they were doing as well, and if that is read as harrassment so be it."

      And you wouldn't simply call the police...why?

      --
      If you can't see the value in jet powered ants you should turn in your nerd card. - Dunbal (464142)
    10. Re:The sky is not falling. by dbIII · · Score: 1

      She was removing the hard drive of his co-worker and not investigating him. Hence my accusation that you were lying by pretending that was a background check on Childs. I apologise if you were not lying but instead simply ignorant of what has been extensively reported - but that's still no excuse for making shit up and accusing others of not reading the articles.

    11. Re:The sky is not falling. by Ossifer · · Score: 1

      Supply official press links refuting the one I posted, or otherwise everyone will know that you are not just a jerk, but also a liar like your boyfriend, the violent two-time convict...

    12. Re:The sky is not falling. by dbIII · · Score: 1

      So in reponse to my accusation that you are making shit up you then make up some stuff like "your boyfriend, the violent two-time convict."
      You have made my point for me.

    13. Re:The sky is not falling. by Ossifer · · Score: 1

      So you admit you can't comeup with anything to refute the press article I cited... Liar.

    14. Re:The sky is not falling. by dbIII · · Score: 1

      I suggest you look at the link from the first Slashdot story on the Terry Childs case and you will see exactly what I mean. There are also the Paul Venezia stories on infoworld
      The incident we both referred to is Jeana Pieralde removing a hard drive from the office of DTIS Security Officer Nancy Hastings - not exactly a "background check" on Terry Childs is it? The way you have represented it as such is a nasty lie no matter what Terry Childs is actually guilty of in reality.
      You are the one putting up the bullshit so you are the one that has to justify it. I suggest doing it in the comments for the more recent story so that you can get your view out to more people and stop wasting my time with childish insults about sexuality.

  12. He did 2 just waiting for court let him out now an by Joe+The+Dragon · · Score: 2, Interesting

    He did 2 just waiting for court let him out now and give him the time that he did.

  13. ugh by nomadic · · Score: 4, Insightful

    'There are suddenly thousands of IT workers all over the country that are now guilty of this crime in a vast number of ways.

    Setting up and configuring system where they have sole access, locking out the actual owner of the system, arbitrarily deciding that their direct supervisors aren't "authorized users" (based not on any actual rules or policies but their own nebulous "best practices" decision and by the way anyone who thinks a network engineer should have the authority to lock whoever he wants out of the system, based entirely on his own discretion, is incompetent), and then refusing to provide system access when he was assigned other responsibilities not dealing with locked system, then repeatedly refusing to provide the information even after being imprisoned? Really? Thousands of IT workers guilty of that?

    1. Re:ugh by Anonymous Coward · · Score: 0

      arbitrarily deciding that their direct supervisors aren't "authorized users" (based not on any actual rules or policies but their own nebulous "best practices" decision

      Actually, the existing written SF policy was that your direct supervisor is NOT by default an authorized user.

    2. Re:ugh by Anonymous Coward · · Score: 0

      For a normal user, perfectly valid, but in Childs' case his supervisor was the COO. Completely different story.

    3. Re:ugh by Vellmont · · Score: 1

      You do realize that the law isn't written specifically about this case, right? So why then, do you bring up every single detail of the case as a means to exclude the other ways the law could be interpreted to apply to?

      The meat of it is about his refusing to provide passwords for 12 days. From what I hear the network remained up during that time. I think it's telling that when pressed, the people who want him in jail seem to focus on him being a dick (which he is), but fail to provide any real explanation as to what harm came to anyone during this period. The law is supposed to protect people from harm, right? Not just be an arbitrary set of rules set down from on high.

      If this was so incredibly harmful that passwords weren't available for 12 days because ONE person was a being a dickweed control freak.. aren't the people who designed and approved such a crazy system at fault as well? Why aren't those people liable for such egregious incompetence? I don't agree with what Childs did, think he's a huge dick, should have been fired, tarred and feathered. But sicking the law after him was just a power play by the city, and had nothing to do with protecting the public, property, or anything but some elected officials reputations.

      --
      AccountKiller
    4. Re:ugh by nomadic · · Score: 1

      So why then, do you bring up every single detail of the case as a means to exclude the other ways the law could be interpreted to apply to?

      You're missing the point; Childs wasn't dragged in just because he refused to give a password, he was convicted because of a series of arrogant and illegal decisions he made over a period of time. To get arrested for this kind of thing you have to do a lot of sequential, stupid things.

      aren't the people who designed and approved such a crazy system at fault as well?

      Childs designed the system. He designed it to the people who actually paid for it didn't have ownership of it.

      But sicking the law after him was just a power play by the city, and had nothing to do with protecting the public, property, or anything but some elected officials reputations.

      Oh come on, the undisputed facts are pretty clear. They didn't call the law right away, they called it after they couldn't figure what else to do.

    5. Re:ugh by Anonymous Coward · · Score: 0

      So if I wheel-booted your car and refuse to remove it for 12 days you're just going to shrug it off and walk away claiming no-harm no-foul?

      After all, I haven't damaged your car, it's perfectly safe and in fine working order. I'm just not allowing you to drive it.

      Would you take the blame for parking it where you parked it?

    6. Re:ugh by Vellmont · · Score: 2, Insightful


      Childs wasn't dragged in just because he refused to give a password, he was convicted because of a series of arrogant and illegal decisions he made over a period of time.

      Please be specific. What were these illegal decisions he made over a period of time?

      Childs designed the system. He designed it to the people who actually paid for it didn't have ownership of it.

      Pure nonsense. Nobody else knew what a password was? Nobody else understood the concept of multiple people having access? Sorry, but this is just pure bullshit. It's 2010, not 1950. The systems Childs used are all well known, and well understood. Everyone understands what a password is, and what only one person knowing a critical password means. The idea that Childs is soley responsible for knowing the failures of the system is just patently ridiculous on multiple levels.

      Oh come on, the undisputed facts are pretty clear. They didn't call the law right away, they called it after they couldn't figure what else to do.

      Which doesn't make it right.

      --
      AccountKiller
    7. Re:ugh by Anonymous Coward · · Score: 0

      Yeah fuck that, there are times when you gotta kick Network Blah Blah Jr. or IV out of the system while you get their superior on the line because they blew away three edge router configs, overwrote the repository (no not just a revision of a file, but the whole repository) to try and cover their mistake. I have done this before, and because of your attitude, you'll never understand someone like myself that takes ownership of the network, and my actions. Don't fool yourself, if you have the power to stop a bad thing (or, more bad things) and you let it happen you might as well have done it yourself.

  14. Not DoS by guspasho · · Score: 3, Informative

    Assuming the verdict is correct, Venezia writes, 'shouldn't the letter of the law be applied to other "denial of service" problems caused by the city while they pursued this case?

    Childs wasn't convicted of "denial of service", that's just rhetoric. He was convicted of computer tampering, as the linked Slashdot story explains in the summary.

  15. The case is very simple by SmallFurryCreature · · Score: 4, Insightful

    You got an upstart sysadmin who went on a powertrip and thought he was smarter then anyone else and therefor above any laws that only apply to lesser people.

    This is not uncommon with people who are highly intelligent but not to well versed in social skills. Not so much nerds but Mensa people. Like that reiserfs guy, thought he could get away with murder because he was smart and the police is dumb, they must be because they ain't him.

    Your assessment is 100% right and he had no call to judge the people asking for access to be unsuitable. His opinion simply did not matter at that time. It is like when a cop with a dog tells you to get down on the floor. That is not the time to start an argument. That is the time to get down on the floor and become part of how the justice system works, injustices included and part of the system, sucks to have it happen to you.

    If you ever find yourself in the same position as Childs, document EVERYTHING, in paper, print all emails and insist on written instructions, never verbal, and then do as you are told and get the fuck out of there.

    Do not argue with the system, you are not smarter. Do you know how you are not smarter then the system? If you think arguing with the system is a good idea.

    Childs is an idiot and yes, idiots go to jail. lets see him argue with Bubba about access to his ass.

    --

    MMO Quests are like orgasms:

    You may solo them, I prefer them in a group.

    1. Re:The case is very simple by binarylarry · · Score: 1

      I fail to see what this has to do with upstart.

      --
      Mod me down, my New Earth Global Warmingist friends!
    2. Re:The case is very simple by SanityInAnarchy · · Score: 1

      thought he was smarter then anyone else and therefor above any laws that only apply to lesser people.

      The way I read it, he was following the policy (law) to the letter. Seems like management were the ones who thought they were above any laws.

      Like that reiserfs guy, thought he could get away with murder

      Because not giving passwords over is exactly like murder.

      It is like when a cop with a dog tells you to get down on the floor.

      No, a cop with a dog is like a cop with a dog.

      If you ever find yourself in the same position as Childs, document EVERYTHING, in paper, print all emails and insist on written instructions, never verbal,

      Agreed.

      and then do as you are told

      I'd be less inclined to do as I'm told if I had everything documented that way.

      and get the fuck out of there.

      Oh, definitely -- though jail does make that harder.

      Also, you haven't presented any evidence that he wasn't, in fact, smarter than the system. The fact that he fought the system and lost doesn't make the system right, and it certainly doesn't make him an idiot, it just makes him a loser, in the most literal sense of the word -- "someone who lost."

      --
      Don't thank God, thank a doctor!
    3. Re:The case is very simple by nomadic · · Score: 5, Informative

      The way I read it, he was following the policy (law) to the letter.

      He was required to store system passwords in a central repository. He violated the policy by failing to do this.

    4. Re:The case is very simple by turbidostato · · Score: 1

      "The fact that he fought the system and lost doesn't make the system right, and it certainly doesn't make him an idiot, it just makes him a loser"

      Which, given the situation, is quite a sinonimous for "idiot".

    5. Re:The case is very simple by X0563511 · · Score: 1

      I like how you just made up a word (sinonimous) and took "just makes him a loser" out of context.

      --
      For large sets, this will be our guide even unto death, for the LORD will work for each type of data it is applied to...
    6. Re:The case is very simple by Tsunamio · · Score: 1

      Childs is an idiot and yes, idiots go to jail. lets see him argue with Bubba about access to his ass.

      I realize this is off topic, but it's a pet peeve of mine. Jail rape does happen on a wide scale, and it's a travesty. Making jokes about it seems to be the norm, but it shouldn't be. We don't actually sentence people to rape, because that's barbarous - right?

    7. Re:The case is very simple by Anonymous Coward · · Score: 0

      This is not uncommon with people who are highly intelligent but not to well versed in social skills.

      and statements like this are not uncommon with people who think they are BOTH highly intelligent AND well versed in social skills....and feel the need to preach.

      Like that reiserfs guy, thought he could get away with murder because he was smart and the police is dumb, they must be because they ain't him.

      irrelevant scenario. while it is true he's intelligent and a geek and a murderer, it does not indicate cause. Correlation is not causation etc..

      Your assessment is 100% right and he had no call to judge the people asking for access to be unsuitable. His opinion simply did not matter at that time. It is like when a cop with a dog tells you to get down on the floor. That is not the time to start an argument. That is the time to get down on the floor and become part of how the justice system works, injustices included and part of the system, sucks to have it happen to you.

      so it's ok for the cop to abuse the situation because he can, but not ok for you to lose respect for the justice system? yeah that's reasonable. you must be one of those insecure trolls who makes himself feel more powerful by siding with the largest combatant. it is precisely this behavior that causes others to disregard your precious justice system in the first place. in the case of childs, it was his distrust of the system that caused him to behave as he did regarding the passwords. whether his solution was sound or not is another matter entirely.

      this whole issue is a symptom of the 'responsibility-without-power' trend coming down from authorities these days. it works like this: get someone into a doublebind where they are responsible for living up to/achieving something they have little power to do anything about (in child's case, follow some set of rules), and then when he inevitably 'breaks the rules' in an attempt to follow them, fire him/get him arrested, and hope he takes the bathwater out with him.

      If you ever find yourself in the same position as Childs, document EVERYTHING, in paper, print all emails and insist on written instructions, never verbal, and then do as you are told and get the fuck out of there.

      Not workable. society is rapidly hitting the point where the average person can no longer shield himself from the (often hypocritical) ultra litigious corporations and social groups (another example of 'responsibility-without-power) and do their actual jobs at the same time. it's time for that to end. life is difficult enough without adding artificial barriers to getting shit done that actually needs to be done. the fact is no one needed to be jailed over this. at worse, fire him and change the damn passwords. if that simple concept creates mountains of politics, then it's the system put in place by the shitty politicians running san fransisco that's the problem, not childs or anyone else.

      Do not argue with the system, you are not smarter. Do you know how you are not smarter then the system? If you think arguing with the system is a good idea.

      well if 'the system' was smarter, we wouldn't be teetering on the edge of financial and social collapse now would we? if you are as intelligent as you imply, then you must know what happens when people stop questioning authority. Of course, if you happen to be someone of significant authority I can see perfectly well why you'd like this scenario, but I guess you lack the ability to see what might happen if you suddenly lost that authority if/when your employer decided to use you as a sump pump for his dirty bathwater.

      Childs is an idiot and yes, idiots go to jail. lets see him argue with Bubba about access to his ass.

      So the gist of your message is: obey, dutiful servant, only idiots disobey and deserve prison? I've seen this attitude prevalent in those in charge these days, and it explains why things are going to the shitter so quickly.

    8. Re:The case is very simple by Anonymous Coward · · Score: 0

      Whole-heatedly agree.
      I disregarded all grandparent said because of that comment.

      I loathe people who think jail rape is an apt punishment for anything.

    9. Re:The case is very simple by Anonymous Coward · · Score: 0

      I like how you just made up a word (sinonimous) and took "just makes him a loser" out of context.

      Did you mean: synonymous ?

    10. Re:The case is very simple by jedidiah · · Score: 1

      One generally does not go to jail for being an idiot.

      One generally goes to jail for committing a crime because of being an idiot.

      There is a missing element here.

      --
      A Pirate and a Puritan look the same on a balance sheet.
    11. Re:The case is very simple by Pence128 · · Score: 1

      That brings up an interesting question. It can be one of two things: If you're in prison for a crime, either the law no longer applies to you for the duration of your incarceration, or you have no rights. Which is it?

      --
      404: sig not found.
    12. Re:The case is very simple by kent_eh · · Score: 1

      ... thought he could get away with murder because he was smart and the police is dumb, they must be because they ain't him.

      Actually, that seems to be the mindset of most criminals.
      Which ultimately makes the police's job easier.

      --

      ---
      "I can't complain, but sometimes still do..." Joe Walsh
    13. Re:The case is very simple by Anonymous Coward · · Score: 0
      Childs is an idiot and yes, idiots go to jail. lets see him argue with Bubba about access to his ass.

      What the f@@ck is wrong with you people? Everyone should be raped in jail? Important part of the experience?? And we're not talking about murderer or rapist here - we're talking about minor (2-5 years) lawbreaking. You, sir, are a an idiot yourself.

    14. Re:The case is very simple by Nyder · · Score: 1

      It is like when a cop with a dog tells you to get down on the floor. That is not the time to start an argument. That is the time to get down on the floor and become part of how the justice system works, injustices included and part of the system, sucks to have it happen to you.

      No, you get down of the floor because you know the cop will let the dog loose on you.

      Not because of the way the justice system works, it's called FEAR OF BEING BITTEN.

      I supposed when the priest told you to drop your pants and bend over, you did it because that's the way the church works?

      --
      Be seeing you...
    15. Re:The case is very simple by turbidostato · · Score: 1

      Did you mean: synonymous ?

      Sorry, my fault. I'm Spanish and in my language it'd be spelled with 'i', hence my mistake.

  16. lesson learned by Anonymous Coward · · Score: 0

    When you don't hand over the passwords, and the mayor comes to visit you in jail....you say "I'm sorry, but incarceration appears to have a profound effect on my memory. You know what would improve my memory considerably? MY IMMEDIATE RELEASE and a signed statement that you understand that I was just trying to DO MY JOB."

    I'd not have handed over San Franciso backbone passwords in a teleconference either.

    If they wanted a more secure and reliable mechanism for storage, they could have specified one. As an administrator, he believed that the systems were at risk and changed the passwords to secure them. Totally within scope of duties. Justice system is broken, but that's no surprise.

    You know a study that no one will do? Study of the demographics, employment status, and intelligence level of your average jury these days as compared with the general populace. No matter how low an opinion you may have of humanity, I can assure you that what passes for a jury these days is scraping the VERY BOTTOM of that barrell.

    1. Re:lesson learned by Skarecrow77 · · Score: 1

      Really? The last jury I served on, from the College student to the 69-year-old grandmother, seemed to have no problems comprehending pretty much exactly what each count against the defendant meant, and whether he voilated the letter of the law, even if he didn't mean to.

      In the one instance we were confused as a whole, we just asked the Judge. You do know that the jusge is at your disposal to answer any legal questions you may have about how the law is written, right? We had to have him explain a subsection that was written in a confusing manner.

      There were for sure some idiots and or biased people on the intial selection panel, but the Judge himself booted some of those for various reasons, and the prosecution and defense attorneys did a damn good job of getting rid of the rest. That's their -job- remember?

    2. Re:lesson learned by Anonymous Coward · · Score: 0

      And they could have slammed him right back in afterwards because they signed that under duress, and thus it can't be held against them.

    3. Re:lesson learned by Anonymous Coward · · Score: 0

      "In the one instance we were confused as a whole, we just asked the Judge"

      I would urge an amount of caution in trusting the judge, a few years back a jury didn't want to convict a defendant of something (I think it was minor drug possession, and the defendant was going to spend quite a bit of time behind bars) so they asked the judge if "Jury Nullification" was legal, the judge said something to the effect of "there is no such thing as a legitimate jury nullification" which of course the jury interpreted as "we legally can't use jury nullification". I believe the case went to SCOTUS and they upheld that Jury Nullification is a right, but judges can make it sound like it isn't if asked. And before someone pulls that "well the law is the law" crap, would you vote to convict a parent for "child pornography" for taking pictures of their half naked children playing in a mud puddle (for the sake of this argument lets assume that it is proven that there was no malicious intent in taking or keeping the photos) knowing that that conviction would result in them spending the next 20 years in prison. I never want to meet the worthless husk of a human who would.

      Jury Selection

      I've always wondered how Jury Selection ISN'T abused. What objective method can be used to prevent the prosecution from stacking the deck in their favor? An example would be a racially charged trial, a black defendant is accused of killing a white individual, the defense argues for excluding most of the white jurors, the prosecution argues for excluding most of the black jurors, the judge is (black or white, choose one) and is possibly racist. How does the system prevent the jury being stacked?

  17. Obligatory analogy by dingram17 · · Score: 1
    From the wording of the judgement, it sounds as if you were the City heavy vehicle supervisor and your manager came along and demanded the keys for a very large tip-truck and you refused because they didn't have a heavy vehicle licence that you would be charged with vehicle theft.

    It sounds like the procedures in place at SF City were weak. In the truck analogy, the rules may require the keys be handed to management when requested, but only a suitably licensed driver could use those keys and operate the vehicle (there are rules like that, they're the Road Rules). Perhaps the IT Dept. needed something equivalent whereby management could possess username/password but were not permitted to use them unless appropriate qualifications/certifications/competencies were held.

    Terry sounds a bit like the truckie that thinks no-one else can drive as well as he/she can so refuses to hand over the keys to 'their' truck. If there were IT admins working for the city that had the appropriate alphabet soup behind their name then management (which goes all the way to the mayor) could provide the access details to those people for specific tasks.

    Now, for the Tui's advert: 'Yeah, Right ...' The PHB is going to use the passwords to have a play themselves to remind themselves of the 'old days', forgetting that when they were trained in MIS they were using punchcards and teletypes, and networking was something that you did at parties. I can see why Terry did what he did, but the letter of the law can be a PITA sometimes. Does California have the equivalent of the GSA that could go through the SF City Council like a dose of the salts and clean things up?

  18. Re:In the by Anonymous Coward · · Score: 0

    The ramification, that is.

  19. In the meantime by countertrolling · · Score: 1

    Getcher damn waivers! Or you're going to jail! Stand up goddammit!

    --
    For justice, we must go to Don Corleone
  20. It's his own damn fault. by Anonymous Coward · · Score: 0

    Setup a common authentication scheme and disable your account as your last act.

    1. Re:It's his own damn fault. by TimSSG · · Score: 1

      I do not think most network routers support that option.
      Tim S.

  21. qual application of justice??? LOL by CPE1704TKS · · Score: 5, Insightful

    You've got to be kidding. Do you honestly think you can go back to prior cases and use that to show how something is or isn't a crime?

    What matters is how good your lawyer is and what sort of strings they can pull. Obviously, this guy's lawyer wasn't as good as the other guy's lawyer.

    The rules that apply to us DO NOT apply to rich people. Stop believing for one second that they do. Look at some black dude that goes to jail for 3 years for stealing bread vs. the Wall Street banksters that steal billions and get multi-million dollar bonuses.

    Marc Rich was convicted of tax evasion, and fled to Switzerland. It took $250,000 in donations to Bill Clinton for him to pardon him on his last day in office.

    There is no justice, all there is is how much money you have to spend to grease the wheels of the system.

  22. No kidding by Sycraft-fu · · Score: 3, Insightful

    Only way I see you being "at risk" is if you are an asshole, or the policies are extremely unclear. In the event of the second case, well then take it upon yourself to get them clarified.

    Personally, I'm not worried. Here our policy is that various critical information, including things like root passwords, has to be kept in a safe. My boss is responsible for all that. Also, all our IT staff has the passwords for everything (in theory, there are some I can't remember because I never use them). So, I'm not worried about a situation where I have sole access to a system an am being pressured to divulge the password. They are stored in a location per policy, and the people who can access them are specified by policy. All I need to do is look at the policy and make sure I follow it, and also make sure that should I set up a system that uses a special password for some reason, it gets documented.

    Always remember: They aren't your systems, it's not your network. They belong to the organization that you work for. That means said organization gets to decide who gets what access. You can, and should, have input on that policy, but you can't unilaterally declare that you are the only one.

  23. This is not a threat by Anonymous Coward · · Score: 0

    Unless you have your head firmly buried in your ass as Mr Childs did. Seriously his actions do not seem those of someone that should have any sort of power. He wielded his wand to say that no one else was worthy of the right to access the information that was not his. If at the point that it became obvious that he would be arrested he thought that somehow his actions were valiant and necessary to save the citizens of the city, his complex had blossomed out of control. A rational person would have cut their ties at that point and moved on. Anyone seeking to do real damage will still do it, most likely not someone that works in the department. Except for Mr Childs.

  24. Can someone please explain the crime? by junglebeast · · Score: 1

    I have googled and read a dozen articles about Terry Childs and still cannot find a single article that actually explains what he has done wrong and what this means.

    So far, all I can tell is that Terry Childs refused to give out passwords (private information) to somebody else who asked for those passwords. What is illegal about protecting the privacy of your users? How is this in any way related to denial of service or cyber crime?

    1. Re:Can someone please explain the crime? by Anonymous Coward · · Score: 0

      His entire real crime boils down to....

      He pissed off his boss.

      Thats it. Thats the entire problem right there.

      Now normally that wont get you in jail. But they decided to make it happen so they look good and the evil hacker terry childs takes any and all blame for this monumental fuckup.

    2. Re:Can someone please explain the crime? by The+Moof · · Score: 1
      Here and, to a broader extent, here is the best info I've read on the subject.

      So far, all I can tell is that Terry Childs refused to give out passwords (private information) to somebody else who asked for those passwords.

      He refused to give out the system management passwords to people who were supposedly authorized to have them. Then later, refused to give them to his successor after being reassigned to a new position. After reading what went down, he sounds more like he was being an egotistical jerk more than a champion of security.

  25. Give me an effing break by Anonymous Coward · · Score: 0

    The guy broke the law and deserves to be sentenced. When you are a system administrator for the city you lose the right to act like a bratty 5 year old child.

    This verdict does NOTHING to affect other sysadmins. If other sysadmins break the law on purpose like Child Terry did, they will be sentenced.

    If Child Terry wants to act like a 5 year old and hide password, he should hang out on Slashdot for a while. Plenty of other 5 year old attitudes here - such as the people who are saying he should not be charged! LOL, pathetic.

  26. Before everybody gets their shorts all twisted . . by pushf+popf · · Score: 3, Insightful
    The three cardinal rules if IT would have protected him:
    1. Remember: It's not your hardware, network or data. You just work there.
    2. When your boss asks you for the password, give it to him.
    3. Don't be a dick.

    IMO, he got what he deserved, and nobody else has anything to worry about unless they plan on breaking the above rules. (Especially #3)

  27. Jury Nullification by John+Hasler · · Score: 1, Offtopic

    If the letter of the law is what convicted Terry Childs, then the law is simply wrong.

    That is what jury nullification is for. Unfortunately, most jurors don't know about it and the judges refuse to tell them. Thus the FIJA .

    --
    Warning: this article may contain humor, sarcasm, parody, and perhaps even irony. Read at your own risk.
    1. Re:Jury Nullification by BitZtream · · Score: 1

      If you think the jury was wrong, you should probably get the case facts and stop basing your opinions on what some shitty, more than likely unemployed slashdotters who not only think the guy is right, but don't even realize why the situation should have never occured.

      He didn't follow proceedure in the first place ( by not storing the passwords in the system the city implemented for this purpose) ... Then tried to use some policies that applied to end user passwords ( not system admin passwords ) to justify his bullshit. What's more, he wasn't even following thouse policies properly.

      The guy did absolutely nothing right because he was acting like an immature spoiled brat.

      No sysadmin with half a clue is bothered by this, or is 'afraid of the ramifications')

      --
      Persistent Volume manager for Kubernetes - https://github.com/dwimsey/openshift-pvmanager
    2. Re:Jury Nullification by harlows_monkeys · · Score: 1

      No, that's not what jury nullification is for. Jury nullification is for dealing with a bad law when all the other mechanisms for dealing with a bad law, such as getting the legislature to change the law, have broken.

      Jurors aren't told about nullification because to do so would lead to widespread injustice. Juries would not only use the power to let people off who are guilty (often for reasons other than a bad law, such as because the person is white and the victim is not), but they would also use it to convict people who are not guilty because the jury doesn't like something about the defendant (see the South from the mid 19th to mid 20th centuries for many many examples). Since juries don't have to say why they convicted, those wrongly convicted would not be able to count on an appeal to save them--the appeals court won't know that the jury convicted based on, say, race rather than on the evidence.

    3. Re:Jury Nullification by westlake · · Score: 3, Informative

      That is what jury nullification is for. Unfortunately, most jurors don't know about it and the judges refuse to tell them

      The home town boy, the white bread kid, escaped the noose. The black man was lynched.

      That has always been the reality of jury nullification - and the geek - the outsider, the prick, the wierdo - who looks to nullification for his salvation is a a god-damned fool.

  28. broad generalizations with no back up by Anonymous Coward · · Score: 0

    the post is making very broad generalization with zero backup of any claims. Just exactly how are many IT professionals going to be affected? This is just false story to bait the readers. There is no story here. They guy was a nut-case who broke the law and common sense. All this warm and fuzzy talk of he built this network as his "baby". last I checked, babies need diapers and care. This is a bunch of inanimate iron with a goof-ball maliciously running it like a 5-year old.

  29. Re:Before everybody gets their shorts all twisted by Anonymous Coward · · Score: 5, Insightful

    You're breaking rule #3.

  30. Re: Initiative by biryokumaru · · Score: 3, Informative
    --
    When you're afraid to download music illegally in your own home, then the terrorists have won!
  31. No, absolutely not by Sycraft-fu · · Score: 2, Insightful

    I mean the keeping of a backup with heavy encryption is certainly defensible. After all you might want to make sure you have the configurations in case you are away on vacation and get a panicked "Oh my god we blew up the network!" call. Of course you would want said data heavily encrypted, in case your laptop was stolen.

    However when those are the ONLY copy, other than the running config? Hell no, that is a blatant attempt to lock others out. Reliability of the service must always come first. So for one, the configs should be stored on the system flash. There's no security risk there, to get at that you either have to have enable access to the system, or be at it physically. In either case you can already do what you want. Also, I'd want other backups stored on a local configuration server somewhere, in case a switch just shit itself and you had to restore to a completely new one.

    The only result of the situation he set up was to make everything critical on him.

    1. Re:No, absolutely not by slashqwerty · · Score: 1

      Of course you would want said data heavily encrypted, in case your laptop was stolen.

      At first thought, that makes sense. But the backed-up and encrypted data was the network configuration. Is that really a secret? Is there any reason you couldn't post it on the internet and let everybody see it?

    2. Re:No, absolutely not by Sycraft-fu · · Score: 1

      Sure, few reasons:

      1) There might be plain text passwords in there. Depending on the device and the way it is configured, there can be plain text passwords in the config file. Not the best security, but then you have to have either physical access or enable (root) to see them so not a huge deal.

      2) Even if all the passwords are encrypted, the hashed version is in the config. So that gives people something to start cracking your passwords with. Sure if it is a good password it could take time, but why give them the opportunity? Also maybe the has is later discovered to be not as secure as previously thought.

      3) There might be information about your network setup that would be useful to someone trying to attack it. I can't think of a good example, but it is a possibility.

      In general, configurations of equipment are just the kind of thing to keep secret. While obscurity shouldn't be your only security, it helps. There's no reason to go broadcasting things. I mean, would you want to give me your IP address and a copy of your /etc/secret (or SAM) file? In theory, that shouldn't hurt anything. If your password is good I shouldn't be able to crack it before the sun goes dark. However it is a risk you wouldn't want to take. For example in the event of a SAM file you might discover that it stores LM password hashes for passwords shorter than 14 characters, and that I can crack those in a day because they are weak. Likewise a vulnerability could always develop in one of the newer hashes that would allow me to crack it fast. Best I simply don't have it, then it's no risk.

  32. SF is criminally stupid by unix_geek_512 · · Score: 4, Insightful

    SF is criminally stupid, that's all there is to it. They've wasted taxpayer money over a case that should never have been brought.

    Their own employees and contractors caused a ton of downtime trying to get control of the network. If they'd left things alone there wouldn't have been any downtime.

    Not to mention they violated they guy's constitutional rights over something that could have been resolved amicably within 24 to 72 hours.

    Instead, they acted like a totalitarian regime and threw the guy in jail to break his will to resist.

    It's the people in charge of SF that should be prosecuted not this guy.

    Did he act like a damn jerk? You Bettcha! Did the city act like Ioseb Besarionis dze Jughashvili in 1936-1938? Heck yeah!

    Anyone in IT should be worried about ending up like this guy if they anger the SF city government in any way, this could be one heck of a bad precedent.

    Semper Fi Comrades

    1. Re:SF is criminally stupid by Kenja · · Score: 2, Insightful

      You do not "leave things alone" when the only person who has access to your network equipment is a disgruntled ex-employee.

      --

      "Have you ever thought about just turning off the TV, sitting down with your kids, and hitting them?"
    2. Re:SF is criminally stupid by Nyder · · Score: 1

      You do not "leave things alone" when the only person who has access to your network equipment is a disgruntled ex-employee.

      You don't make it so only 1 employee has the only access to everything.

      And if your stupid enough to do that, you don't fire him.

      --
      Be seeing you...
    3. Re:SF is criminally stupid by dkf · · Score: 1

      You don't make it so only 1 employee has the only access to everything.

      And if your stupid enough to do that, you don't fire him.

      That's an utterly unhelpful statement. Yes, the city should not have permitted things to get into that situation, but they did and reversing time isn't an option. Fundamentally, it was the City that owned the network; they paid for it, it was theirs. All the authority that Childs ever had was because it was delegated to him by the City. Thus when the City decided it was no longer delegating any authority to him, Childs ceased to have any right to deny access. (Yes, the City may well have been a bunch of dicks, but that should have been a matter for an employment tribunal or something like that, and not an idiotic tussle over network administration access.)

      He was also totally not following best practices by not having a strategy in place to cope with his sudden accidental death, e.g., in an auto accident, or pulmonary aneurysm, or being hit by a meteorite, or any number of stupid things that could happen. No, I've got no sympathy for Childs at all. But I won't be working for the City either (even if I was living in the right part of the world and was legally able to do so).

      --
      "Little does he know, but there is no 'I' in 'Idiot'!"
    4. Re:SF is criminally stupid by BitZtream · · Score: 1

      Their own employees and contractors caused a ton of downtime trying to get control of the network. If they'd left things alone there wouldn't have been any downtime.

      For how long? Wait till a real failure occurs and not be able to do anything about it? You've never been an admin, clearly.

      Not to mention they violated they guy's constitutional rights over something that could have been resolved amicably within 24 to 72 hours.

      Yes, if Childs wouldn't have tried to hold the city hostage it could have been over very quickly. But he didn't, he thought he was in control and the city would cave. He was wrong on so many levels. He got what he brought on himself, you're an idiot if you can't see that. He could have ended it at any instant he wanted to.

      Instead, they acted like a totalitarian regime and threw the guy in jail to break his will to resist.

      So what you think should have happened is he should have been left to do whatever the hell he wanted, and the city should have just left everything the way it was and not do anything because it was working at the time ... I don't know how to respond to such a retarded statement, wow ... just ... wow.

      It's the people in charge of SF that should be prosecuted not this guy.

      No, blackmail is illegal, which is what this was, try again.

      Anyone in IT should be worried about ending up like this guy if they anger the SF city government in any way, this could be one heck of a bad precedent.

      Any moron who goes through what this idiot did rather than just turning over the passwords when they get fired deserves to be treated just like him. Had he actually followed the policy they wouldn't even have had to ASK for the passwords as he would have stored them in the cities password management system.

      Everytime I see a post like yours I just laugh at how junior admins with half a clue side with idiots like this. Any halfway competent admin would have never been put in this situation in the first place. Any halfway intelligent human being would have just turned over the passwords and went looking for a new job.

      Instead, this idiot will sit in jail and will never work anywhere in the IT industry again. You can act like he's a hero and you should make sure the next time you go look for a job you tell them exactly how great this guy was, save them the trouble of dealing with you and having to find out the hardware that you're worthless.

      The reality of it is, the fact that the initial situation happened in the first place means he was a shitty admin. He may just be stupid or (the likely reason) he was just trying to blackmail them, eitherway, he's a waste of oxygen and food supplies.

      --
      Persistent Volume manager for Kubernetes - https://github.com/dwimsey/openshift-pvmanager
  33. Note that this involved a government. by John+Hasler · · Score: 1

    The city of San Francisco has cops, jails, and prosecutors. If the mayor gets mad at you, one of his employees, he can arrest you, throw you in jail, and prosecute you as he did Childs. A private company has to convince a disinterested prosecutor to go after you. While not impossible, that's much harder. I suspect that if the circumstances had been exactly the same except that Childs had been working for a private company he might have been sued but almost certainly not prosecuted.

    --
    Warning: this article may contain humor, sarcasm, parody, and perhaps even irony. Read at your own risk.
  34. The "taxpayers' money"... isn't. by Tetsujin · · Score: 5, Insightful

    "but it was bought and paid for by the City of San Francisco"

    Excuse me, it was bought and paid for by THE PEOPLE OF SAN FRANCISCO.

    Paid through our tax money, which also means it was paid for through *HIS* tax money.

    The government is supposed to serve the public trust and taxes are their main source of revenue - but I take exception to this attitude that, because someone pays taxes, government funds are somehow their money. It's not your money anymore, you gave it to the government. The fact that some of it once belonged to you (even if only on paper) does not entitle you to a stake in deciding how it is used.

    So, for instance: yes, your taxes pay the wages of the police. This doesn't mean you get to boss them around.
    Your taxes pay for the schools, but that doesn't entitle you to decide the curriculum.
    Your taxes pay for government infrastructure, but that doesn't mean you can micro-manage the government.

    That's not to say citizens in the US (or anywhere else, for that matter) have no stake in the government or its affairs - but the money paid in taxes has nothing to do with that. We have a stake in our government because the operation of the government affects our lives, in the short term and the long term. Would this stake not still exist even if the government could somehow operate without taxing its citizens? IMO bitching about "the taxpayers' money" is just a cheap way to get the attention of people who would otherwise not care.

    --
    Bow-ties are cool.
  35. Re:qual application of justice??? LOL by Anonymous Coward · · Score: 0

    He was never convicted, he didn't technically flee to Switzerland, he was already there. And apparently JOE IS GAY. I learned all this from wikipedia.

  36. Re: Initiative by Sycraft-fu · · Score: 3, Insightful

    Ummm that was way, way later in the proceedings. Read the news stories about it and BengalsUF's information. It wasn't like the came in to his office one day and arrested him. He was, repeatedly, asked for access and he wouldn't give it. He had created an extremely locked down system that only he could get in to. He refused to give others access, and gave out false passwords to try and throw people off. Finaly yes, it came down to a "You hand it over or we arrest you." He wouldn't so they did.

  37. Re:FIRST by biryokumaru · · Score: 1

    Wow, that's, like, 5 minutes late. You're really off your game lately. This must be the sixth article I've read today where the first few posts were actually relevant and interesting.

    --
    When you're afraid to download music illegally in your own home, then the terrorists have won!
  38. What if this was Google not a 'Government' by ozphobia · · Score: 1

    So if this was a private company, and one of the contractors decided to lock everyone one else out, would it have been different? Just because it is a public system doesn't make it right to 'protect the population from incompetent techs'.
    I have contracted for a number of companies, and many time I have had to create 'god' accounts so they can check the system, knowing full well that they may screw it up. But they pay me to do a job, they own the system, and they have rights to the system.
    Just because he thinks they will break it, doesn't give him the right to deny access. They may have wanted to give it to a more knowledgeable contractor.

  39. Wow. by nedlohs · · Score: 1

    The courts can actually get things right. Faith restored!

  40. The dictionary definition of tragedy by Eternal+Vigilance · · Score: 1, Troll

    Poor Terry Childs. Exactly the kind of personality that would have him be able to design a system resistant to sustained, vicious attack is what landed him in jail.

    Childs' only crime was exposing the ignorance and impotence of those who imagine themselves superior.

    The comments in the earlier thread reveal this was a case that called out for jury nullification. Sadly, this did not happen.

    Law is most fundamentally not about "justice," but about enforcing the rule of the powerful.

    1. Re:The dictionary definition of tragedy by Eskarel · · Score: 3, Insightful

      Terry Child's crime was being a borderline psychotic control freak, ensuring that no one other than himself had access to any system and that they could not easily recover the system and then refusing to turn over any of the passwords or configuration.

      This was not a system designed to resist sustained viscious attack. Apparently the switches all came back up from a power cut without any configuration and he was the only person who knew where the configurations or how to decrypt them. You could guarantee major downtime for the city just by cutting the power and hitting this guy with a crowbar.

    2. Re:The dictionary definition of tragedy by Eevee · · Score: 1

      "Tragedy is when I cut my finger. Comedy is when you fall into an open sewer and die." -- Mel Brooks

  41. Re:Before everybody gets their shorts all twisted by shitdrummer · · Score: 4, Insightful

    I would never hire anyone for a technical role who would give a password to an unauthorised person, including their boss (assuming they're not authorised to receive it).

  42. Re:Before everybody gets their shorts all twisted by llindeen · · Score: 1, Troll

    Your right... Childs thought the network was "his"... he was wrong. The passwords are intellectual property and as such he isnt allowed to keep it. He is however allowed to "forget" the passwords. Then there would have been nothing they could have done to him. His problem was he had an ego, and that ego will get him time in prison. In short, the guy mad a bad judgement call based oh his miscalculated self importance. He deliberately and purposely hid intellectual property. It has been in every employment agreement I have ever signed that you must surrender all passwords, notes, documents, sketches upon termination. Everything you design and implement on company time and on company systems is company property. That includes the passwords. Oh well. Looks like he will learn the hard way to read what you sign.

  43. Re:Before everybody gets their shorts all twisted by ClosedSource · · Score: 5, Funny

    Don't worry, you probably won't be hiring anyone until you stop calling yourself shitdrummer.

  44. Re: Initiative by biryokumaru · · Score: 5, Informative

    Actually, this is the best thing I've read on the subject, by far.

    --
    When you're afraid to download music illegally in your own home, then the terrorists have won!
  45. "I wouldn't likely get the job" by nurb432 · · Score: 1

    Or ANY IT job ....

    Now, after you are in, you might get them to sign something but good luck doing it during the interview.

    --
    ---- Booth was a patriot ----
    1. Re:"I wouldn't likely get the job" by david_thornley · · Score: 1

      The right time to negotiate anything like this is after the offer and before you accept. You probably want to bring it up in the interview so they don't get the idea that you're blind-siding them, but you don't need anything signed until the last moment.

      --
      "When you have eliminated the unacceptable, whatever is left, however improbable, must be the truthiness" - Holmes
  46. Turn in your keys by SoupGuru · · Score: 1

    Here's a question: if you get fired, are you legally obligated to turn in your building keys? I honestly don't know and I think there are some interesting similarities.

    --
    What doesn't kill you only delays the inevitable
    1. Re:Turn in your keys by gclef · · Score: 2, Informative

      Yes, you are. They are not your property, and never were.

    2. Re:Turn in your keys by PPH · · Score: 2, Interesting

      Building keys != sys admin passwords.

      Back when I left Boeing, I gave my replacement the passwords (root and others) for all the systems I was responsible for. Plus instructions on changing them as well as revising some configuration settings that directed system maintenance messages to my personal pager. For four years thereafter, I'd continue to get messages for various system events. Inspection of the message headers indicated that they had never disabled my various system accounts from which these messages originated. I never tried to log on, but I'm willing to bet that my passwords were never changed.

      My problem? I doubt it.

      --
      Have gnu, will travel.
  47. Re:qual application of justice??? LOL by nomadic · · Score: 1

    The rules that apply to us DO NOT apply to rich people.

    How do you explain Martha Stewart? R. Allen Stanford? Jeffrey Epstein?

  48. too paranoid to give it to your managers ?? by Anonymous Coward · · Score: 0

    If you are too paranoid to give it to your supervisor - then you have no confidence in him - and you should have resigned or asked for something else to do.

    If you accept him - take his orders and do it. Worst case - go over his head and talk to his boss..... but that is it.

    No 'I wont give you the passwords cos you are a jackass' nonsense. This is not your minutemen or local militia. This is a city administration...

    1. Re:too paranoid to give it to your managers ?? by fractoid · · Score: 1

      It depends on what supervisor means.

      'Supervisor' may mean your direct superior in your company's chain of command. In that case, he should already have access. If he doesn't, then hand it over.

      ''Supervisor' may mean a liason officer between your company and a client. In that case, hell no - but it's up to your boss (or his boss, etc) to make that call.

      --
      Rampant carbon sequestration destroyed the Dinosaurs' tropical paradise. I'm here to help repair the damage.
    2. Re:too paranoid to give it to your managers ?? by Coren22 · · Score: 1

      Except that Childs would have been breaking the law to hand over his password to his supervisor as that is directly addressed in the password policy for San Francisco.

      "Password Policy"
      As such, all County employees (including contractors, vendors, and temporary staff with access to County systems) are responsible for taking the appropriate steps, as outlined below, to select and secure their passwords.
      All system-level passwords (e.g., root, enable, NT admin, application administration accounts, etc.) must be changed on at least a monthly basis"
      "Do not share County passwords with anyone, including administrative assistants or secretaries.

      All passwords are to be treated as sensitive, confidential County information.

      Here is a list of things to avoid
      -Telling your boss your password.
      -Talking about a password in front of others.
      -Telling your co-workers your passwordwhile on vacation."

      http://www.sfgov.org/site/uploadedfiles/dtis/coit/Policies_Forms/CCISDA_security.pdf

      --
      APK likes to ask for responses to the same things over and over. Maybe he just likes the responses?
  49. Re:Before everybody gets their shorts all twisted by Ihmhi · · Score: 2, Interesting

    Wasn't the mayor his boss? I seem to recall that it has been stated many times that Childs would have given the passwords to the mayor and the mayor only just as he has been told to do. Unless new facts in regards to this have come to light then it is my opinion that he was doing his job.

  50. when did doing your job by teknosapien · · Score: 1


    become a crime? Other than the arrogance of your normal super sysadmin I really see him as doing his job.
    Apparently that powers that be don't understand what it involves is much more that moving and blocking 0's and 1's.
    It's thwarting social engineering, spurious attacks from with in the organization along with not letting under qualified users have access
    to critical systems
    Guess its time to turn in the keyboard
    For a lawn mower and shovel
    better yet a surf board!

    --
    no matter how good it is, it is human nature always wants to make things better
    1. Re:when did doing your job by timmarhy · · Score: 1

      he didn't have a job there anymore, that's the whole point. if you were sacked and refused to hand in the only set of keys to the building, what do you reckon would happen to you?

      --
      If you mod me down, I will become more powerful than you can imagine....
  51. Re:The "taxpayers' money"... isn't. by Ihmhi · · Score: 2, Insightful

    The government is supposed to serve the public trust and taxes are their main source of revenue - but I take exception to this attitude that, because someone pays taxes, government funds are somehow their money. It's not your money anymore, you gave it to the government. The fact that some of it once belonged to you (even if only on paper) does not entitle you to a stake in deciding how it is used.

    You are completely wrong on this point. You are entitled to decide how it is used. How much worse would government be if they could just do whatever the fuck they wanted with tax money with absolutely no opposition whatsoever? Pessimists and/or cynics will say that that is already the case, but even now there are at least *some* people fighting things they disagree with for whatever reason.

    You do have a say in how government resources are used because it is your money. Use the boxes - soap box, ballot box, jury box, ammo box (in that order).

  52. Bad Laws? by IonOtter · · Score: 2, Insightful

    "I know no method to secure the repeal of bad or obnoxious laws so effective as their stringent execution." - Ulysses S. Grant

    --
    [End Of Line]
  53. Re:He did 2 just waiting for court let him out now by Anonymous Coward · · Score: 0

    Punctuation. Capitalization. Please use them. This isn't digg.

  54. Re:Before everybody gets their shorts all twisted by amirulbahr · · Score: 1

    It wasn't his boss. He was fired.

  55. Re:In the by Anonymous Coward · · Score: 0

    Ramificationing him in teh butt?

  56. Re:Before everybody gets their shorts all twisted by fractoid · · Score: 2, Funny

    He doesn't work there.

    --
    Rampant carbon sequestration destroyed the Dinosaurs' tropical paradise. I'm here to help repair the damage.
  57. Terry was naive. by stimpleton · · Score: 1

    Terry Childs was naive. I am not going to blow my own horn, I am not a technically talented as others, but I am a battle hardened motherfucker in the work place. If you dont think others won't turn on a dime and stab you in the back, especially in a public service roll then you need to open your eyes or you learn the hard way. As i have in the past, as as terry has now. there is no need to be an asshole, just vigilant.

    --

    In post Patriot Act America, the library books scan you.
  58. Re:Before everybody gets their shorts all twisted by Anonymous Coward · · Score: 0

    Are you actually in charge of a shop now? Doubt it!

  59. Jury a popularity contest? by redelm · · Score: 1

    So they convicted the nasty BOfH even though the nice city managers slipped up and did something they must not do. Feh! I don't think I trust American courts nor juries.

    The real effect of this case is costs. Everyone, particularly those with prosecutors on staff and even moreso those with BMfH will have to pay more to cover this "no-win" risk. I foresee a bunch of IT admin turnover as people Vote with their feet.

  60. Re:He did 2 just waiting for court let him out now by X0563511 · · Score: 1

    Er, what? Can you rephrase that in a way that is at least comprehensible?

    --
    For large sets, this will be our guide even unto death, for the LORD will work for each type of data it is applied to...
  61. This guy was a arrogant jerk. by techvet · · Score: 2, Insightful

    He plays peek-a-boo with the passwords and then tries to play Lord God of the network, as if he answered to no one. This guys gives other sysadmins a bad name. He was a Class A jerk. Perhaps he got bad advice from someone, but odds are very high his arrogance brought him down. Nothing new - it happens in all venues (entertainment, sports, business, etc.). I also blame management for letting it get to this point. It should never have been to the point where only he knew the passwords. They should be reprimanded as well unless he unilaterally changed them without their knowledge. Then he definitely deserves to be punished. What a jerk.

  62. Re:Before everybody gets their shorts all twisted by shitdrummer · · Score: 1

    Are you actually in charge of a shop now? Doubt it!

    Yes. Well, my section within our IT department in an organisation within the Banking industry.

    Password security is one of the questions I ask of all potential employees, as should any IT employer.

    Funny thing about banks, they kind of take security a bit seriously.

  63. Re:The "taxpayers' money"... isn't. by bws111 · · Score: 1

    You are entitled to voice your opinion and attempt to influence how it is used. You can do that using your boxes. You are not, however, entitled to decide how the money is used, as you have no legal authority to do so. Otherwise, everyone could just say 'I decide that all the money will be sent to my account'. Doesn't work that way.

  64. Re:The "taxpayers' money"... isn't. by timmarhy · · Score: 1
    wrong. you elect officals who then delegate to various people who decide how to spend the money. you have no legal or moral grounds to think you get a direct say in how this happens. the best you can do is lobby and write letters.

    every election you get to have your say by voting someone in or out based on the job they do.

    the reason you american's FAIL so spectacularly at this, is you have reduced your system to a totally polarised 2 party system where each side always justifies their parties failings to the point it takes 2 unpopular wars, a health care system that is the laughing stock of the 1st world and the worst financial crisis since the great depression before anyone will change their opinion on which side is the right one to vote for.

    --
    If you mod me down, I will become more powerful than you can imagine....
  65. He was wrong...it was illegal...he paid the price by Anonymous Coward · · Score: 0

    It is as simple as that.

  66. Proof CCIEs are not worth the time to hire by Anonymous Coward · · Score: 0

    This guy was a CCIE. Do not employ anyone that is one. This is proof they're only a bunch of ego driven shit-stabbers.

  67. anyone ever see that seinfeld episode by circletimessquare · · Score: 1

    where the mechanic absconds with jerry's car because jerry wasn't taking good care of it?

    the job of the IT admin is to do whatever the hell the OWNERS of a network decide to do with it. if the owners of a network want to give out all the user names and passwords, then that's their call. in what position do you believe the it admin is in to question that?

    otherwise, you have some sort of psychotic attachment to your network, you have boundary issues, just like that psychotic mechanic in the seinfeld episode

    terry childs is obviously guilty to anyone who isn't a psychotic it admin

    --
    intellectual property law is philosophically incoherent. it is your moral duty to ignore it or sabotage it
    1. Re:anyone ever see that seinfeld episode by PPH · · Score: 1

      the job of the IT admin is to do whatever the hell the OWNERS of a network decide to do with it. if the owners of a network want to give out all the user names and passwords, then that's their call. in what position do you believe the it admin is in to question that?

      As long as my job description says "do what the boss wants" and nothing about "maintain the security of the system and the integrity of the data", I'm fine with that. So I'll just sit here and wait for my moron PHB boss to tell me what to do.

      Back in a previous life, working along side unionized crew, they used to refer to this as "working to rules", which was a kind of work slowdown used during times of labor-management conflict.

      --
      Have gnu, will travel.
    2. Re:anyone ever see that seinfeld episode by Anonymous Coward · · Score: 0

      the job of the IT admin is to do whatever the hell the OWNERS of a network decide to do with it.

      Ok, true.

      if the owners of a network want to give out all the user names and passwords, then that's their call. in what position do you believe the it admin is in to question that?

      Ahh, but it wasn't the owner who said that. The owner is the city of San Francisco. It was a mid-level employee of the city who ordered Childs to hand over the passwords, contrary to the written password policy of the OWNER (the city).

  68. Re: Initiative by Anonymous Coward · · Score: 2, Informative

    It didn't come down to "You hand it over or we arrest you" it came down to Terry getting ready to flee the state without telling anyone the passwords and the police having to arrest him to make sure he didn't.

  69. Re:qual application of justice??? LOL by westlake · · Score: 1

    The rules that apply to us DO NOT apply to rich people.

    The geek might usefully compare his own income to the median for his city, county or metropolitan district - to see which side of the line he falls and how distant he is from the center.

    Do you honestly think you can go back to prior cases and use that to show how something is or isn't a crime? What matters is how good your lawyer is and what sort of strings they can pull. Obviously, this guy's lawyer wasn't as good as the other guy's lawyer.

    The geek tends to get the lawyering he deserves.

    If only because what he really wants to do is to play the lead in one of the EFF's street theater productions.

     

  70. Of course by Sycraft-fu · · Score: 1

    For one, they keys aren't your property. Just because someone gives you something to use, doesn't make it yours to keep. My work has a laptop I'm allowed to borrow, but I can't keep it if I leave their employment, that would be theft.

    Likewise, they have a right to decide who has access to what. So when you leave, if they decide you should no longer have unrestricted physical access to the building, they can take that away in the form of taking your keys. Should you make a copy or break in or whatever, you can be charged with trespassing or worse.

    When you leave employment, or even when you are employed, you have to give up access to things when asked and you can't lock your employer out. I mean you can still have a job and your employer says "We want your master key back, you are only allowed in to the building during normal hours," or "You no longer manage this server, give the root password to this new guy, who will then change it." Their stuff, their rules.

  71. Re:Before everybody gets their shorts all twisted by BlueBoxSW.com · · Score: 1, Insightful

    I agree with you, and I'm not all read up on the case, but I have to disagree with #2.

    Your login is, in many respects, an electronic signature. This system obviously had lots of logging and checking going on. Giving his login and p/w to someone else is a bad idea, especially if you think the whole mess is going to end up in a courtroom.

    What he SHOULD have done (IMHO) is create a login with equal access, and given the credentials to his boss, the mayor, the police, etc., and then let THEM, the more qualified people decide who should get the information.

    This way he upholds his obligations to his workplace, and passes the liability to someone better qualified to make the decision.

    Pretending that HE was the most qualified person to decide who got access seems to be where he went wrong.

  72. Re:Before everybody gets their shorts all twisted by dudpixel · · Score: 2, Funny

    Could I please have your password?

    --
    This seemed like a reasonable sig at the time.
  73. Re:Before everybody gets their shorts all twisted by sldghmr · · Score: 1

    Well said.

    The juror from ADP made a good statement saying that at the very least he could have created another admin account and handed it over instead.

    Really though, if he felt that way he would be ethically right to tell them he felt that way but if the boss continues with the request then hand it over. If they go in and ruin the system then he just got a lot of work to do and some extended job security while he builds it again.

  74. He did 2 years just waiting for his court date he by Joe+The+Dragon · · Score: 1

    He did 2 years just waiting for his court date he should get out now!

  75. Give me liberty or give me death by Anonymous Coward · · Score: 0

    Terry Childs should have just commited suicide rather than give up the password. (only because it would make for better reading).

  76. Free Terry Childs by Anonymous Coward · · Score: 0

    It's time for everyone in the IT industry that cares for the security of their company's network to write to Governor Arnold Schwarzenegger and demand that he commute this sentence. Further, it is time to write to our Congress Critters and demand that this act not be used for the prosecution of public officials that believe they are properly doing their job. Lastly, anyone that turns their passwords over to the CEO of their organization should never be liable for any criminal action, regardless of how long it took the CEO to realize that his underlings are incompetent boobs.

  77. interview with the netword engineer on the jury by 0WaitState · · Score: 5, Insightful

    Pretty interesting interview with one of the jury members, who appears to understand the issues. Terry Childs juror explains why he voted to convict

    The juror lays out the legal issues pretty effectively, and makes a compelling case for conviction on those issues, while also discussing the incompetence of the city's IT department. Apparently he does not believe in jury nullification.

    Personaly I disagree with the outcome on the basis that I think the City of San Francisco illegitimately used its combined capabilities as employer, and owner of a court system and police force to escalate a civil employment matter into a criminal case, and then jailed a man for 2 years pre-trial on a laughable pretext. But I appreciate this juror's willingness to discuss the issues.

    --

    Remain calm! All is well!
    1. Re:interview with the netword engineer on the jury by Anonymous Coward · · Score: 0

      According to that same juror, he wasn't arrested until he left the state and withdrew $10K from his savings. Childs made a huge number of really bad decisions.

    2. Re:interview with the netword engineer on the jury by Uncle+Warthog · · Score: 1

      So, removing your own money from the bank is an actionable offense there resulting in arrest? Also, while I can appreciate someone wanting to hang onto good, competent help, arresting them to keep them from crossing the state border sounds a little too extreme to me. Sounds like all the more reason not to work for the SF government.

  78. Re:Before everybody gets their shorts all twisted by Ifni · · Score: 1, Offtopic

    Really? Then why is it they consider my password and answering a personal question two-factor authentication? It's possible you work at one of the few banks that actually do authentication properly, but to generalize about the whole banking industry taking security seriously when they pull crap like that, and all but encourage identity theft is a little disingenuous.

    --

    Oh, was that my outside voice?

  79. IT Union by MrKaos · · Score: 1

    Better still, sysadmins need to get unionized...Until they do organize, they're not going to be treated as well as waste disposal workers (garbage men).

    Like it or not now this decision has been made it sets a world wide precedent. Until IT professionals recognise that collaboratively we are the best people to formulate the legal structure of the industry and how laws should be interpreted someone will always be dictating them to us.

    Simply put this situation, like many others, is an end product of our own inaction. We either control or be controlled.

    --
    My ism, it's full of beliefs.
  80. Re:The "taxpayers' money"... isn't. by kent_eh · · Score: 1

    The fact that some of it once belonged to you (even if only on paper) does not entitle you to a stake in deciding how it is used.

    Actually, you do.
    Every 4 years, at the ballot box.

    At least you get to say who you want making those proxy decisions on your behalf.

    --

    ---
    "I can't complain, but sometimes still do..." Joe Walsh
  81. Re:Before everybody gets their shorts all twisted by Alex+Zepeda · · Score: 1

    Unfortunately the mayor was not fired. :(

    --
    The revolution will be mocked
  82. Re:Before everybody gets their shorts all twisted by bendodge · · Score: 1

    As I understand it, he was required to log the passwords in a central database and didn't. That's what got him. He also carried the ONLY backup copy of the config on his person (heavily encrypted), gave his bosses fake passwords, etc. It reeks of job security.

    --
    The government can't save you.
  83. Re:Before everybody gets their shorts all twisted by Anonymous Coward · · Score: 0

    Well, I certainly hope you don't work for Bank of America... I had to deal with shitty password security for 5 years, within one of their non-BoA branded "sub-banks". I complained that I couldn't use special chars and got told it was a security risk to use them...

    I haven't used them since, nor will I ever use them again. 5 years of crap because of an employer lock-in...

  84. Re:Before everybody gets their shorts all twisted by idsfa · · Score: 1

    THIS.

    Rest of thread is people with ownership issues.

  85. Re:Before everybody gets their shorts all twisted by shitdrummer · · Score: 2, Insightful

    I'm not in the US, so I can't really talk about US bank security. But there is a difference between customer security and internal security.

    I'm dealing with systems that entire banking sectors use to transfer funds between each other. Many billions of dollars passing through these systems daily.

    Compare the risk associated with those systems to the risk of a customer losing thousands (even hundreds of thousands) of dollars. Many banks choose to wear the risk of fraud to make customer interaction easier. Not saying it's right or not, but there's always a trade off.

    Look at the way some banks (particularly in the US) hand out credit cards. They know that some people aren't going to pay their bills but they calculate (correctly) that the percentage of defaults will be low enough that the overall business will be profitable. They could get tougher with their customer selection criteria so that virtually noone defaults, but they realised they can make more money this way.

  86. Re:The "taxpayers' money"... isn't. by Eskarel · · Score: 1

    Wrong.

    You can't tell the government how to spend tax revenue, or how to utilize the things they bought with tax revenue. The money isn't yours and you don't own the things they bought.

    What you can do, is suggest how you'd like the money and resource to be utilized, and vote out people who don't utilize it that way. The job of the government is to govern, the job of the people is to choose the people who do the governing. That's how a representative government works, you don't make the decisions, you choose the people who do.

  87. Oh please can we stop this? by drolli · · Score: 1

    It has been discussed over and over. Two difficult persons collide in a job, something goes wrong, it escalates beyond the point of repairing the damage, some formal rules and orders are pulled out and thrown in the court - from there on its pure luck what happens. Court decisions about duties in the job etc. are always very uncertain, not only for admins.

  88. taxation without representation by SuperBanana · · Score: 2, Informative

    The fact that some of it once belonged to you (even if only on paper) does not entitle you to a stake in deciding how it is used.

    That's pretty effin' funny, given that this country was founded after a revolution based on the simple concept of being taxed but not receiving representation in exchange.

    So, uh, yes- if you're taxed, you damn well do get a stake in deciding how it is used here in the US. Fun fact: in the state where the revolutionary war started (MA), we have "town meetings"- and they're not the kind of Town Meeting you see politicians holding, which are basically just "get some people in a high school gym and have them ask you some questions."

    No, see: town meetings are where the town (anyone who wants to show up) debates and votes on damn near everything from policies to budgets. The rest of the year, the town is run by a town council, also elected.

    It's impressive to see an entire basketball court full of chairs, and 15+ rows on each side, full of town residents. Democracy in action.

  89. Lesson learned. by miffo.swe · · Score: 1

    Im a sysadmin and the lesson for me is, dont give a shit about security, protocol or third party victims in case of security breach. If some clueless middle manager asks me for the passwords to some very sensitive database, i will give them to him no matter what. For all i care he can sell them on Ebay. The only thing i will care about hence forth is getting a written order or atleast having a witness of me handing it over. I wont spend time in jail to prevent some idiot boss from making bad mistakes. Especially if i have to take crap like Terry for keeping security tight.

    --
    HTTP/1.1 400
    1. Re:Lesson learned. by jimicus · · Score: 3, Insightful

      Then - there's no nice way to put this - you are an idiot.

      There are established protocols for preventing this situation for coming up in the first place. Well, actually they're there in the event of you getting run over by a bus but they'd work just as well if you got fired.

      The established protocol is that the passwords are encrypted and a brief written explanation for how to decrypt them (be it key, file or passphrase) is kept somewhere secure such as a bank deposit box or in a sealed envelope in a safe to which few others have access.

      Yes, it does open the organisation to a certain degree of risk. But the risk is substantially lower than setting things up so that if you get run over by a bus, your former employer is totally screwed.

    2. Re:Lesson learned. by miffo.swe · · Score: 1

      "There are established protocols for preventing this situation for coming up in the first place."

      Call me an idiot all you want. The places that have those established protocols are few and far between.
      The problem is the suits that wants you to secure stuff but at the same time wants to be able to do whatever falls into their head at the moment.

      --
      HTTP/1.1 400
    3. Re:Lesson learned. by Uncle+Warthog · · Score: 1

      I agree with you 100% except for the idiot part.

      You're talking about a password escrow policy, a damned good thing to have in any case. He's talking about the actual risk you only briefly mention. How would what you're talking about here prevent or minimize the risk that he's talking about here? Answer: it wouldn't.

  90. Terry HAD a clear agreement by Anonymous Coward · · Score: 0

    Terry HAD a clear agreement. He couldn't tell his boss (not authorized) and he couldn't tell the Mayor (who was authorized) because there were non-authorized people in the same room as the Mayor and it was on speaker.

    The contract was clear.

    But he still got jailed.

    Your idea has already been tried and failed.

  91. Re:Before everybody gets their shorts all twisted by L4t3r4lu5 · · Score: 1

    Job security?! Damn right! I'm not condoning what he's done at all, but picture this situation (Not so far fetched in the current economical climate): If you've dedicated a large portion of your life making SF's network infrastructure bulletproof and awesome only to have your boss decide you're now superfluous, and he can save a few thousand dollars hiring a dude in an Indian cube-farm with a VPN connection to do the admin work, I'm fairly sure you'd take small steps to make sure you keep your job.

    This didn't happen, but it's not so hard to believe it could have.

    --
    Finally had enough. Come see us over at https://soylentnews.org/
  92. What if a limo driver refused to hand keys over? by George_Ou · · Score: 1

    Let's imagine a limo driver refused to hand over the keys of the car to a 19 year kid who is prone to fast driving. But the kid doesn’t like that driver so he gets his father to fire the limo driver, but the driver refuses to hand the keys over to the father. The father fires the driver and hires a new limo driver, but the original driver even refuses to hand the keys to the new limo driver. At that point the limo driver has effectively commandeered a car that does not belong to him which makes him legally and morally wrong. It doesn’t matter if a few Internet geeks cheer him on as someone who “stuck it to the man” because if they were in a similar situation, they would go to jail too and I would convict them if I were on the jury.

  93. Re:qual application of justice??? LOL by Rob_Bryerton · · Score: 0, Flamebait

    Awwww, look at the cute little cynical nerd & how he rails against THE MAN. How original.

  94. Re:Before everybody gets their shorts all twisted by Anonymous Coward · · Score: 0

    Your right...

    And your [sic] an idiot.

    Another subliterate joins the ranks of Slashdot - just what we need.

  95. Re:Before everybody gets their shorts all twisted by unitron · · Score: 1

    But there is a difference between customer security and internal security.

    Let me guess. Banks care a lot more about the latter than the former?

    --

    I see even classic Slashdot is now pretty much unusable on dial up anymore.

  96. Re:Before everybody gets their shorts all twisted by drooling-dog · · Score: 1

    I would never hire anyone for a technical role who would give a password to an unauthorised person, including their boss

    That's some job security for your new hire, isn't it? Unless you can become an "authorised person" merely by telling him/her that you are, which clearly defeats the purpose of authorization in the first place...

  97. Know very little by jav1231 · · Score: 1

    I never quite bought that he was only required to give passwords to the Mayor. If so, SF had a pretty screwed up system. I can tell you, if my boss wants the passwords to my system he gets them. You know why? Because I want my job. From the beginning, while I sympathized with Childs, he came off as a l337 who built up this huge kingdom in WoW and didn't want anyone to play with it. Give the passwords to your boss, keep a paper trail, if the system comes down you have all you need to defend yourself. Holding the system hostage was idiotic. That's not to say there isn't a case for his innocence, only that he's not completely innocent from what I can see.

  98. Anonymous Coward by Anonymous Coward · · Score: 0

    Ok, let me get this straight. The article states that among others his own boss asked for the passwords and he refused. Dude, come on. My boss already has the passwords locked away in case I get hit by the proverbial bus. This guy deserves what he gets for being a over protective IT jerk-mo.

  99. Re:qual application of justice??? LOL by drinkypoo · · Score: 1

    How do you explain Martha Stewart? R. Allen Stanford? Jeffrey Epstein?

    They didn't follow the rules that apply to rich people.

    --
    "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
  100. Re:Before everybody gets their shorts all twisted by pushf+popf · · Score: 1

    I would never hire anyone for a technical role who would give a password to an unauthorised person, including their boss (assuming they're not authorised to receive it).

    That's nonsensical. If you're not required to do what your boss says, he's not your boss.

    In any case, you're making an irrelevant distinction. If the boss wants the password, you give it to him. If the boss then blows up the network or sells the password to the Russians, that's his problem not yours. When law enforcement comes by, you say "It blew up right after my boss demanded the password"

    Childs has ego issues. He was just an employee, not Superman, and was not tasked with saving the universe, just with keeping the hardware running. Keeping the password safe from hackers is prudent. Not giving it to his boss even after the city demanded it was just being a dick.

    Rule #3. "Don't be a dick."

  101. Re:Before everybody gets their shorts all twisted by pushf+popf · · Score: 1

    Your right... Childs thought the network was "his"... he was wrong. The passwords are intellectual property and as such he isnt allowed to keep it. He is however allowed to "forget" the passwords. Then there would have been nothing they could have done to him.

    What possible up-side could there be to "forgetting" the passwords, except pissing everybody off and making it really hard to get another job?

    I just don't see an up-side in that action for anybody. The city would be need to pay to have their passwords reset, he'd still be out of work (although probably not in jail), but would be publicly known as "the guy who boned his employer when given the chance".

    Honestly, I'd hire someone who went to jail for his beliefs long before I'd hire someone with a "scorched earth" policy for job changes.

  102. Re:Before everybody gets their shorts all twisted by Coren22 · · Score: 1

    Rather difficult to create another admin account when they haul you off to jail instead. He was hauled off immediately after being requested for his password in a manner that was extremely suspect. Also, you have NO requirement to provide anything to your former employer after they have fired you.

    --
    APK likes to ask for responses to the same things over and over. Maybe he just likes the responses?
  103. Re:Before everybody gets their shorts all twisted by Coren22 · · Score: 1

    All you have said is accurate. He was also proved right about the incompetence of the people replacing him. The Fiber WAN ran perfectly fine until the passwords were given over, and then the new admins managed to crash it.

    --
    APK likes to ask for responses to the same things over and over. Maybe he just likes the responses?
  104. Re:Before everybody gets their shorts all twisted by hibiki_r · · Score: 1

    I wouldn't, and look for a different job quickly.

    However, if I did want job security, I'd not do stupid stuff like giving my boss fake passwords: The key to job security is to convince your boss that the operation can't survive without me. To do that, I should show them how dependent they are on me, not by giving them false information. Anything that makes me hard to replace and my employer doesn't understand isn't really providing job security, but will lower my reputation when I leave, as It'd not lower my chances of getting fired, but would make anyone that used to do my job badmouth my job in fron of my former boss.

    So kids, if you are going to be sleazy enough to follow job security practices, at least pick the ones that work.

  105. Re:What if a limo driver refused to hand keys over by Cro+Magnon · · Score: 1

    It seems more like this:

    After the driver refused to hand the keys to the 19 y/o, the kid shows up with an unknown adult, tells the driver he's fired and the unknown adult is the new limo driver. In THAT scenario, the driver is justified in not handing the keys over to anyone EXCEPT the father.

    --
    Slow down, cowboy! It has been 4 hours since you last posted. You must wait another few hours.
  106. You seriously don't know the chain of command? by George_Ou · · Score: 1

    Are you saying Terry Childs doesn't know who his boss' boss is or who the CIO or CEO is in his company? You're suggesting the Limo driver doesn't know the father who hired him? This *is* the "FATHER" showing up along with the police who surely would have demanded proof of ownership of the car. And don't try to tell me he thought it was fake police officers throwing him in a fake prison cell and that he hired a fake lawyer to defend him from a fake trial that led to a fake 5-year sentence in a fake prison cell. So stop giving me your fake arguments.

    1. Re:You seriously don't know the chain of command? by Cro+Magnon · · Score: 1

      The MAYOR was Terry's father. The guy demanding the "car keys" was just another employee. Granted, he was higher in the pecking order than Childs, but if Childs was only supposed to hand the keys over to the mayor, it was a serious breach of the rules for the boss to demand them.

      Based on posts from that juror on /. it sounds like Childs DID pull some asshat stuff that caused the jury to find him guilty, but that doesn't excuse the considerable stupidity and asshatery of the SF govt.

      --
      Slow down, cowboy! It has been 4 hours since you last posted. You must wait another few hours.
  107. Re:Before everybody gets their shorts all twisted by rutledjw · · Score: 1

    I agree with this. I'm pretty surprised so many people are jumping to this guy's defense based on some pretty off and esoteric arguments regarding details they know nothing about, e.g. "not knowing if the boss can have the password", etc.

    Not giving it to his boss even after the city demanded it was just being a dick.

    And that's the end of it, Mayor Gavin had to make a PERSONAL visit to get the password. Is HE authorized to have the password? I'm sure he made good use of it - gave it to the IT staff...

    --

    Computer Science is Applied Philosophy
  108. Re:Before everybody gets their shorts all twisted by rutledjw · · Score: 1

    You have to return the property of your former employer to the employer. That's not just physical items, but can include IP as needed to do your job. That's been in every severance agreement I've had the displeasure to give or receive. Passwords are in there.

    Not having seen the agreement, the password is owned by SF, not this admin. He had no right to withhold it; almost certainly he had an obligation as a part of his severance to provide it.

    --

    Computer Science is Applied Philosophy
  109. Re:Before everybody gets their shorts all twisted by sldghmr · · Score: 1

    Maybe I had bad info. What I read was he was being re-assigned, not fired, when originally asked for the account info.

    Dont get me wrong, I think the potential of 5 years in prison is extreme for this type of situation.

  110. Re:What if a limo driver refused to hand keys over by BitZtream · · Score: 1

    Too bad that isn't what happened to Terry Childs. He knew everyone involved and they were his superiors.

    --
    Persistent Volume manager for Kubernetes - https://github.com/dwimsey/openshift-pvmanager
  111. Re:He did 2 just waiting for court let him out now by Compaqt · · Score: 1

    He means that he has completed 2 years in jail just waiting for the trial, and that he should be let off for time served now.

    --
    I'm not a lawyer, but I play one on the Internet. Blog
  112. Re:The "taxpayers' money"... isn't. by Tetsujin · · Score: 1

    The fact that some of it once belonged to you (even if only on paper) does not entitle you to a stake in deciding how it is used.

    Actually, you do.

    Every 4 years, at the ballot box.

    Well, voting is kind of an incidental, minimal means of influencing the direction of the government. One can involve oneself in the decision-making process by activism or even entry into politics. My point is that it's not the money which grants us this privilege, or which governs the situations in which the privilege may be exercised.

    --
    Bow-ties are cool.
  113. the opposite is true as well by Anonymous Coward · · Score: 0

    I was fired from a job, the passwords demanded.
    The management misused the passwords, put themselves in a pickle.
    They threatened legal action on the grounds of my "sabotage" wheres they had actually screwed the DNS up and had no clue that they had caused it much less how to fix it. On advice I declined to fix it on the grounds that it would have given me unclean hands. Presumably on advice, the threats came to nothing.

    What saved me?
    Legal advice that had me write on the envelope: "By opening this envelope and using the passwords within you assume all responsibility for what happens next. You are hereby advised to engage the services of a suitably qualified profession system admin to open this envelope and operate the system for you". there followed a brief description of where the documentation was and the general disposition of the system.

    You can't refuse legitimate management instructions. it is their system, not yours. You must, however, as one skilled in the art make management aware of the risks they are taking on if they use the passwords without the requisite levels of technical proficiency. You are under no obligation to advise further once the employment has terminated - indeed you should not so advise, other than to repeat the "get a professional in" mantra.

  114. Re:The "taxpayers' money"... isn't. by n0tquitesane · · Score: 0

    It's not your money anymore, you gave it to the government.

    Perhaps you gave your money to the .gov, but mine was stolen from me. I have never agreed to pay them a cent, it was all done with out my consent.

    NQS

  115. Re:The "taxpayers' money"... isn't. by Dragoness+Eclectic · · Score: 1

    I can tell you're not an American--you're used to being a 'subject' rather than a citizen.

    I have the most fundamental moral and legal ground of all to think that I get a direct say in how my tax dollars are spent: "Governments are instituted among Men, deriving their just powers from the consent of the governed,"

    Taking your money and using it for one's own purposes without your consent is called stealing, and government that does it is a tyranny.

    --
    ---dragoness
  116. Re:The "taxpayers' money"... isn't. by Dragoness+Eclectic · · Score: 1

    Actually, we, "the people" consent to be governed, and delegate our decision-making authority to our representatives. The money IS mine, as I am a citizen of this country, I own my 1/300 millionth or so share of the things it buys, and I can tell the government how to spend my taxes. No guarantee they'll listen, but they generally do if a big enough collective of the citizen-owners yell about it. Governments don't work without the consent of the governed, especially this one.

    If my elected delegates don't do a good job of representing me, I (collectively) can fire them and elect someone else who will.

    Need to re-organize HR though; it's sticking me with really crappy interview candidates for the job.

    --
    ---dragoness
  117. one rule for them, one rule for us by Hognoxious · · Score: 1

    Were the requesters in a position to make, alter, or administrate the request?

    Why is that relevant? If I've got the root password on the finance box, I've got the password, whether or not I was in a position to blah bullshit blah bloody blah.

    Were they knowledgeable enough to know what they were asking?

    In my experience, yes, they usually are. You can't ask for something if you don't know it exists. If you know it exists but don't know what it is/does, you shouldn't be frigging about with it. That's basic common sense.

    I once had someone request sap_all on a production machine (this is like having root on a unix system; a user can do pretty much anything). He must have known what he was asking for (and if he was asking for something when he didn't know what it was, he's an idiot and he should read this). He was refused by three separate people, tried going over people's heads etc. Eventually he found someone compliant and stupid enough to do it. Even if ignorance is an excuse (which it isn't) any attempts after the first time were intentional and culpable.

    Also, most organizations have an acceptable use policy that employees must sign as part of enrollment. If it says anywhere in there that passwords are not to be shared, then how can your excuse stand?

    Actually quite often it means that they do end up in the position where they should not be dealing with specifics but rather guiding policy instead.

    The "ah, I'm special" excuse.

    If you don't have the balls to stand up to a request that is against written company policy then you deserve to get fired

    Internet tough guy alert.

    I have had one case where the request was one that really shouldn't be carried it out. I eventually carried it out

    Then people complain that IT doesn't get treated as a profession. Sure, I'll build this school that'll fall down ... just sign this disclaimer.

    What did you say earlier about balls? I'd leave that time at Enron off my resumé if I were you...

    --
    Confucius say, "Find worm in apple - bad. Find half a worm - worse."
  118. Re:The "taxpayers' money"... isn't. by sjames · · Score: 1

    Urm, in a democracy, that is, a government Of the People, By the People, and For the People, YES you absolutely DO have a right to a say in how the money gets spent and in how the police operate and in what the schools teach.

    This doesn't generally result in micro management, but in theory anyway, if a large enough group of people petitioned the government insisting on a new rule about who gets the enable passwords, then they should get their way. Good luck getting a significant fraction of the people worked up enough about the issue to actually petition the government...

    This is commonly tied in with references to taxpayer money and such due to another part of U.S. history. A big issue leading to the American Revolution was "taxation without representation", that is extracting tax money from the People without giving them any say in how it gets spent.

  119. Hit-by-bus Envelope by Gunfighter · · Score: 1

    We keep a "hit by a bus" envelope sealed and secured in a safe just in case something happens and root access is needed to the servers. Curious as to why that wasn't SF's policy and how other municipalities handle these sort of security issues.

    --
    -- Stu

    /. ID under 2,000. I feel old now.
  120. Re:Before everybody gets their shorts all twisted by MikeBabcock · · Score: 1

    Ditto.

    If someone's authorized to have the password, they'd have it already.

    If there needs to be a secure handover of power situation, that should already be in place before it needs to be done.

    In fact, if there's anything I'd want to ask Childs its whether he'd ever pressured management for a proper disclosure scenario to be documented.

    "In the event of my death or demotion, passwords can be retrieved by ... "

    --
    - Michael T. Babcock (Yes, I blog)
  121. Only a moron insists on the mayor by George_Ou · · Score: 1

    Just imagine if every IT employee pulled the "I'll only give the keys to the Mayor". Sure you can do that, but it comes with a 5-year prison term. This wasn't just the boss, but the boss' boss and his boss.

    1. Re:Only a moron insists on the mayor by Cro+Magnon · · Score: 1

      If the written policy said Mr Childs was supposed to give the keys only to the Mayor, that's what he was supposed to do. Otherwise he WOULD have been going against the official policy, and maybe risking jail for THAT.

      --
      Slow down, cowboy! It has been 4 hours since you last posted. You must wait another few hours.
  122. San Francisco is scummy by Anonymous Coward · · Score: 0

    San Francisco is scummy and should be boycotted. Every company and person should just leave and move to the other cities, maybe help clean up Oakland and let Frisco rot in their own stench.

  123. Re:He did 2 years just waiting for his court date by X0563511 · · Score: 1

    Thanks!

    --
    For large sets, this will be our guide even unto death, for the LORD will work for each type of data it is applied to...
  124. Re:The "taxpayers' money"... isn't. by AthanasiusKircher · · Score: 1

    Actually, you do.

    Every 4 years, at the ballot box.

    Umm... you do realize that elections are generally held every year in most municipalities? (And certainly every two years everywhere in the U.S.) The terms for a particular office might vary from one year to ten (so your chance to vote a particular person out of office might happen more or less frequently than 4 years), but elections generally happen every year -- sometimes more frequently when special circumstances arise.

    It's a sad fact in the U.S. that so many people only show up to vote in Presidential elections every 4 years. There are a lot of local offices that might have a lot more direct impact on your life or your community which are also a critical part of the government.

  125. Not everything can be in a policy by George_Ou · · Score: 1

    In fact, most things are not explicitly stated in policy and that's where common sense and the chain of command comes into play. So long as the superior is not asking the employee to do something clearly illegal or unethical, that employee has the choice to comply or face termination. They also have to release control of any company property.

    This is so that a person working for the San Francisco federal building can't demand to see President Obama to settle any workplace dispute. You can't say, I'm only going to give access to President Obama just because you feel that the entire chain of command is incompetent. You pull that in the military during war time and they shoot you for that. You are allowed to refuse immediate orders from direct superiors and go above their heads if you have a problem with the order, but you can't refuse the entire chain of command short of the President.

    1. Re:Not everything can be in a policy by Cro+Magnon · · Score: 1

      Not everything can, or should, be in a policy, but if it IS in a policy, it should be followed. Terry Childs didn't just decide everyone else was incompetent and go to the mayor. The policy SAID that only the mayor was authorized.

      Neither the federal worker nor the military grunt have anything in their written procedures about only giving access to the President. They WOULD be in the wrong if they tried such a stunt.

      --
      Slow down, cowboy! It has been 4 hours since you last posted. You must wait another few hours.
  126. Re:Before everybody gets their shorts all twisted by shitdrummer · · Score: 1

    Have you ever worked in a secure IT environment? Actually, have you ever worked in IT?

    Good IT security policy has rules and restrictions over who can have access to certain systems. I manage some systems that my boss isn't authorised to access. There are plenty of examples of this and it is completely normal. Basic IT security practice is to only have access to systems you need to access. An example of this is root access for some systems. In order to get root access you need to place a request with IT Security, they enable your root access for a limited time (perhaps an hour or so, depending on what you need the access for). IT Security keep a log of who gained root access when, why, and who authorised it (if additional authorisation is required).

    You need clear written rules for password/account hand-over. Places serious about IT security have a dedicated IT Security section. Typically someone there is authorised to receive passwords to pass out to replacements etc. For some systems you may be required to keep a copy of the account details in a sealed envelope within a dual access safe.

    If I gave my boss the password to a system he's not authorised to access I would be fired on the spot and taken to court for breaching security protocol. My contract specifically mentions that scenario.

    I'm not defending Childs, from what's come out from the trial he was being a dick. However if they didn't have any clear written rules for password hand-over then the higher-ups also should take some blame for this situation.

  127. Re:Before everybody gets their shorts all twisted by John+Saffran · · Score: 1

    Could I please have your password?

    hunter2

  128. Re:Before everybody gets their shorts all twisted by pushf+popf · · Score: 1

    Have you ever worked in a secure IT environment? Actually, have you ever worked in IT?

    Unless your first computer came as a pinout diagram for a 4-bit processor, a soldering iron and an idea, I've been doing it longer than you have. I've been in banking since punch-cards and magnetic tape, UUCP over dial-up, thorough mainframes, dumb terminals, terminal emulators, PCs and the beginning of the web, then moved into web and application support for the federal government before starting my own company to go after mid-range businesses.

    And as nostalgic as it makes me feel, my experience is irrelevant here. There was nobody in the entire city that he was willing to give the passwords to, which makes him a dick (and now a felon) not a conscientious employee.

    For what it's worth, I blame his boss and his boss's boss as much as our pet head-case. They needed to have access restoration policies and procedures in place for exactly this situation. What did they plan on doing if he was hit by a bus or dropped dead from Burger-King and Jolt Cola? One guy holds all the keys? That's just stupid.

  129. Re:Before everybody gets their shorts all twisted by Cramer · · Score: 1

    Claiming to forget the passwords simply wouldn't pass a litmus test. Right, you forgot the password(s) you've been using for weeks and were using just moments ago. Intentionally changing the passwords to something noone knows (not even to yourself) is evidence of willful intent -- and he'd be on the hook for a great deal more given the difficulty of regaining control without the passwords.

    I don't think it's fair to make him a felon over this. But he was certainly an enormous ass to begin with. As I've said before, the city isn't without blame here either. They allowed this maniac to build a network forwhich no one else had access. That is simply wrong. Always.

  130. Re:Before everybody gets their shorts all twisted by Cramer · · Score: 1

    He didn't go to jail for his beliefs. He's on his way to jail because he's a prima donna who refused to let anyone else touch his network. Did you miss the part about him getting a copyright on the network design?

  131. Re:Before everybody gets their shorts all twisted by Cramer · · Score: 1

    Really? I've seen no reports to support that. I wouldn't be surprised if they screwed some stuff in the interim when they didn't have the passwords -- and thus learned how he'd "rigged the network"... didn't save configs, and disabled password recovery where he did.

  132. Re:Before everybody gets their shorts all twisted by shitdrummer · · Score: 1

    Have you ever worked in a secure IT environment? Actually, have you ever worked in IT?

    Unless your first computer came as a pinout diagram for a 4-bit processor, a soldering iron and an idea, I've been doing it longer than you have.

    Nice. I wasn't trying to pay you out or anything, it's just that the /. crowd are very varied in their backgrounds.

    There was nobody in the entire city that he was willing to give the passwords to, which makes him a dick (and now a felon) not a conscientious employee.

    Agreed. However clear written policies may have helped the situation. Then again, there's no guarantee that Childs would have followed those policies.

    For what it's worth, I blame his boss and his boss's boss as much as our pet head-case. They needed to have access restoration policies and procedures in place for exactly this situation. What did they plan on doing if he was hit by a bus or dropped dead from Burger-King and Jolt Cola? One guy holds all the keys? That's just stupid.

    Definately agreed. I have "hit by a bus" action files for each position in my team, including myself. As I'm sure you know, it's just good risk management. Unfortunately we have had to implement one of those "hit by a bus" action files in the past.

  133. No it didn't by George_Ou · · Score: 1

    http://www.formortals.com/terry-childs-network-admin-convicted/

    No it didn't, there was no policy. What kind of an idiot writes a policy with mayor-only permissions? He pulled this Mayor-only excuse from his a$$.

    Read what the juror said. He said Childs had already given the COO access to the system before. He only had a problem giving access after he found out that he was getting reassigned. So he gave a bad username and password to his boss, the COO, and HR despite the fact that police had already been called to the meeting. Then emailed everyone laughing at them that they can't get in the next day. The cops tried to solve this as an employer/employee issue and then Childs withdrew $10K and left for Nevada the day before his arrest.

    This guy was a true piece of work. It's a classic case of an IT employee trying to lock out his employers and it gives us all a bad name. This business that it's his management's fault for giving him too much slack is no excuse. I was given a lot of freedom to act and design when I worked in a similar role and I saw that as a privilege that I earned.

  134. Re:The "taxpayers' money"... isn't. by kent_eh · · Score: 1

    Umm... you do realize that elections are generally held every year in most municipalities? (And certainly every two years everywhere in the U.S.) .....

    It's a sad fact in the U.S. that so many people only show up to vote in Presidential elections every 4 years. There are a lot of local offices that might have a lot more direct impact on your life or your community which are also a critical part of the government.

    It's an equally sad fact that voter turnout is declining rapidly here in Canada as well.

    I place a portion of the blame on the un-inspiring selection of candidates and their ideas.
    And of course the lazy-assed public deserves their share of the blame as well.
    Really, how hard is it to show up and mark an X once in a while

    And, yes, when I said every 4 years, I was referring to any specific office, not the entire government apparatus in all it's myriad permutations.

    --

    ---
    "I can't complain, but sometimes still do..." Joe Walsh
  135. How long should I hold my breath.. by Anonymous Coward · · Score: 0

    .waiting for the SF DA to be prosecuted for distributing 150 of those passwords to the public and actually causing a denial of service?