Slashdot Mirror


Terry Childs Case Puts All Admins In Danger

snydeq writes "Paul Venezia analyzes the four counts San Francisco has levied against Terry Childs, a case that curiously omits the charge of computer tampering, the very allegation that has kept Childs in jail for seven months and now appears too weak to present in court. Count 1 — 'disrupting or denying computer services' — is moot, according to Venezia, as the city's FiberWAN did not go down due to Childs' actions. Venezia writes, 'Childs' refusal to give up the passwords for several days in no way caused a disruption of the normal operation of the FiberWAN. In fact, it could be argued that his refusal actually prevented the disruption of normal network operation.' Counts 2 through 4 pertain to modems Childs had under his control, 'providing a means of accessing a computer, computer system, or computer network in violation of section 502,' according to case documents. As Venezia sees it, these counts too are spurious, as such devices are essential to the fulfillment of admin job requirements. 'If Childs is convicted on the modem charges, then just about every network administrator in the world could be charged with the same "crime,"' Venezia writes. All the authorities would have to do is 'point out that you have a modem or two, and suddenly you're wearing pinstripes of the jailhouse variety.'"

498 comments

  1. Too bad "being an asshole" is not a crime by winkydink · · Score: 4, Funny

    On second thought, I'd be in for a long stint.

    Never mind.

    --

    "I'd rather be a lightning rod than a seismometer." -Ken Kesey

    1. Re:Too bad "being an asshole" is not a crime by mabhatter654 · · Score: 5, Insightful

      that's the point really. His keeping the passwords is really no different than a VP keeping a laptop or company automobile. There are several civil steps that need to be gone through before "keeping" something you were previously entitled to have and protect becomes "criminal".
      Consider the case of loaning a car to your long term SO for many years, then the relationship goes south and you show up with the cops to take back the car she's had for several years. Yes, you can get it back, but the cops will tell you to get a judgment first and won't just let you take it. In the same way the new manager saw a "rogue" employee that was cut off, isolated, and anti-social and first tried to illegally fire him. When that didn't work, then he started harassing about the passwords and created a situation with the prosecutor to get the passwords or throw the guy in jail... a leap of about 6 other legal processes.

      Like has been said before.. modems and back doors in your office or home office (if expected to work from home/call in) are quite common for admins. VPN access to servers for when they crash is common. Those don't really figure into the "criminal" part because they didn't ASK if he had them and didn't ASK him to return them... packing his cardboard box on the way out the door is not formally "asking". As far as wiping the configs, that was paranoid overkill, but considering how often city office property gets stolen, wiping the config keeps thieves from getting the network settings to the whole thing which is more valuable than any one office of downtime due to power failure.

      "keys to the kingdom" passwords are quite common.. I'm the only person at my 1000 person company with ALL of a certain server's passwords plus some network ones. There's a small number of people I would release those to... if I was pre-accused of malicious intention before I even left I'd probably handle the transaction thru a lawyer.

      Like he predicted, when the city hired consultants (again not thru a legal means, just some random company to "fix it") and they started breaking stuff they didn't understand isn't his problem... Remember he was accused of "damages" even though the manager had no cause to make that ... they only poor performance he demonstrated was being disgruntled. Assuming he was doing damage and calling the cops is bordering on criminal filing a false report.

      The proper course of action would have been for the DA to sue him in small claims court for the password. Make a valid case and allow him his grievance before a judge, then honor the ruling. Then a judge would have thrown him in jail until he talked for contempt... there's no time limit on contempt, so no need to file other charges! Frankly they're not a good lawyer if they didn't think of the simplest legal thing first.

    2. Re:Too bad "being an asshole" is not a crime by Anonymous Coward · · Score: 0

      hear, hear

    3. Re:Too bad "being an asshole" is not a crime by Anonymous Coward · · Score: 3, Interesting

      Passwords are not property, the city should have gotten them before firing him. Once they let him go they had no reasonable expectation that he would give them any "knowledge" which is all that the passwords are.

    4. Re:Too bad "being an asshole" is not a crime by Anonymous Coward · · Score: 0

      Consider the case of loaning a car to your long term SO for many years, then the relationship goes south and you show up with the cops to take back the car she's had for several years. Yes, you can get it back, but the cops will tell you to get a judgment first and won't just let you take it.

      Ummm, no. You don't need the cops, it's your car. Take your key and go get it (or hire a repo man). There are no squatter's laws for cars. The car has a registered owner. Setting aside the registered owner requires a judgment, but until then, you win by default.

      The proper course of action would have been for the DA to sue him in small claims court for the password. Make a valid case and allow him his grievance before a judge, then honor the ruling.

      Here's a hint: district attorneys do not sue in small claims court - they see in grown up court. Further, small claims courts can only award monetary damages - they can't compel action.

    5. Re:Too bad "being an asshole" is not a crime by larry+bagina · · Score: 2, Interesting

      it's called a bailment. Look into it.

      --
      Do you even lift?

      These aren't the 'roids you're looking for.

    6. Re:Too bad "being an asshole" is not a crime by zappepcs · · Score: 4, Insightful

      Here is the deal as I see it. He's an admin with a bit of an attitude, yet he did his job well apparently. Everytime that I'm asked to do inane bs at work, I turn it into a paperwork exercise. That is to say that I am happy to paper the office of whichever vp wants reports and to be in charge. Soon, they ask me to 'just take care of it' as I see fit. Either you want a competent admin or you don't. Once you get one, you have to trust them and work with them, even if there are conflicts of personality. This is simply because you as a vp or cxo cannot replace that person. You are forced to work with them... deal with it.

      Positional authority is a powerful thing. If you as a cxo are afraid to give it to someone, get some certs... or perhaps learn to delegate and deal with that.

      The fact that this made the level it did in courts is indicative of the fact that management is not willing to give away any power to anyone. In much of this situation, they had no need for what they ask for, and should not have had it.

      In the cold light of day, if they gave him that much control, they got what they deserve. When you give someone that much power/authority, you must be nice to them. This is a situation that repeats itself across the globe without end. This particular one just happened to make the news because Terry has big balls.

      No matter what happens, this is a simple case of bad management. period.

    7. Re:Too bad "being an asshole" is not a crime by TubeSteak · · Score: 1

      The proper course of action would have been for the DA to sue him in small claims court for the password.

      Small Claims Court is for... small claims.
      Usually anything less than $5,000 in value.

      Are you going to argue that those passwords were worth less than $5,000?

      --
      [Fuck Beta]
      o0t!
    8. Re:Too bad "being an asshole" is not a crime by jamstar7 · · Score: 1

      Consider the case of loaning a car to your long term SO for many years, then the relationship goes south and you show up with the cops to take back the car she's had for several years. Yes, you can get it back, but the cops will tell you to get a judgment first and won't just let you take it.

      If the title & registration of the car is in your name, yeah, they will just let you go take it. It's proveably your property.

      --
      Understanding the scope of the problem is the first step on the path to true panic.
    9. Re:Too bad "being an asshole" is not a crime by poopdeville · · Score: 2, Funny

      Don't confuse us with facts.

      --
      After all, I am strangely colored.
    10. Re:Too bad "being an asshole" is not a crime by DarkOx · · Score: 1

      Yes, the probably are worth less than that. Its not like its all that hard to do password recovery on most infrastructure equipment. I also have a tough time accepting that localized interruptions are intolerable to a municipality during the hours most residents are asleep. It could have be reconciled without him for that much money.

      --
      Repeal the 17th Amendment TODAY! Also Please Read http://www.gnu.org/philosophy/right-to-read.html
    11. Re:Too bad "being an asshole" is not a crime by JWSmythe · · Score: 1

          I'm pretty sure they're holding a whole jail open for people like us. :)

          I'm an asshole to work for.. I'm an asshole to work with.. But, when I'm in charge, I run a tight ship, and everything gets done right and quickly.

          But, someone in senior management always has the master password list, in case I get hit by a bus or something.

          As for modems, who uses those any more. :) Apparently a few of his were DSL lines, so they were probably always up. Having redundant lines is a good thing, especially if part of his network supported essential services (EMS/911/etc)

      --
      Serious? Seriousness is well above my pay grade.
    12. Re:Too bad "being an asshole" is not a crime by JWSmythe · · Score: 4, Insightful

      > As far as wiping the configs, that was paranoid overkill, but considering how often city
      > office property gets stolen, wiping the config keeps thieves from getting the network
      > settings to the whole thing which is more valuable than any one office of downtime due
      > to power failure.

          When I left my last job as Sr. SysAdmin (they laid me off, for someone cheaper), they were absolutely sure I had left back doors into the network, and that I could sabotage everything. They couldn't find the backdoors (because they didn't exist), and ended up changing the OS on every server. In that beautiful move, they screwed up an awful lot of stuff. Ha!

          The funniest part was, some of the people who they kept on were thieves. They were stealing confidential data, and abusing the network for personal gains. It took two more years for them to figure that one out. All I can do now, since I have no involvement in that company, is sit back and laugh. :)

          The "keys to the kingdom" were on file with senior management though. Shit happens. I could get hit by a bus. I could get shot in a botched convenience story robbery. I could just decide not to ever come to work because I got a better offer. Why cripple their company?

      --
      Serious? Seriousness is well above my pay grade.
    13. Re:Too bad "being an asshole" is not a crime by ILuvRamen · · Score: 1

      well actually, it's good that they can't charge him with that or anything. If they could, they could send him to prison. But with no crime, they could just order him to work in the IT department at the prison. Now that's a sentence fit for an asshole lol.

      --
      Google's Super Secret Search Algorithm: SELECT @search_results FROM internet WHERE @search_results = 'good'
    14. Re:Too bad "being an asshole" is not a crime by TechForensics · · Score: 1

      The proper course of action would have been for the DA to sue him in small claims court for the password. Make a valid case and allow him his grievance before a judge, then honor the ruling. Then a judge would have thrown him in jail until he talked for contempt... there's no time limit on contempt, so no need to file other charges! Frankly they're not a good lawyer if they didn't think of the simplest legal thing first.

      You can't sue for other than monetary damages in Small Claims courts, at least in my state of Massachusetts. Other states could follow the same logic. However a TRO or preliminary injunction would be allowed in the upper-level courts of most states, and would be reasonably fast.

      --
      Those are my principles, and if you don't like them... well, I have others.
    15. Re:Too bad "being an asshole" is not a crime by TechForensics · · Score: 5, Informative

      Passwords are not property, the city should have gotten them before firing him. Once they let him go they had no reasonable expectation that he would give them any "knowledge" which is all that the passwords are.

      Sorry. I'm a lawyer and you're only partly right. Passwords may not be "property" but it can still be potentially harmful to withhold them. If a plaintiff could prove harm or even better, immediate irreparable injury, a court would say give 'em up or go to jail, go directly to jail, do not pass go, do not collect two hundred dollars.

      --
      Those are my principles, and if you don't like them... well, I have others.
    16. Re:Too bad "being an asshole" is not a crime by teknosapien · · Score: 1

      Your response brings up some interesting points but I feel it falls short of the real world in this instance. First off when you are in a position such as this person was, you own the keys to the kingdom. That being said I would never hand over the keys to the kingdom with out the consent of the king (mayor in this instance). As for comparing this to a company owned laptop/auto your not even close. The V.P. that keeps this stuff does not put the public in danger as would the CITY WIDE network (911 etc...) being broken. This is a much higher "for the common good" response to the current situation. Ultimately in retrospect, yes he should have gotten a lawyer, but when your in charge a system such as this and the the pool of clueless morons are the only pool you have to pull from (insert supervisor/manager in this instance) you don't take handing the keys of the kingdom over with out the blessing of the king. This is a new era with new rules and covenants and needs to be treated other than some one walking off with "material things"

      --
      no matter how good it is, it is human nature always wants to make things better
    17. Re:Too bad "being an asshole" is not a crime by Anonymous Coward · · Score: 5, Interesting

      Except from TFA -

      In this statement, the defense asserts that those present during the questioning were simply not qualified to hear the passwords. This impromptu meeting took place at the police station in the Hall of Justice, not in the DTIS offices, and Childs was brought there while in the building doing work on the FiberWAN. Those present included various members of the San Francisco Police Department, representatives from HR, and an unknown group of people on the other end of a speakerphone.

      If this is true, then his refusal to divulge the passwords becomes a lot less problematic from an ethics and security standpoint. You don't give up the master keys to a seemingly random group of people, including those that don't work in the department and some unknown others on the phone.

      To think of this another way, you might not have a problem giving up your Social Security number and debit card PIN number to a bank employee while you're in their office conducting business, but if there were a half-dozen other people in the office too, listening to the conversation, you would certainly think differently.

      Up until now, I'd been under the impression that Childs' refusal to divulge the passwords occurred during a private discussion or meeting with his boss -- not in a situation like this.

    18. Re:Too bad "being an asshole" is not a crime by Anonymous Coward · · Score: 0

      The proper course of action would have been for the DA to sue him in small claims court for the password. Make a valid case and allow him his grievance before a judge, then honor the ruling. Then a judge would have thrown him in jail until he talked for contempt... there's no time limit on contempt, so no need to file other charges! Frankly they're not a good lawyer if they didn't think of the simplest legal thing first.

      Actually, the lawyers did the right thing. Lawyers for either side aren't allowed in US small claims courts

    19. Re:Too bad "being an asshole" is not a crime by abelb · · Score: 1

      Not really, It's more like being given access to something like an office that remains on company property. The former employee then hides the keys preventing anyone else from gaining access to the office. Ownership of the office and the keys always remains with the company. Hiding the keys is a nuisance act which disrupts the company, so if the employee knowingly and deliberately disrupted the company they should be liable for any losses the company incurred as a result of those actions. I'm guessing?

    20. Re:Too bad "being an asshole" is not a crime by Score+Whore · · Score: 2, Insightful

      I think you completely fail to understand something very specific about server administration: You don't own the boxes. Your employer does. Your knowledge of passwords, etc. is so that you can do your job. In every company I've ever worked for I never have the authority to grant or revoke access to a system. I had the capability since I had root access, but that didn't grant me authority. It's not the job of an administrator to decide who does and doesn't have access any more than it is the job of a security guard to decide who has the privilege of entering the building. You are the implementor of the policy, not the creator of the policy.

      Childs is totally wrong here.

    21. Re:Too bad "being an asshole" is not a crime by Score+Whore · · Score: 1

      If the title & registration of the car is in your name, yeah, they will just let you go take it. It's proveably your property.

      Hell, even in a joint title you can just go take it.

    22. Re:Too bad "being an asshole" is not a crime by Anonymous Coward · · Score: 0

      You're right in that it would take a judge to issue a court order before the admin would be required to give the information.

      Until that time, the admin has no responsibility to hand over that information.

    23. Re:Too bad "being an asshole" is not a crime by sumdumass · · Score: 1

      Until that time, the admin has no responsibility to hand over that information.

      Sort of. If it is a case with injury or irreparable harm, each day the passwords were withheld could mean more money you ultimately have to compensate or repay.

      A normal person would see a responsibility to himself and his family to limit the potential damages applied to himself. It's not a responsibility to the place that just fired you, but there is one there, especially if you have a family and any judgment effects their financial well being.

    24. Re:Too bad "being an asshole" is not a crime by Fulcrum+of+Evil · · Score: 1

      A TRO from what, exactly? There's no evidence that Childs behaved maliciously.

      --
      "We returned the General to El Salvador, or maybe Guatemala, it's difficult to tell from 10,000 feet"
    25. Re:Too bad "being an asshole" is not a crime by InsertCleverUsername · · Score: 1, Interesting

      Sorry. I'm a lawyer and you're only partly right. Passwords may not be "property" but it can still be potentially harmful to withhold them. If a plaintiff could prove harm or even better, immediate irreparable injury, a court would say give 'em up or go to jail, go directly to jail, do not pass go, do not collect two hundred dollars.

      Sounds simple, but could the judge really punish someone if they just used the Reagan ("I don't remember.") defense? This "get out of jail free" card worked again and again for various Bush cronies. I've promptly forgotten entire books of material immediately after final exams myself.

      --
      Ask me about my sig!
    26. Re:Too bad "being an asshole" is not a crime by sumdumass · · Score: 4, Insightful

      That's not necessarily true. Just like the security guard, if the policy said no one enters the building without ID and a company Badge, then not letting anyone in without either of those is appropriate.

      The same can be said about a corporations bank account or credit card numbers. It's completely ethical and responsible to not disclose those things to anyone you cannot personally verify their right to access the information. Credibility is only a stones throw from socially engineering the information away from someone. The police in the room could have been attempting to get access to install illegal taps on a public official or anything other then what they were doing. Childs was probably within his rights to demand that he be contacted by the proper people in a manner that he could verify their identity. The mayor was most likely his point of contact and his superior which is why he refused to do anything until he could give it to them.

      Here is a thought experiment. Suppose I walked into your building in a uniform of some sort and asked you for the passwords to your servers and access to the server rooms. I gave you ID that matched the name on my uniform and claim I was hired by the company to perform a security audit of the system.

      Do you
      A- give me access and the passwords
      B- tell me to get lost
      C- contact your superiors and verify that I am legit then give me the passwords and access

      C- is the right answer (even though A happens all to often). But Childs wasn't in a position to contact his superiors or the mayor could have been his superior and instead stated that he would give the information to the mayor. When the mayor came around, he surrendered everything without hassle.

    27. Re:Too bad "being an asshole" is not a crime by sumdumass · · Score: 3, Interesting

      I have servers that I set up 10 years ago for small businesses and I'm probably the only one with the passwords assuming they are still running (486 and Pentium II machines running either Netware 3.something or some dos app). I get calls every once in a while from companies I haven't done business with in over 5 years asking me if I could remember the pass words to the servers.

      I generally type everything out and put it in a sealed envelope within a binder with all the server specs, applications, network diagrams and so on. The problem is that someone has either decided they didn't need it and tossed it or whoever replaced me did something with it and it can't be found anymore. Most of the times, someone changed them and they aren't the same anymore. I think one situation occurred where a company raided an office because a manager was embezzling and the cops never returned the binder. Management leaves or whatever. Sometimes they need it only for data recovery or some sort of migration to a newer system and sometimes they are still using the crap but need to change something.

      Filing the "keys to the kingdom" with the management doesn't always work well so check that they are still there and still current every once in a while.

    28. Re:Too bad "being an asshole" is not a crime by nomadic · · Score: 1

      Not a requirement for TROs.

    29. Re:Too bad "being an asshole" is not a crime by Fulcrum+of+Evil · · Score: 1

      There has to be some sort of imminent threat, though. Why would you bother with a TRO from someone who you fired and isn't trying to do anything to you? I may as well get a TRO against my college roommate.

      --
      "We returned the General to El Salvador, or maybe Guatemala, it's difficult to tell from 10,000 feet"
    30. Re:Too bad "being an asshole" is not a crime by Runaway1956 · · Score: 1

      Yeah, pretty much on target. But, they weren't concerned about simple, fast, or cheap. Someone was gunning to make a name for themselves, and when the media got hold of it, they just dug in, and grew more determined to punish the accused.

      --
      "Windows is like the faint smell of piss in a subway: it's there, and there's nothing you can do about it." - Charlie Br
    31. Re:Too bad "being an asshole" is not a crime by dontmakemethink · · Score: 1

      If a plaintiff could prove harm or even better, immediate irreparable injury, a court would say give 'em up or go to jail

      Doesn't firing someone without cause also result in immediate irreparable damages, specifically to their wallet and reputation?

      Also begs the question, why didn't Childs just say he was so pissed off from getting fired that he erased the passwords then got astronomically piss-drunk for a week straight and forgot them?

      --

      War as we knew it was obsolete
      Nothing could beat complete denial
      - Emily Haines
    32. Re:Too bad "being an asshole" is not a crime by khallow · · Score: 1

      You are the implementor of the policy, not the creator of the policy.

      Two things. 1) in your example, you have the authority to implement the policy. 2) Mr. Childs may have legitimately had the authority to set policy too.

    33. Re:Too bad "being an asshole" is not a crime by More_Cowbell · · Score: 1

      OK, perhaps, but replace car with house in his analogy, and the reverse is true. Yours or not, it is not possible (generally) to legally immediately remove someone from a residence they have been in for some time (provided that person has not broken any other laws).
      Keep in mind, I'm not saying you can't get some local sheriff or whatever to do this, it's just not within their legal right (again, generally).

      --
      Experience teaches only the teachable. -AH
    34. Re:Too bad "being an asshole" is not a crime by N1AK · · Score: 3, Interesting

      Sorry. I'm a lawyer and you're only partly right. Passwords may not be "property" but it can still be potentially harmful to withhold them.

      If a salesman is fired, is he breaking the law if he refuses to work for free advising his old company about their customers (Who else do they buy from, What are their priorities, etc)? If a engineer leaves, does he have to produce detailed schematics for anything the company owns?

      If the admin followed the rules he was employed under (assuming the company has a password policy) then I can't see why a password should be treated better than the job related knowledge required in most careers.

    35. Re:Too bad "being an asshole" is not a crime by LingNoi · · Score: 1

      I'm not arguing with that, however what about a situation where the plaintiff claims to have forgotten the password?

    36. Re:Too bad "being an asshole" is not a crime by Anonymous Coward · · Score: 0

      Sorry. I'm a lawyer and you're only partly right. Passwords may not be "property" but it can still be potentially harmful to withhold them. If a plaintiff could prove harm or even better, immediate irreparable injury, a court would say give 'em up or go to jail, go directly to jail, do not pass go, do not collect two hundred dollars.

      How about time elapsed? I'm not sure if that could have been an issue in this case. In my situation, I was in charge of a number of servers, all of which ran Windows except for two, which ran different flavors of unix -- one HP-UX and one Solaris. The bright sons of bitches had fired all their unix admins some years earlier. These two boxes had been acquired just before the last admin was tossed out, because a few customers wanted the product we sold, but only if it would run on a unix box. Since I knew enough Linux to do basic unix admin functions, the work fell to me. Later, they absorbed a company with some unix talent, but had me retain responsibility for our area's servers.

      I always kept my supervisor, as well as his manager and the director up to date on the system passwords, by email, so they'd have a traceable record. I sent the same information on the day I left -- to all three.

      Two months later, I get a call. They've had a power drop which exhausted the UPSes (dumb move anyway) and can't (for whatever reason) get these two servers back up and need the passwords. I emailed all three of them with the passwords, which I fortunately still remembered. I've forgotten them by now, but haven't heard from them in years (not even to say thanks, the bastards), so I guess it worked.

      However, I decided then that, if I ever head from them again, I was going to tell them I'd forgotten and would have to come in to search some other systems (which I knew they had to preserve) for some clues. My consulting rate would, at that time, be $500/hour -- door to door -- eight hours minimum -- no guarantee of success.

      "Sorry, judge, I really can't remember passwords which I haven't had occasion to use for over half a year. No, my emails containing any system information have disappeared, just like the copies they received from me."

    37. Re:Too bad "being an asshole" is not a crime by Jane_Dozey · · Score: 3, Insightful

      More like an employee is charged with looking after the office and keeping it secure so they hide the keys. They then refuse to give up the keys to a person who has no need or reason to enter the office. Employee states that they will give up the keys if told to do so by an appropriate person in authority. Employee then gets arrested.

      --
      Silly rabbit
    38. Re:Too bad "being an asshole" is not a crime by wisty · · Score: 2, Insightful

      Also, the city had a responsibility to not fuck things up. If somebody steals your car keys and you smash your windscreen (rather than hiring a locksmith to jimmy your lock), you can't sue for damages you caused yourself.

      (I'm not a lawyer, that's not advice.)

    39. Re:Too bad "being an asshole" is not a crime by ObsessiveMathsFreak · · Score: 0, Troll

      I'm a lawyer and you're only partly right. Passwords may not be "property" but it can still be potentially harmful to withhold them.

      Potentially harmful? And you're a lawyer. Gods help our legal system.

      --
      May the Maths Be with you!
    40. Re:Too bad "being an asshole" is not a crime by z_gringo · · Score: 1

      Frankly they're not a good lawyer if they didn't think of the simplest legal thing first.

      I thought the first rule of being a lawyer was to select the path that generates the most billable hours.

      --
      -- -- Warning. Do not stare directly at the sun.
    41. Re:Too bad "being an asshole" is not a crime by xouumalperxe · · Score: 0

      Doesn't firing someone without cause also result in immediate irreparable damages, specifically to their wallet and reputation?

      Yes,which is why decent legislations state that you must give employees a certain amount of forewarning, and there are certain remedies, e.g. severance pay.

    42. Re:Too bad "being an asshole" is not a crime by julesh · · Score: 4, Interesting

      Sorry. I'm a lawyer and you're only partly right. Passwords may not be "property" but it can still be potentially harmful to withhold them. If a plaintiff could prove harm or even better, immediate irreparable injury, a court would say give 'em up or go to jail, go directly to jail, do not pass go, do not collect two hundred dollars.

      Why should I be under any obligation to do something for an organisation that is no longer my employer to prevent harm from coming to them? Sure, if it's my job I have to do what they ask me to, and if my negligence causes them harm then I could be in trouble. But if I'm no longer under contract, why should I do anything? Why, in fact, can I not say, "Oh, those passwords? Well, when I left my job with you they were no longer useful to me so I destroyed my copies of them, as security best practices dictate I should do with any confidential information I no longer require?"

    43. Re:Too bad "being an asshole" is not a crime by z80kid · · Score: 1
      > Yours or not, it is not possible (generally) to legally immediately remove someone from a residence they have been in for some time (provided that person has not broken any other laws).

      I had a "roommate" who was sponging off me for about a year. When asked to leave, the roommate refused. She claimed that I needed to go through formal eviction proceedings. As much as I hated to do so, I called the police.

      The police stated that in order for this person to have rights she needed to either have her name on the lease, or some proof that she had paid utilities or other expenses related to the residence. Since she never paid a dime towards anything, the police removed her.

    44. Re:Too bad "being an asshole" is not a crime by neomunk · · Score: 2, Insightful

      Your rant is only accurate if policy is to give the golden keys that can shut the city's network down to any manager that asks for it. I HIGHLY doubt that such is the case.

      Remember, this guy didn't just build a computer for a person and then not hand the passwords over, he was in charge of a public-owned network. I would be aghast if the city had network policies that gave root access to anyone who thought that they needed it, and especially those who were so cocky about it as to ask in a room full of people who SHOULDN'T have it in any case.

      In short, manager != owner. Without a copy of SF network policy here, your declaration of him being totally wrong is pure baseless speculation.

    45. Re:Too bad "being an asshole" is not a crime by Anonymous Coward · · Score: 0

      The "keys to the kingdom" were on file with senior management

      As they should be. Our role is to do a job, protect our network and systems and occassionally, tell a CXO "NO, that's a bad idea."

      Our best protection as admins is our reputation and signed paperwork stating policies.

      Do no harm should apply to us too, not just doctors.

    46. Re:Too bad "being an asshole" is not a crime by ta+bu+shi+da+yu · · Score: 1

      In a way, telling them their own passwords was a dumb move really. If someone had gained unauthorized access, they might have come back at you!

      --
      XML is like violence. If it doesn't solve the problem, use more.
    47. Re:Too bad "being an asshole" is not a crime by drinkypoo · · Score: 1

      Consider the case of loaning a car to your long term SO for many years, then the relationship goes south and you show up with the cops to take back the car she's had for several years. Yes, you can get it back, but the cops will tell you to get a judgment first and won't just let you take it.

      Depends on the cops. Besides, if the car is registered in your name, that's the only thing that REALLY matters. If you report it stolen instead of just calling them then they'll probably take it back. This might make you an asshole, depending on what she did to deserve it. In the absence of common law which causes you to be lumped as spouses, she has no particular right to your property no matter how long she's had it.

      If some woman cheated on me, for example, I sure wouldn't be letting her drive off in one of my cars after I found out. I'd be taking the air out of the tires to make it so myself, though.

      "keys to the kingdom" passwords are quite common.. I'm the only person at my 1000 person company with ALL of a certain server's passwords plus some network ones. There's a small number of people I would release those to... if I was pre-accused of malicious intention before I even left I'd probably handle the transaction thru a lawyer.

      Do you really have the right to do that? I think the answer is no. On the other hand, you have no obligation to give them to anyone not above you in the chain of command. (or above your former position, in this hypothetical situation.)

      Childs should most certainly have gotten a lawyer before the duck hit the fan, however. It is a terrible flaw of our system that you cannot have justice without one, but it is still (for the most part) true.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    48. Re:Too bad "being an asshole" is not a crime by TheVelvetFlamebait · · Score: 2, Insightful

      I can't see why a password should be treated better than the job related knowledge required in most careers.

      Passwords are different because:

      a) they are small and trivial to communicate (unlike your examples), and
      b) they are (for all practical purposes) essential for the running and maintenance of an important and expensive part of many companies

      When a sales company fires a salesman, they can try to recoup the salesman's loyal customers, or they can bear the losses. There will be plenty of others.

      When an engineer leaves, if he's worth keeping, he'll have kept some reasonable schematics of his work. If he decides to steal or vandalise them before he goes, well, then he's liable.

      I can't see why this is so difficult to grasp.

      --
      You know, there is a difference between trolling and pointing out the flaws in your reasoning. Just saying.
    49. Re:Too bad "being an asshole" is not a crime by mcgrew · · Score: 1

      Consider the case of loaning a car to your long term SO for many years, then the relationship goes south and you show up with the cops to take back the car she's had for several years. Yes, you can get it back, but the cops will tell you to get a judgment first and won't just let you take it.

      It's worse than that. A couple of years ago my car was stolen. As chronicled in the not very SFW journal, I'd let a woman stay at my apartment for a week when she'd become homeless.

      The cops said since she was living there (never mind the fact that she wasn't living with me, just crashing there for a few days) they couldn't charge her with Grand Thieft Auto, as permission was assumed.

      It very often sucks to be me.

    50. Re:Too bad "being an asshole" is not a crime by delcielo · · Score: 1

      Except that it's not up to Terry to decide who is qualified to hear them, and who is not. They're not his. The network belongs to the City. The routers belong to the City. The City determines who is qualified to hear them. Now, that might not square with you from a technological standpoint; but that doesn't matter.

      --
      Hot Damn! It's the Soggy Bottom Boys!
    51. Re:Too bad "being an asshole" is not a crime by TheVelvetFlamebait · · Score: 2, Insightful

      What's wrong with that? Are you worried because a lawyer issues advice based on the potential for harm (and he therefore, in your opinion, is stupid)? Or are you worried because he seems to think there are situations when withholding passwords might not be harmful (and he therefore, in your opinion, is stupid)? I can't decide from your post, and both options seem absurd.

      --
      You know, there is a difference between trolling and pointing out the flaws in your reasoning. Just saying.
    52. Re:Too bad "being an asshole" is not a crime by poot_rootbeer · · Score: 1

      To think of this another way, you might not have a problem giving up your Social Security number and debit card PIN number to a bank employee while you're in their office conducting business, but if there were a half-dozen other people in the office too, listening to the conversation, you would certainly think differently.

      Your SSN and PIN are data that authenticate YOUR identity, and if compromised could cause harm to come to YOU.

      How would the ex-administrator have been harmed, personally, if some untrusted third party learned the passwords to a system for which he no longer had a bit of responsibility, and in fact was barred from?

    53. Re:Too bad "being an asshole" is not a crime by Anonymous Coward · · Score: 0

      I would argue that on top of that though, it is the administrators responsibility to make sure that the person attempting to have the change made is authorized to do so. I won't speculate on specifics as I didn't RTFA but when I implement policy, that policy needs to follow procedure. If you don't have authority within my hierarchy, and you come to me to do something, I will not do it for you until proper procedure is followed (meaning the appropriate people authorize the request). Now if the President of my company says comply with so-and-so I comply without question.

    54. Re:Too bad "being an asshole" is not a crime by cgenman · · Score: 1

      I think you completely fail to understand something very specific about server administration: You don't own the boxes. Your employer does... It's not the job of an administrator to decide who does and doesn't have access any more than it is the job of a security guard to decide who has the privilege of entering the building. You are the implementor of the policy, not the creator of the policy.

      I'll bet dollars to doughnuts that SF policy about city network-wide passwords limits their sharing to select groups of people. Terry Childs, apparently, refused to share passwords with people who didn't meet that policy requirement.

      It's a quetion of where legitimate authority comes from. If authority comes from "above", then whenever anyone above him in the org chart asks him for anything he should jump immediately. However, if authority comes from following the installed procedures and policies of the system, you may find yourself in a location where you have to deny your own boss certain things he asks for because it wouldn't fit proper security procedures. As Terry Childs was working for a public entity, and in a security capacity, it seems like procedural authority should take precedence here.

    55. Re:Too bad "being an asshole" is not a crime by poot_rootbeer · · Score: 1

      what about a situation where the plaintiff [sic] claims to have forgotten the password?

      Well, the courts would have to evaluate the veracity of such a claim. If the password was an essential part of the guy's job duties, and he had to make use of it on a daily basis during his employment there, it's pretty clear that if he says "I forgot" immediately afterward, he's lying. And that could result in perjury charges.

    56. Re:Too bad "being an asshole" is not a crime by Jester998 · · Score: 2, Insightful

      No one in the room was in Childs' chain of command. His boss wasn't there, nor was his boss' boss, etc. It was a group of random city employees (city police, HR) and random, unknown people on the other end of a phone.

      What authority did anyone there have to order him to divulge passwords?

      If someone from HR or Finance, even if they're a VP or C*O, came to me and said "Hand over all the network passwords now.", I'd tell them to fuck off too until someone to whom I report said otherwise.

    57. Re:Too bad "being an asshole" is not a crime by poot_rootbeer · · Score: 1

      Its not like its all that hard to do password recovery on most infrastructure equipment.

      If I remember the story correctly, the city brought in consultants from Cisco to do password recovery analysis on the systems after Childs refused to relinquish the passwords.

      Wanna ballpark the amount of the consultancy bill that the city was ultimately presented with?

    58. Re:Too bad "being an asshole" is not a crime by Jester998 · · Score: 2, Insightful

      It's not about PERSONAL harm. It's about professional ethics and legal implications. If you were fired from a company, and subsequently went and posted every password you knew on a forum or email list, you'd be sued or charged in a heartbeat.

      This is no different in the least -- even if he was already barred from accessing the system, it was still a random group of people whose authority over him and/or the systems was nonexistent, or questionable at best. If he HAD divulged the passwords in those circumstances, he should have been charged, not the other way around.

    59. Re:Too bad "being an asshole" is not a crime by poot_rootbeer · · Score: 1

      Yours or not, it is not possible (generally) to legally immediately remove someone from a residence they have been in for some time (provided that person has not broken any other laws).

      So Childs was the tenant, and the network was his primary residence? I guess since he had been paid to maintain it, that would make him a live-in superintendent?

      I think this analogy is starting to veer off-topic. There's a reason why usually stick with car-based analogies, everybody.

    60. Re:Too bad "being an asshole" is not a crime by Anonymous Coward · · Score: 0

      If Childs really faces problems because he did not reveal passwords, I see only two reasonable conclusions: 1) Refuse to hold secret information or 2) forget the secret information once your job no longer requires you to have it or when you're under duress and about to lose your job anyway. "I don't recall" has worked for people who have committed actual crimes.

    61. Re:Too bad "being an asshole" is not a crime by jenn_13 · · Score: 1

      I think a better analogy would be requiring a fired employee to hand over his keys to company property...

    62. Re:Too bad "being an asshole" is not a crime by kextyn · · Score: 4, Insightful

      The things you mention (customers, schematics, etc) are a lot different than a password. If the company has any clue what the're doing then that small, trivial password becomes completely useless immediately after he is fired. I can't remember if it was the root passwords he refused to give up or his own account's password. If it was his own there is no reason for the company to need them. If it was the root passwords why was he the only one with them? One person should not hold all the root passwords for the company's equipment and I'm pretty sure he had a boss that should have made arrangements in case Terry suddenly died.

    63. Re:Too bad "being an asshole" is not a crime by furby076 · · Score: 1

      that's the point really. His keeping the passwords is really no different than a VP keeping a laptop or company automobile. There are several civil steps that need to be gone through before "keeping" something you were previously entitled to have and protect becomes "criminal". Consider the case of loaning a car to your long term SO for many years, then the relationship goes south and you show up with the cops to take back the car she's had for several years. Yes, you can get it back, but the cops will tell you to get a judgment first and won't just let you take it

      Fault & bad comparison.
      Faulty: If you loan your SO your car and the day you break up you come with the cops they will give you the car - that day - but they will not arrest her (unless you have evidence of her trying to sell your car illegally, or proof positive of her saying "it's mine and you can never have it back" which is stealing). If you have legal citings that say otherwise please post it, otherwise ownership gives you instant access (with some exception, like someone renting living space from you and giving someone reasonable time to vacate space like a storage unit).

      Comparison: It's a bad comparison all-together. The SO could easily argue that giving up the car would be detrimental (she couldn't get to work, or go to pick her daughter up from school, or go to the doctor, or go to the car rental place) and was asking for a 2-3 day continued usage period where it would not cause the same harm to the owner. She would not win, since letting someone borrow your vehicle doesn't entitle them to use it when you want it back, but the cops most likely won't arrest her either (unless they want to be total douchebags or she was kicking/screaming). But what makes this a bad comparison - once the network admin leaves the company he has absolutely NO need to access the systems. He was fired - his responsibility to maintain the network has been removed. It will not hurt him to not have access to the computers. He has no legal right to access the information nor any reason to. If the network admin says "but i have some personal files on there" that is too bad. Most companies (those who think of it) have terms stating that any data on their servers belong to them and the laws support this. Now the company could be nice and say "when we get a new network admin we will have him burn your information to CD" but they are under no legal/moral obligation to do so.

      I am not sure about the terms of this specific case but if one of these two scenarios happened then two different outcomes would occur:

      1) If someone else in the company (e.g. the CEO) had copies of the PW and the network admin changed the PW's at the last second to screw with the company he could be held liable for tampering with private property in an attempt to cause malicious harm. Information which he no longer has a legal right to access (he was fired) cannot be changed even if he thinks it is to help the company "your honor i was just protecting them". It is no longer his responsibility nor his call to make.

      2) If he did not change the password after he found out he was going to be fired (this includes finding out by accident) then he is not requried to write the passwords down for them. They could ask him, and he could refuse. They could offer him money. If a company fires you they have to take the good and the bad. The good is they no longer have you for the reasons they wanted to fire you. The bad is they lose any information you have in your head and that is not information you have to divulge (unless you have a contract stating you need to spend your time writing something up). They should have thought of the information loss before firing you. When I was fired from a job years ago I was not asked for information from my boss, but there were a LOT of technical needs that was not documented (I tended to document every process I ran but never had a chance to do all of them). My employer would have no legal right to demand me to document those. He could offer to pay me but I could also tell him to go to hell.

      --

      I do not support "The Man". I also do not support your irrational stupidity
    64. Re:Too bad "being an asshole" is not a crime by John+Jamieson · · Score: 1

      You raise a good point.

      Whether we agree with him or not, Childs was obviously a person of principle, not the jerk some would like to portray him as.

    65. Re:Too bad "being an asshole" is not a crime by furby076 · · Score: 2, Interesting

      Why should I be under any obligation to do something for an organisation that is no longer my employer to prevent harm from coming to them? Sure, if it's my job I have to do what they ask me to, and if my negligence causes them harm then I could be in trouble. But if I'm no longer under contract, why should I do anything? Why, in fact, can I not say, "Oh, those passwords? Well, when I left my job with you they were no longer useful to me so I destroyed my copies of them, as security best practices dictate I should do with any confidential information I no longer require?"

      You are absolutely correct - once they fire you then you are no longer responsible to provide them with any services (unless you signed a contract stating otherwise). Even if it causes their system to fail it is no longer your responsibility. They can offer you money...or they should have thought of that BEFORE firing you (e.g. sending you an e-mail two days in advance stating "please document all systems you have access to, how you access them, including login credentials and all back-door access and get this to us before XYZ date"). If they did that and you neglected to respond, while still employed, then they could have legal recourse. Otherwise....QQ PvP World

      --

      I do not support "The Man". I also do not support your irrational stupidity
    66. Re:Too bad "being an asshole" is not a crime by furby076 · · Score: 1

      To think of this another way, you might not have a problem giving up your Social Security number and debit card PIN number to a bank employee while you're in their office conducting business, but if there were a half-dozen other people in the office too, listening to the conversation, you would certainly think differently.

      Uhm I worked in retail banking (with 3 different banks) for five years (from teller to head teller to manager) and currently work for a major credit card company in software development...PLUS I worked in network security...you never give your pin number to ANYBODY. Very few people, actually depending on how it was coded nobody, have access to passwords. If it was coded to allow someone to see it most likely it is a DBA - but a good programmer/systems designer would request the databse containing the PIN numbers can never been seen by anything except the software. Now given that there are ways to get around that security if you have access to the source code - but you get the point. Whoever made the PIN example for the bank was wrong. SS is different as that is used to look up your info and it is something any bank employee (minus support staff like secretaries, janitorial staff, etc) have access to.

      --

      I do not support "The Man". I also do not support your irrational stupidity
    67. Re:Too bad "being an asshole" is not a crime by Anonymous Coward · · Score: 0

      "... Your knowledge of passwords, etc. is so that you can do your job"

      And the first rule is:

      Don't tell anybody your password, ever!

      It's company policy!

    68. Re:Too bad "being an asshole" is not a crime by N1AK · · Score: 1

      I think a better analogy would be requiring a fired employee to hand over his keys to company property...

      How this that a remotely good analogy? The keys are company property, if he doesn't return them he is committing theft. The copy of a password stored within his brain is NOT property, and is exactly the same as customer details or architectural details. If he no longer works for the company then he has no legal obligation to consult for them.

    69. Re:Too bad "being an asshole" is not a crime by N1AK · · Score: 2, Insightful

      Passwords are different because: a) they are small and trivial to communicate (unlike your examples), and

      Firstly, the effort required to communicate the data isn't important. Either you work for the company or you don't, if you don't then you are free to choose to do what you wish. I could request that you put "N1AK is awesome" in your signature, is it a crime for you not to perform this trivial act? Would it be different if I used to employ you?

      Secondly, there is plenty of things a Salesperson could tell his ex-employer very easily and quickly. How long would it take to say "Oh, I heard that our competitor is releasing a product which improves x by % but at a cost to y". That information could arguably be far more important to the long term success of the company than a single password, why should it be treated differently?

      b) they are (for all practical purposes) essential for the running and maintenance of an important and expensive part of many companies

      His boss should of ensured that the critical information wasn't lost with him. The company was at fault for not ensuring that the passwords would be available if something happened to Mr Childs, that is not his responsibility. Compliance with Sarbanes-Oxley is vital for businesses in America, if an accountant was fired before he had properly processed some information relevant to SO it could have far more damaging consequences than a typical admin password.


      The point here is not whether Terry's actions were damaging to the company or not, regardless of how damaging they might be. He was obviously being as difficult as he could. The issue is whether someone can be punished for choosing not to do work for someone who no longer employs them?

    70. Re:Too bad "being an asshole" is not a crime by WCguru42 · · Score: 1

      I'm NASA (not a sys admin) but I would equate passwords to keys as opposed to clever networking tricks being like schematics. I don't know the story but regardless of if you're fired for the wrong reasons if you're a reputable person then you'll maintain your civility and return what must be returned and never deal with the company again.

      --
      "Educate the mind but never at the expense of the soul."~Blessed Basil Moreau
    71. Re:Too bad "being an asshole" is not a crime by Peter+La+Casse · · Score: 1

      That's exactly right. It is up to the senior network administrator to decide who is qualified to hear the passwords.

    72. Re:Too bad "being an asshole" is not a crime by cayenne8 · · Score: 1
      "Yes,which is why decent legislations state that you must give employees a certain amount of forewarning, and there are certain remedies, e.g. severance pay."

      Wow...dunno where you live where they have these laws, but, every state I've lived in are 'at will' states. Basically aside from reasons illegal to fire/discriminate (color, sex, etc) you can be fired at any time for no reason whatsoever....effective immediately.

      Actually, I thought MOST states in the US were 'at will' states.

      --
      Light travels faster than sound. This is why some people appear bright until you hear them speak.........
    73. Re:Too bad "being an asshole" is not a crime by nabsltd · · Score: 1

      The major diffference is that any company that does not have some sort of escrow for important passwords (root, etc.) really deserves what they get if somebody just doesn't bother to tell the the password to their critical system.

      By having some sort of policy in effect for how changes to these important passwords are handled, you can't actually stop a rogue admin from changing them, but you will have very strong legal reasons for firing, and possibly for a compensation lawsuit.

      Last, in pretty much every password-protected system I know, if you have physical access, you will be able to change the main admin password in some way. This probably should be a requirement for all systems that any business/government purchases.

    74. Re:Too bad "being an asshole" is not a crime by Kelbear · · Score: 1

      I don't know what standard IT practices say about high-level password rotation, but I have to change my computer's passwords every 30 days. I remember the new one most of the time but not all of the time. I'll assume the IT dept's would require as much security if not more considering how much more access is granted through them.

      It's entirely plausible to forget a password that's strong, random, and rotated every 30 days. I'd be more suprised if he remembered the password than if he forgot it. I'd figure him for a liar if he claims not to have written it down somewhere, rather than if he claims he forgot it.

    75. Re:Too bad "being an asshole" is not a crime by BitZtream · · Score: 2, Insightful

      I'm not really sure what dimension you live in, but in the one your are posting in, your are wrong.

      If your SO has a car thats titled in your name and you break up and demand it back by calling it stolen, the police will make them turn it over immediately. There will be no waiting or courts involved as there is no need to be. They may not arrest your SO, they may not charge them, but you will certainly get your car back pretty much as soon as you prove its yours. It doesn't even matter if you are married, if the title isn't in your name, its not your car, and you have to turn it over immediately. If the car is titled in both names, THEN you end up in a situation you describe, but thats cause you both legally own the car. Your analogy doesn't, in any way, apply here, +2 points for using a car analogy. -several billion for being stupid.

      Its nice that you live in a fantasy world which thinks that the guy has any excuse what so ever to not turn over those passwords to his boss, but your world is just that. His employement is a priveledge, not a right, and so is his holding of those passwords. Once his boss demanded them, he should have turned them over. The instant he didn't, for ANY reason, he should have been terminated. What he got was EXACTLY what he should have got. He's an arrogant twit who took advantage of his situation to make other peoples jobs a royal pain in the ass. Now I'm sure somewhere in your head you can justify that as being OK, but in my mind, thats about the most perfect reason to fire someone as you can come up with.

      You, with your passwords should be fired for being an absolutely shitty admin. There is no excuse for you haveing the only passwords to anything other than your own personal account. If that account is an admin account not only should you be fired but you should be tatooed in such a way that no other company makes the mistake of hiring your incompetent ass.

      Those passwords should be stored securely within the company by someone trustworthy OTHER than yourself for several reasons. The first of which is in case you get hit by a bus and die. The second is that you are a shitty admin and need to be replaced for pulling the bullshit you're pulling. I could go on, but the point is made I think. Your ignorance is practically criminal, you're using your power as a control point in case something happens that you don't like. I'd fire you on the spot if I were your boss.

      The proper course of action would have been to wait 6 months for a court slot to open up, only to go to small claims court and be told that you're in the wrong court because the potential dollar value involved for damage is massive? Or to be told that you're supposed to go to a criminal court because the guy has unauthorized access to computers which is most certainly a criminal offense. The guy broke the law in several ways, this isn't a civil matter, it wasn't the instant he refused to turn over said passwords.

      Its funny that you talk about them not being a good lawyer, you really have no clue what the hell you are talking about.

      --
      Persistent Volume manager for Kubernetes - https://github.com/dwimsey/openshift-pvmanager
    76. Re:Too bad "being an asshole" is not a crime by BitZtream · · Score: 1

      By having passwords that no one else has, I.E. not following the policy of storing a copy of said passwords in a secure location accessable by other authorized personal, you have effectively stolen data from the company upon termination.

      Your negligence is what created the situation when you didn't either follow proceedure for keeping a backup copy of the passwords or by not implementing said procedure on your own, take your pick which one I don't care, just stop thinking you're going to go around the situation by being cute.

      --
      Persistent Volume manager for Kubernetes - https://github.com/dwimsey/openshift-pvmanager
    77. Re:Too bad "being an asshole" is not a crime by jedidiah · · Score: 1

      The keys to the kingdom should not be handed over to "senior management".

      They need to be handed over to a gatekeeper that can keep
      them safe until they are actually needed. The idea is to
      NOT make it easy for any schmuck to abuse the system. I
      would imagine Sarbanes Oxley all by itself requires this
      much of IT organizations these days.

      Yes, give them root level access so they can commence with
      the Enron style paper shredding or any number of other
      dubious activities.

      If you can't gaurantee the integrity of the system
      and you are going to be held responsible for that
      same integrity then you need to leave.

      They aren't letting you do your job.

      --
      A Pirate and a Puritan look the same on a balance sheet.
    78. Re:Too bad "being an asshole" is not a crime by N1AK · · Score: 1

      I'm NASA (not a sys admin) but I would equate passwords to keys as opposed to clever networking tricks being like schematics. I don't know the story but regardless of if you're fired for the wrong reasons if you're a reputable person then you'll maintain your civility and return what must be returned and never deal with the company again.

      How exactly do you 'return' something that is in your memory?

      I see myself as a reputable person, and disagree entirely with the idea that I must act in the best interests of an ex-employer regardless of whatever they have done in the past.

      Passwords aren't physical property, treating someones knowledge (of any form) as though it remains company property after they leave is not the solution.

    79. Re:Too bad "being an asshole" is not a crime by Vancorps · · Score: 1

      My guess is that you've never been in this position as you are completely incorrect.

      Parent is right, the cops will tell you to get judgement first. A friend of mine went through this problem during her divorce since most things had been in her name since she was paying for most everything. That was exactly what the cops told her when she asked the question because she was afraid for her life to go to the house and get it without police being present.

    80. Re:Too bad "being an asshole" is not a crime by WCguru42 · · Score: 1

      treating someones knowledge (of any form) as though it remains company property after they leave is not the solution.

      This word, "knowledge", I don't think it means what you think it means.

      Seriously, your password is not the same sort of knowledge that design technique is. Just because you store something in your mind does not immediately make it your own and only. I'll try to present an analog (though admittedly lacking a bit). Say your employer gave you a passcode to enter into the building, but the funny thing about your passcode is that no one can get into the building without you first entering your passcode. If you've memorized it and then get fired, you still need to give that code back to your employer so that they can use their property. No matter how stupid it was of them not to have some form of tracking their passwords, you still need to give them the code back.

      Also, I'm not saying that you need to act in the best interest of a company irregardless of what they've done in the past, but you need to maintain your own standards of right and wrong. It is not difficult for one to return passwords to a company, it doesn't harm you, and in all honesty, it's the right thing to do.

      --
      "Educate the mind but never at the expense of the soul."~Blessed Basil Moreau
    81. Re:Too bad "being an asshole" is not a crime by Anonymous Coward · · Score: 0

      uh, there is a much easier analogy, it involves keys! Are you required to give back the keys your employer gave you? Or, to pre-answer some of you...if you were given the ability to change the locks, seen as creating new passwords that only you have, do you have to return the keys which the company does not have a copy of?

      Imagine you hire me to change the locks on your house. I'm pretty sure you would want me to give you those keys when I'm done, or when you fire me, as I install the last one whilst pissing on your floor.

    82. Re:Too bad "being an asshole" is not a crime by More_Cowbell · · Score: 1

      The police stated that in order for this person to have rights she needed to either have her name on the lease, or some proof that she had paid utilities or other expenses related to the residence. Since she never paid a dime towards anything, the police removed her.

      Dude, seriously... no offense, I know this is /., and reading TFA is out of the question, but how about reading the comment you are replying to? ;)

      Keep in mind, I'm not saying you can't get some local sheriff or whatever to do this, it's just not within their legal right (again, generally).

      Local cops are NOT lawyers, judges, constitutional scholars, etc... They do have guns and handcuffs, so I generally agree that doing what they say is a good idea, but that does not make all their actions legal.

      Turning someone out onto the street on the spot without an eviction notice or some other court type order is GENERALLY ILLEGAL (in all the states I've lived in anyway). Tenants have more rights than most of them know.

      Cheers.

      --
      Experience teaches only the teachable. -AH
    83. Re:Too bad "being an asshole" is not a crime by Maxo-Texas · · Score: 1

      They still try to find cause to avoid unemployment taxes.

      It's amazing how stupid they can be tho... even in "at will" states, you can't say "You are fired, we want a younger person".

      --
      She was like chocolate when she drank... semi-sweet at first and then increasingly bitter.
    84. Re:Too bad "being an asshole" is not a crime by Maxo-Texas · · Score: 1

      as admin, he should have some kind of masterkey/password. he was the source of all security.

      His issue (besides being pissed) was that he felt the new people were going to screw things up and then he would be held legally responsible.

      A little paranoia (perhaps justified the way things turned out).

      As far as the root article... "providing modems" is a crime is just stupid. That's part of your job as an admin.

      --
      She was like chocolate when she drank... semi-sweet at first and then increasingly bitter.
    85. Re:Too bad "being an asshole" is not a crime by SignalFreq · · Score: 1

      Sorry. I'm a lawyer and you're only partly right. Passwords may not be "property" but it can still be potentially harmful to withhold them. If a plaintiff could prove harm or even better, immediate irreparable injury, a court would say give 'em up or go to jail, go directly to jail, do not pass go, do not collect two hundred dollars.

      Exactly. A court would rule and demand they be released. The proper course of action is filing a civil complaint and then letting the courts sort it out. Refusing to give out passwords is not a criminal act.

      Mr. Childs agreed to release the passwords to the Mayor. He did not threaten to withhold them forever or completely refuse to give them out. He merely refused to give them out to people he did not trust. The city filed a very weak CRIMINAL complaint, based solely on three modems found in Mr. Childs office to put him in jail. The modems have been shown to be 100% legitimate, so the only remaining thing is his refusal to release passwords to people he did not trust (which is a civil complaint). He should be released from jail and counter sue. The DA should have never brought charges based solely on three modems.

    86. Re:Too bad "being an asshole" is not a crime by arekusu_ou · · Score: 1

      I know you were being funny, but he wasn't being an ass.

      He gave a chunk of his life to the city, the network was his baby, his sweat and blood.

      They viciously fired him, and then expected him to cooperate afterwards. He walked away and said they can't what's in his head.

      Even without giving my sweat and blood, if they treated me like that, I wouldn't be cooperative either. The stuff they asked for are or should be documented. And he sounds more meticulous than I am.

      He should countersuit for defamation.

    87. Re:Too bad "being an asshole" is not a crime by nomadic · · Score: 1

      Well TRO is probably not the mechanism you'd use, but you could probably get some sort of injunctive relief (of which a TRO is just one form). So a positive injunction to turn over the passwords probably would be pretty easy to get, considering the city needs them and giving them wouldn't have really taken much effort on Childs' part.

    88. Re:Too bad "being an asshole" is not a crime by Wintermute__ · · Score: 1

      Any CCNA or CCIE worth his salt could have reset those passwords, given physical access to the hardware. If they hired the most expensive consultants they could find, that's their lookout. $5000 could conceivably cover it. If I hire Norm Abrams for my home improvement project, I know he'll do an excellent job. But I'd better be willing to pay him for it.

    89. Re:Too bad "being an asshole" is not a crime by Fulcrum+of+Evil · · Score: 1

      Childs was always willing to give over the passwords, just not to someone who posed a threat to the network (remember - fuck up the network and E911 can go down). He stated as such and handed them over to the Mayor months ago. Meanwhile, without the passwords, the network just ran itself. Regardless, you don't fire someone before getting the passwords taken care of.

      --
      "We returned the General to El Salvador, or maybe Guatemala, it's difficult to tell from 10,000 feet"
    90. Re:Too bad "being an asshole" is not a crime by Wintermute__ · · Score: 1

      Yes and no. I'm not familiar with every line of SOx, but I'll bet you five bucks it is actually those in "senior management" who are legally responsible for protecting those records, not the sysadmin.

      It is your responsibility to follow procedure, and that should include password escrow of some sort, ultimate responsibility for which falls to "senior management".

      If they abuse it and destroy those systems, that is exactly what the penalties in the legislation are for. Not "throw the sysadmin in jail because he obeyed his boss".

         

    91. Re:Too bad "being an asshole" is not a crime by n0tWorthy · · Score: 1

      That's why I store the hundred or so passwords that I maintain in PasswordSafe. There are so many secure phrases that must be documented for the PKI cards, the ecommerce systems and whatnot that I certainly don't remember most of them. I would spend a long time in jail if I were "required" to remember them because I just wouldn't be able to do it.

      --
      "Be kind, for everyone you meet is facing a great battle." - Philo of Alexandria -
    92. Re:Too bad "being an asshole" is not a crime by wastedlife · · Score: 1

      That would be age discrimination, which the state may have a law against. However, with "at will" states, they just need to say you were fired for another reason. It basically creates a loophole for discrimination, because you just have to hide it.

      --
      Said, "It's just like dice but it's got more sides And it tells me who lives and who dies"
    93. Re:Too bad "being an asshole" is not a crime by Maxo-Texas · · Score: 1

      which makes it amazing when they try to make up a reason instead of just saying "your fired... because we want to" and then the reason violates the law. /slap forehead at their stupidity.

      --
      She was like chocolate when she drank... semi-sweet at first and then increasingly bitter.
    94. Re:Too bad "being an asshole" is not a crime by anotherslashfan · · Score: 1

      You're getting close to a point that I have been trying to make. Given they have "physical access" to these devices and systems, if their IT dept is worth any salt, they would have been able to recover/crack or reset the passwords they were demanding. (Yes, even the root accounts.) They didn't have to "demand" passwords from him...or throw him in jail for it. Maybe he's setting "them" up? This is an ego trip for the city. But it may backfire and expose their lack of competency in the IT dept.

    95. Re:Too bad "being an asshole" is not a crime by Arterion · · Score: 1

      How can they prove you have something memorized? How can they charge you criminally if you don't give up something you had memorized?

      Now, if the passwords were printed out, written on paper, and stored in a safe, and Child's had taken that paper with him and refused to return it, absolutely he's violating the law. But telling him he has to remember a bunch of passwords or go to jail is both cruel and inhumane punishment. I am even wondering if he couldn't use his fifth amendment rights of simply not witnessing against himself.

      All else aside, The first burden of proof would be to establish that Child's actually had the passwords memorized. I have no idea how the state could accomplish that.

      But really, the remaining charges are for him having modems, not about passwords.

      --
      "That which does not kill us makes us stranger." -Trevor Goodchild
    96. Re:Too bad "being an asshole" is not a crime by Arterion · · Score: 1

      It would be the same as him memorizing the shape of a physical key. Sure, he could possibly recreate that key and access company property, but that would be a crime in itself.

      However it wouldn't be right for the courts to force him to make them a copy of the key from memory for the company.

      --
      "That which does not kill us makes us stranger." -Trevor Goodchild
    97. Re:Too bad "being an asshole" is not a crime by Cramer · · Score: 1

      They aren't "physical property", but they certainly are "intelectual property". He refused to hand over any passwords while employed there. That would be one, if not the, reason to fire him. Once no longer employed there, he is most indeedly required to hand over the passwords just like any other physical property. No matter how much of an ass he was while employed there and afterwards, I still think the city is taking this a little far in keeping him jailed for months.

    98. Re:Too bad "being an asshole" is not a crime by Cramer · · Score: 1

      In this case... I suspect the judge would literally laugh you under the jail. Right; he forget the password he set and has been typing in daily for weeks or months -- and was using shortly before being fired. And the "well, I just changed the passwords an hour ago" excuse also falls flat.

    99. Re:Too bad "being an asshole" is not a crime by Cederic · · Score: 1

      If he gave up the passwords to after he's been fired then he's guilty of conspiracy to misuse computing services (in British terms; I'm fairly sure the US has equivalent laws).

      He has a cast iron defense that he was fucked either way: Share the passwords with people he knew he'd signed a contract not to tell the passwords to (i.e. people unauthorised to have access) or get shafted as he is being for refusing.

      I hope to hell the city get fucked senseless both financially and (regarding specific employees) in terms of custodial sentences for doing this to him.

    100. Re:Too bad "being an asshole" is not a crime by Anonymous Coward · · Score: 0

      Point taken but the employee was told to do so by an 'appropriate person in authority' (his boss), and my understanding is that he refused.

    101. Re:Too bad "being an asshole" is not a crime by TheVelvetFlamebait · · Score: 1

      Firstly, the effort required to communicate the data isn't important. Either you work for the company or you don't, if you don't then you are free to choose to do what you wish. I could request that you put "N1AK is awesome" in your signature, is it a crime for you not to perform this trivial act? Would it be different if I used to employ you?

      Just to remind you, we are talking about passwords here, not trivial requests. Withholding the password can case serious damage to the company. The company owns the equipment, the former admin does not. The former admin owes the company its passwords, not so much in virtue of the company being his former employer, but in virtue of the fact that he is a person withholding their own vital information from them.

      I might add that the trivial effort required to comply with such a request is important, because it means that the cost to the admin is far, far outweighed by the benefit to the company.

      That information could arguably be far more important to the long term success of the company than a single password, why should it be treated differently?

      Because the password is a secret that can be discovered from exactly one source. If a sales company wanted to find out what a former employee already found out, they can have another sales man repeat the work he already did. A password might only have a single source.

      His boss should of ensured that the critical information wasn't lost with him.

      Consider, for a moment, what you are advocating. No admin would have the obligation to share a password once terminated. What happens if an admin decides not to share a password at all? The employer can't fire him, because he knows that if he did that, not only would he not have his passwords, but he'd have no-one running his system. It gives admins far too much power to make themselves indispensable through unethical and harmful practices.

      The point here is not whether Terry's actions were damaging to the company or not, regardless of how damaging they might be. He was obviously being as difficult as he could. The issue is whether someone can be punished for choosing not to do work for someone who no longer employs them?

      I don't think the courts see it that way. They don't see this as a chance to set a precedent forcing people to work for their employers unpaid. That would be ridiculous, and the courts know this. They see it as a chance to minimise damages to a companies as a result of an admin abusing his power.

      --
      You know, there is a difference between trolling and pointing out the flaws in your reasoning. Just saying.
    102. Re:Too bad "being an asshole" is not a crime by mabhatter654 · · Score: 1

      worse they had basically accused him of sabotaging the system when they asked for the passwords.. whoever he gave them to would break stuff and blame him anyway... damned if he did, damned if he didn't.

    103. Re:Too bad "being an asshole" is not a crime by mabhatter654 · · Score: 1

      So when you tell the last security guard he can only give keys to the owner... then the OWNER doesn't know anything about firing him you have the same problem. You fired the guard, he's not legally obligated to be on the premises, so he can't unlock the gate! But he can't give the key to YOU because YOU are not the owner he took the keys from.

    104. Re:Too bad "being an asshole" is not a crime by Score+Whore · · Score: 1

      I'm curious as to what your disagreement with me was. Your thought experiment is exactly what I said.

    105. Re:Too bad "being an asshole" is not a crime by mabhatter654 · · Score: 1

      they got access to the hardware.. but not access to the network because the routers were set to reset to defaults on power failure. Great plan for preventing people from stealing stuff and trying to get in from home. Bad for consultants because they would have had to reprogram the whole thing!

    106. Re:Too bad "being an asshole" is not a crime by Golddess · · Score: 1

      I mostly just skimmed the discussion, but I wanted to add an additional distinction that seemed to be lacking.

      In your examples, I would expect it to be pretty common SOP to already have such things written down and documented somewhere prior to the employment termination. Passwords typically aren't due to security concerns.

      That being said, as someone else pointed out, Childs probably shouldn't have been the only person with the passwords anyway, since what if he suddenly died one day?

      --
      "I'm not sure I like the fugnutish tone you used in your post!" -RogL (608926)-
    107. Re:Too bad "being an asshole" is not a crime by mabhatter654 · · Score: 1

      Giving them a sealed envelope with recovery instructions and passwords is not the same as just making them have everything personally. The point is that this envelope has the "keys to the kingdom" and they are now in control. You have presented them with the information and it is now THEIR responsibility as owners to protect that information. YOUR work is finished.

      That is very much in the spirit of SOX.

    108. Re:Too bad "being an asshole" is not a crime by mabhatter654 · · Score: 1

      it's more like the 20-year janitor that always "just shows up" and never takes vacations. Eventually everybody loses their keys, plant and office managers change, but this guy is always there so nobody gets the keys and makes sure their copies really work. Then janitor has a heart attack and now you're harassing his kids for the keys to your business.

    109. Re:Too bad "being an asshole" is not a crime by Score+Whore · · Score: 1

      First I made no rant.

      Second I never said "give the golden keys .... to any manager", I said that the role of server admin doesn't set policy re. access.

      Third, this wasn't just a request to pass the password out to all and sundry on a whim, it was a emergency situation and only one person knew the password. I don't know about where you work, but I've worked for a large bank and for the military and at no point was I the only holder of the passwords. The fact that Childs was the only person who knew the passwords brings serious questions as to his just doing the job with proper regards to operational correctness.

    110. Re:Too bad "being an asshole" is not a crime by Score+Whore · · Score: 1

      Terry Childs, apparently, refused to share passwords with people who didn't meet that policy requirement.

      Terry Childs apparently refused to share the passwords with anyone. Can you explain to me how it's possible that an IT department of more than one person would allow it to come about that only one person knows the passwords necessary to maintain the network?

      Ever hear of a single point of failure?

    111. Re:Too bad "being an asshole" is not a crime by cayenne8 · · Score: 1
      "It's amazing how stupid they can be tho... even in "at will" states, you can't say "You are fired, we want a younger person"."

      No...they can just say "you're fired"....with no reason given.

      --
      Light travels faster than sound. This is why some people appear bright until you hear them speak.........
    112. Re:Too bad "being an asshole" is not a crime by TechForensics · · Score: 1

      Sounds simple, but could the judge really punish someone if they just used the Reagan ("I don't remember.") defense? This "get out of jail free" card worked again and again for various Bush cronies. I've promptly forgotten entire books of material immediately after final exams myself.

      It kind of depends on whether the judge BELIEVES the "I don't remember" defense. If he doesn't, watch out, you're getting hung out to dry until you "remember". If he thinks it's plausible you might have forgotten, he (or she) would try something less severe, tailored to his (or her) impression of the case and the Admin's state of mind / truthfulness. OTOH if (s)he believes it's not likely you remember, you're off the hook. Yes, everyone gets to file affidavits saying how likely it is a Sysadmin would forget such passwords. His medical records could go into evidence (if he's an epileptic, for instance, it is well known that a grand mal seizure can wipe out some significant memory). (To say nothing of processor speed.)

      --
      Those are my principles, and if you don't like them... well, I have others.
    113. Re:Too bad "being an asshole" is not a crime by TechForensics · · Score: 1

      A TRO is just a preliminary preliminary injunction, which can order the party to do or not do something. Usually a TRO is secured ex parte on representation things are getting so desperate so fast there's no time to notify the opposition and have them present. (Typically there is a very speedy hearing to see if the TRO will stand.) In this case if his boss swore on oath the server room would be attacked by Trolls without the passwords (thanks to Scott Adams) and everything laid to waste, a TRO might enter. (Chances are though the admin would be in court for that hearing well before any time of compliance stipulated in a TRO, however.) Since that would irrevocably disclose the passwords, however, the judge might tell the Admin to type in the passwords himself, privately, if the judge felt the Admin had a point about their being abused for other purposes after the immediate emergency were over.

      --
      Those are my principles, and if you don't like them... well, I have others.
    114. Re:Too bad "being an asshole" is not a crime by raphae · · Score: 1

      "The password is rot13 encrypted on the bottom of the beige stapler on my desk."

      "There is no beige stapler on their desk."

      "There was. Then someone must have stolen it."

      Seriously, how could they possibly justify locking someone up for something like that?

      I can think of a million variants like this, all of which could be equally plausible and basically impossible to prove.

      Then the case becomes not something about criminally witholding information. It seems like the worst thing that could be charged would be some type of professional, criminal negligence which would have cost the company money. But in that case the territory becomes so murky and the lines of responsibility between the company, management, and employees so crisscrossed that it seems like it would be very difficult to successfully litigate against someone.

    115. Re:Too bad "being an asshole" is not a crime by nomadic · · Score: 1

      Wasn't really his decision to make. And especially foolish considering the Mayor is just going to turn around and give it to Childs' former supervisors. Though maybe I just have less sympathy for Childs because I've met the arrogant sysadmin with a messianic complex type before, and I just find them annoying.

    116. Re:Too bad "being an asshole" is not a crime by raphae · · Score: 1

      As a professional Systems Administrator who prides themself on their professional conduct, I seriously hope that you are *not* a sysadmin. Such a stubborn, immature, bratty attitude is absolutely unprofessional. If you are incapable of divorcing egotistic impulses from professional conduct, you absolutely should not ever be working near critical systems of any kind.

      Any good professional in the world should have some reasonable anticipation (and possibly first-hand experience) of the possibility of dealing with employers who are unfair, wrong, or just stupid. That never, in any way, justifies a retaliatory act of damage against that employer. If you think that it does, you should not be working with critical systems.

    117. Re:Too bad "being an asshole" is not a crime by Stephen+Samuel · · Score: 1
      Nice analogy, but -- in this case, childs didn't steal or vandalize anything. The system ran just fine without his passwords.

      The fact that the city hired some consultants that broke the system while trying to fix it isn't his problem.

      --
      Free Software: Like love, it grows best when given away.
    118. Re:Too bad "being an asshole" is not a crime by Fulcrum+of+Evil · · Score: 1

      Really? How is it his boss' decision? If you fire me then demand anything beyond a place to send the final paycheck, I'm acting out of kindness, and if my first encounter with you is idiot consultants demanding things without expectation and you undermining my work, good luck getting those passwords. I'd have done the same thing - if the mayor then gives boy wonder the keys to the kingdom, so be it. At least it's documented then.

      --
      "We returned the General to El Salvador, or maybe Guatemala, it's difficult to tell from 10,000 feet"
    119. Re:Too bad "being an asshole" is not a crime by chefren · · Score: 1

      How exactly do you 'return' something that is in your memory?

      You tell them what they are and then they change them.

    120. Re:Too bad "being an asshole" is not a crime by stanjam · · Score: 1

      You have a point, but one I doubt the company understands. It is relatively easy to get the systems back as long as you have physical access, but I doubt that the company understands this outside from a few IT people (if that). The bigger concern for me would be the back doors, making sure they were all found and shut down. THAT I would sue over!

      --
      Open Source: Eroding the Digital Divide
    121. Re:Too bad "being an asshole" is not a crime by TechForensics · · Score: 1

      I like your username.

      To answer your question, voluntary drunkenness causing a large harm would be treated severely, like drunk driving resulting in an accident. Also, see my other post, the judge may not BELIEVE such a story, and then, as they say, you are for it.

      --
      Those are my principles, and if you don't like them... well, I have others.
    122. Re:Too bad "being an asshole" is not a crime by Anonymous Coward · · Score: 0

      I worked for an ISP and was let go. My workstation was encrypted by truecrypt (the boot drive). I was testing it for a few months on my workstation first to see if it would work properly before having it deployed on company laptops. I typically never had to use the password for it since the computer was left on all the time and the only password I had to use was my windows domain password. The password for the truecrypt boot was different. All files that I had were kept in a central server for backup purposes which the admin/exec staff had complete access to.

      After I was let go, they came to my house wanting the password to log in to the workstation, even though there were no files kept on the workstation. They told me that if I didn't give up the password, they could have called the police and charged me kind of criminal act of destruction of computer something or other. I gave the password up because it didn't really matter.

      The issue I've always wondered is, what if that password that I rarely ever used was just written down on a post-it note and it got thrown away and therefor I no longer knew the password?

      When someone left the company, typically their laptop or workstation was re-installed with windows from the ground up so why didn't they just do that with my workstation instead of wining about a password prompt.

      All my work files that may have been of any value to the company were kept on a central server that they had complete access to and not stored on my workstation. Again, why the big deal?

      Was I really obligated to give them the password at this point? After a work relationship (in Arizona) is terminated, as far as I know there is no longer any obligation to each other in any way.

    123. Re:Too bad "being an asshole" is not a crime by ibsteve2u · · Score: 1

      You are forced to work with them... deal with it.

      And that runs afoul of the need for absolute control that afflicts many a "vp or cxo". They must know all and control all; they know the data is of critical importance to the corporation - and they also know no one is more competent than they are in any area. You resist, gently, with explanations of the technical complexity and inherent risks, but that serves only to irritate their pride, and they insist that you shall give them the passwords.

      So you try to educate them enough to ensure that they are not excessively dangerous, and give them the passwords...at which point they figure out that they can't understand it, and that irritates their pride. Again. So they offshore the systems and your job, content in the knowledge that they do not have to see that irritating person who knew more than they did ever again.

      So happy, in fact, that they don't even think about how they now have absolutely no control over how their data is used or modified...let alone over the passwords used to access it.

      --
      Orwell: "In a Time of Universal Deceit, telling the Truth is a Revolutionary Act"
    124. Re:Too bad "being an asshole" is not a crime by pnutjam · · Score: 1

      The whole thing is a moot point. No important passwords should be stored only in one person's head. What if he had been killed in a car accident, or locked up for some non-work related criminal offense.
      I use an encrypted password database, Keepass. I keep all important passwords in there and the Director of IT has the password to that. If I were the Director of IT I would make sure that master password was in a company safe or safe deposit box that the CEO or CFO have access to, but I'm not so I don't worry about that part.

  2. When modems are illegal... by MrEricSir · · Score: 5, Funny

    Thankfully I'm stealing my neighbor's wifi, so I don't have to worry about being caught with a modem.

    --
    There's no -1 for "I don't get it."
    1. Re:When modems are illegal... by Anonymous Coward · · Score: 2, Insightful

      Whoops! Looks like you forgot that you have to modulate and demodulate signals to connect to a wireless network!

    2. Re:When modems are illegal... by Anonymous Coward · · Score: 0

      care to share the password of your neighbors wife?

    3. Re:When modems are illegal... by Crudely_Indecent · · Score: 1

      Stealing WiFi and other types of service is pretty easy for a wireless ISP network administrator.

      It's fun to memorize mac addresses, wep keys and passwords if I don't already have a backdoor (or combination, or key). I'm then able to connect virtually anywhere in several counties either directly to a tower, through a customers cpe, or dial-up if necessary. DSL subscribers would be fair game as well as most NIDs are found outside the residence.

      There would be no way to keep me from getting onto that network with what I know.

      If it is found true that by withholding passwords he prevented outage then he might get out of this. I can imagine withholding passwords if I didn't trust my replacement.

      --


      "Lame" - Galaxar
    4. Re:When modems are illegal... by ozphx · · Score: 1

      Whoops! Looks like you forgot that his neighbours modem is not somewhere where he is likely to be caught with it.

      Unless hes fucking his neighbour's wife, in which case I retract my statement.

      --
      3laws: No freebies, no backsies, GTFO.
    5. Re:When modems are illegal... by Anonymous Coward · · Score: 0

      I provide my WiFi unencrypted and free so others *can* use it. You may not in fact be steeling anything.

    6. Re:When modems are illegal... by kid_oliva · · Score: 1

      Thankfully I'm stealing my neighbor's wifi, so I don't have to worry about being caught with a modem.

      It is only stealing if it is unencrypted. Otherwise it is free in my book.

      --
      I eat Karma for breakfast, lunch, and dinner. That's why I don't have any.
  3. the admin's response by commodoresloat · · Score: 4, Insightful

    'If Childs is convicted on the modem charges, then just about every network administrator in the world could be charged with the same "crime,"' Venezia writes. All the authorities would have to do is 'point out that you have a modem or two, and suddenly you're wearing pinstripes of the jailhouse variety.'"

    It still beats having to wear a suit to work.

    1. Re:the admin's response by mc1138 · · Score: 1

      I'd wear shackles over a tie any day!

    2. Re:the admin's response by Anonymous Coward · · Score: 1, Funny

      That's what she said!

    3. Re:the admin's response by Anonymous Coward · · Score: 0

      How about "wearing" a broom handle that your cellmate thinks is really cute as a handle?

    4. Re:the admin's response by mdielmann · · Score: 1

      It still beats having to wear a suit to work.

      This always amuses me. There are comfortable suits out there (although you may have to find a style that doesn't include a tie). So what's the big deal about what clothes are required? Especially from a group that is willing to wear authentic medieval (read, uncomfortable) gear for kicks, refusing to wear decent-quality clothing for money leaves me baffled. As far as I'm concerned, it's just another costume that's required to play a game. It also happens that that game has some nice financial rewards involved.
      Besides, who really believes that your clothing changes who you REALLY are?

      --
      Sure I'm paranoid, but am I paranoid enough?
    5. Re:the admin's response by Cederic · · Score: 1

      Besides, who really believes that your clothing changes who you REALLY are?

      Women.
      Senior Managers.
      People in public service.
      Many other people.

      (Note that responses are not mutually exclusive)

    6. Re:the admin's response by mdielmann · · Score: 1

      It changes how people perceive you, which is different. Trust me, putting an asshole in an Armani suit isn't going to make him a nicer person. Which gets back to the point. If some fool is going to pay you twice as much for wearing a costume while you work, why not? And if your boss recognizes that far too many of their clients are going to have these same, possibly faulty, preconceptions, then what's wrong with them demanding that you wear a costume to improve the company's bottom line? And as far as those women who like an asshole in a nice suit, the assholes can have them.

      --
      Sure I'm paranoid, but am I paranoid enough?
  4. Ouch. by Anonymous Coward · · Score: 0

    .....(refusal to give up the passwords) actually prevented the disruption of normal network operation. >>

    The truth hurts.

    1. Re:Ouch. by mabhatter654 · · Score: 1

      no, it didn't. The manager hired contractors to try to prove Childs was causing "harm". They couldn't crack the password, and when they unplugged the routers the settings were wiped and needed to be uploaded. They didn't have those either. The manager CHOOSE to break 2-3 offices and make the problem worse. That wouldn't hold up on Judge Judy, let alone actual court.

    2. Re:Ouch. by LittleRunningGag · · Score: 1

      Is it common for router startup configs to be left blank like that?

    3. Re:Ouch. by doctorcisco · · Score: 5, Informative

      No. Wrong. Incorrect.

      He used the Cisco IOS command "no service password-recovery." Normally, with physical access to the router and a reboot, you can gain access to the router configuration file. "no service password-recovery" turns that function off.

      HOWEVER, it DOES NOT WIPE THE CONFIGURATION FILE. It simply makes it impossible to gain console access to the router unless you swap out the flash memory. When you reboot the router, the magic key combination doesn't work, the router boots up, and all is as it was before.

      Sigh.

      doctorcisco

    4. Re:Ouch. by Anonymous Coward · · Score: 0

      Is it common for assholes to use tt tags?

    5. Re:Ouch. by almondo · · Score: 2, Insightful

      I expect he will be able to find more than one Cisco certified security professional who will point out that devices with limited or no physical security can and should be configured with "no service password-recovery". Proper administrative policies would have had version control archiving router and switch configurations, thereby completely alleviating the impact of disabling break key recognition.

      I don't call it secure until at the very least, I can't break in without extraordinary measures.

    6. Re:Ouch. by Achromatic1978 · · Score: 1

      Proper administrative policies would have had version control archiving router and switch configurations, thereby completely alleviating the impact of disabling break key recognition.

      Would you mean, perhaps, administrative policies that from all of this, it would appear to have been Childs job to implement? Not entirely sure why he wouldn't have also locked that down and denied people access to it the same way as he did in general, but alrighty then.

    7. Re:Ouch. by Anonymous Coward · · Score: 0

      its not common, but its not unheard of to leave a "fail-secure" startup configuration that is marginally functional (if at all).

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

      Actually, he was following DoD protocol of not saving configs to flash, they were just in volitile memory, so the config on the routers couldn't be taken off-site and compromised, or they'd lose the config. That's why they were crapping their pants... He did have a secure network, you have to hand it to him.
      The funniest part of it to me is the fact that he gave the password to the loser mayor, and they couldn't figure out why they weren't working... He'd restricted access to his IP/MAC for admin access control. Beautiful.

    9. Re:Ouch. by Anonymous Coward · · Score: 0

      It does wipe the config if you want to recover the password and therefore regain access. (http://www.cisco.com/en/US/products/hw/routers/ps274/products_configuration_example09186a00801d8113.shtml)

      However, in this case I believe the wiping of the config part came from him not copying the running config to start-up. (At least that is what one of the original articles stated.) That is just plain dumb, especially if you use "no service password-recovery"...

    10. Re:Ouch. by archen · · Score: 1

      As someone else stated this guy has balls. Having the config in memory and not writing to flash? Yeah that confirms it. No way I'd have the guts to run a router like that. You take power and power backup systems for granted, but there is always a chance at failure. I'd think that the last thing you would want after an extended power failure and all the problems that come with it is to have all your routers defaulted.

    11. Re:Ouch. by almondo · · Score: 1

      "Would you mean, perhaps, administrative policies that from all of this, it would appear to have been Childs job to implement?"

      Yes, I think that is a fair conclusion. If it wasn't his responsibility to account for these archival processes then it sure should have been somebody's (like maybe his manager who locked himself out?). In any case, the problem was a lot bigger than his refusal to disclose IMHO.

  5. This seems hard to swallow by Crashspeeder · · Score: 2, Interesting

    First, this story sounds very one-sided and has quite a bit of sensationalism. Ok, a lot. I'm sure they can charge him with something to the effect of unauthorized access to a government computer system. Nobody's going to be pointing out modems as tools of a crime. That's like saying having a car means you're a bankrobber because bankrobbers use getaway cars.

    1. Re:This seems hard to swallow by Dun+Malg · · Score: 2, Interesting

      I'm sure they can charge him with something to the effect of unauthorized access to a government computer system.

      You're sure? How can they charge him with unauthorized access when his only action was to not give them passwords? The passwords were set when he was still employed, and had the authority to do so.

      --
      If a job's not worth doing, it's not worth doing right.
    2. Re:This seems hard to swallow by davester666 · · Score: 1

      Well, they can charge him with anything, but I from what I remember reading about the story, he didn't access the gov't computers after he was fired.

      I believe the main complaint against him was that he had all the knowledge over how the overall system worked, had the main administrator passwords, and wouldn't turn them over to others. I'm iffy on whether he was claimed to have disabled others from accessing the system, and whether he did that before or after he was fired.

      --
      Sleep your way to a whiter smile...date a dentist!
    3. Re:This seems hard to swallow by mysidia · · Score: 1

      The problem is they probably can't prove he gained unauthorized access, because most likely he didn't, he just had the means to.

      And the access would have been unauthorized up to (and until) he was being re-assigned and removed as admin and got fired, etc, etc.

    4. Re:This seems hard to swallow by pavon · · Score: 5, Interesting

      He maintained access to a system which he had no right to access, while refusing to give the owners of that system the means to remove his access in a manner that wouldn't significantly disrupt the service.

      Still I have a hard time seeing this as a crime. If an employee won't give you the keys to your vault, then you fire them, call a locksmith and sue the ex-employee for damages. No criminal charges, just a civil liabilities. That is what should have happened to Childs, no more no less.

    5. Re:This seems hard to swallow by mysidia · · Score: 1

      Given the level of competence they've shown so far (as evidenced by the articles), I wouldn't be surprised if they accidentally locked themselves out of their own accounts trying to break security.

      And blamed the automatic account lockout on the admin.

      In some systems, automatic account lockout happens if you repeatedly attempt to exercise privileges not assigned to your user, i.e. maybe some users tried to 'guess' a god password and su or enable from their account, and some automatic system throttled them.

      There are a lot of ways they could have gotten locked out that the sysadmin had nothing to do with (other than having configured it that way when the admin was still authorized to have full access and enter configuration decisions)

    6. Re:This seems hard to swallow by mabhatter654 · · Score: 1

      he had LEGAL means to have those, so the "hacking" point is moot. If they expected him to work late, or work from home, then it was part of his job tools. That access is a civil matter, unless it is PROVEN he caused actual, measurable harm... as he was in jail from the date of accusation, they have absolutely no trail to prove anything.

      Again, if that was true your boss could fire you while your on vacation, and having taken your company laptop and cell for emergencies, then charge you with theft and hacking... again, would never hold up in court with out better, legal measures first.... calling you 10x a day or sending cops to your location is not "reasonable".

    7. Re:This seems hard to swallow by mabhatter654 · · Score: 5, Interesting

      he set the routers to return to default under power failure. Actually that was a really smart move, these are in city building, probably stolen all the time. The router is only worth a few bucks, access to the network from a stolen router is priceless. The "consultants" tried to unplug them and read the settings to hack in. The routers did EXACTLY what he told them to...

      The biggest problem is procedural. This is why companies have audits, why SOX auditors demand documentation and cross training in public companies. The city management ALLOWED him to become more isolated and anti-social. They routinely pulled other people off helping him and allowed him to fly solo for several years and allowed the other employees and documentation to fall painfully behind.

      They didn't realize this until a new manager with a "dotted line" to his position didn't like him and tried to summarily fire him.. Then they realized first, Childs won his job back, and second he got to be an employee you "can't fire" because he had keys nobody could take! The prosecutor was dead wrong to take on a case directly from a department manager and not from higher up the HR food chain. Now the prosecutor realizes they bet their career on some petty middle-manager pushing somebody around. They're trying to find something to pin on him so they don't get seriously censured by the court for keeping this guy in jail 7 months.

    8. Re:This seems hard to swallow by Grimbleton · · Score: 1

      They charge gun owners in their own homes with possession of a tool of crime while serving warrants for other people, so that's not much of a leap.

    9. Re:This seems hard to swallow by ani23 · · Score: 1

      thats the problem. you can replace have a locksmit make new keys for your vault but still maintain the valuables inside. not the same with routers. u lose the config

    10. Re:This seems hard to swallow by ckaminski · · Score: 2, Insightful

      What they can charge you with, and what they can convict you with, are two very different things, and depend greatly on your lawyer and the judge and jury you draw.

    11. Re:This seems hard to swallow by Peyna · · Score: 1

      They're trying to find something to pin on him so they don't get seriously censured by the court for keeping this guy in jail 7 months.

      Judges set bonds, not prosecutors. Bond really only serves 2 main purposes. The primary one is to make sure you show up for trial. The secondary one is to protect the public from you, if there is a showing that are a serious potential danger to the public if you are allowed free pending trial. Given the nature of these charges, I'm guessing the judge decided the defendant was not likely to show up for trial on his own, or even with a significant amount of cash or surety at risk, so he set a high bond to guarantee his attendance at trial.

      --
      What?
    12. Re:This seems hard to swallow by Anonymous Coward · · Score: 0

      If an employee won't give you the keys to your vault, then you fire them, call a locksmith and sue the ex-employee for damages.

      A key is a physical object, and company property.

      A password is different, more like the combination to the vault.

    13. Re:This seems hard to swallow by Anonymous Coward · · Score: 0

      The config should be backed up somewhere (how else do you handle the router crashing and burning and a replacement needing to be built?).

      Worse case, you need to reset the router to factory defaults and then reload the config.

    14. Re:This seems hard to swallow by teknosapien · · Score: 1

      They did not prove unauthorized access. Oh wait he was in JAIL!!!!

      --
      no matter how good it is, it is human nature always wants to make things better
    15. Re:This seems hard to swallow by teknosapien · · Score: 2, Insightful

      or maybe he just didn't have the $$$

      --
      no matter how good it is, it is human nature always wants to make things better
    16. Re:This seems hard to swallow by pavon · · Score: 1

      Yep, like I mentioned, without the keys the only fix would cause significant disruption. That would make the damages even higher, but it's still an issue that civil court is most appropriate for.

    17. Re:This seems hard to swallow by Fulcrum+of+Evil · · Score: 1

      He maintained access to a system which he had no right to access

      You sure? The means to access are not the same as access.

      --
      "We returned the General to El Salvador, or maybe Guatemala, it's difficult to tell from 10,000 feet"
    18. Re:This seems hard to swallow by Achromatic1978 · · Score: 1

      You mean, the kind of behavior you're asking of the person you're firing for, amongst other reasons, not documenting the network to your desired standards or per your requirements? I could see how that might not work ...

    19. Re:This seems hard to swallow by _Sprocket_ · · Score: 1

      He maintained access to a system which he had no right to access, while refusing to give the owners of that system the means to remove his access in a manner that wouldn't significantly disrupt the service.

      Now hold on a minute. How is he maintaining access to a system he had no right to access? Because he knew privileged credentials?

      There was a time awhile back where we were doing audits of privileged accounts on infrastructure systems. There was a rather big stir when one account was found tucked away in the remote access system for an apparent "hacker". As it turned out, a variation of a former admin's real name happened to include the word "hacker" if you didn't understand the context. He hadn't worked there for years. Yet his account he had used to appropriately manage a system he was responsible for still existed. He could have logged in at any given time since he left.

      Are you saying the incompetence of a former employer and either their inability to follow, or even lack of, proper procedures can become a liability of the former employee?

    20. Re:This seems hard to swallow by arkhan_jg · · Score: 5, Informative

      He was sprung with a surprise secret audit, and claims he caught the auditor taking a hard-drive, at which point he confronted her. At which point she locked herself in, and called the CIO.

      On July 9, 2008 and at all relevant times, Richard Robinson was the Chief Operations Officer of DTIS [the San Francisco Technology Information Services Department]. Defendant unwittingly found himself at a meeting with Robinson in a room at the police station at the Hall of Justice. Present at that meeting were Lt. Greg Yee and Vitus Leung from the City's Human Resources Dept. Waiting outside the room but joining the meeting midway was Inspector Ramsey. The meeting was unorthodox and short on civilities. Defendant was told that he was being reassigned and was asked to disclose the FiberWAN passwords in addition to other passwords. There was no advance notice to defendant of this request. The surrounding circumstances of this request were unnerving and troubling to defendant at best. He resisted this surprise request to disclose the passwords to the FiberWAN, telling Robinson that no one was qualified to have the passwords. Under the pressure of the situation, defendant gave password information that could not be validated. During this exchange wherein defendant was questioned regarding the passwords, a speakerphone was on the desk in meeting room and people were listening in on the other end of the phone connection in a different part of the City.

      Would you have given over the root passwords for your network and servers in those circumstances? Especially since you're likely to take the blame and/or get sued if some monkey screws something up and then blames it on you.

      As you say, a civil action would have been more than adequate to recover them - he only wanted to hand them over in secure fashion to someone qualified to know them. He did hand them over the Mayor, "the only person he felt he could trust," a few days later, after he was already in jail.

      OK, Childs had a bit of a God complex, but after years designing something that intricate, and being the only 24/7/365 support for a few years due to budget cuts, it's understandable. They've basically charged him for having the tools, access and knowledge to actually do his job.

      Ironically, after claiming he was the one threatening the network, the city put the list of vpn passwords they found in his house into evidence unredacted, thus compromising half of the vpn 2-factor security for the entire network, forcing them to reset them all 2 days later; locking everybody out of the vpn access entirely. This was the first network outage since they imprisoned Childs, and was directly caused by the incompetence of the city technical management.

      --
      Remember kids, it's all fun and games until someone commits wholesale galactic genocide.
    21. Re:This seems hard to swallow by LingNoi · · Score: 1

      If anything this has shown you shouldn't work for government because not only do they fuckup anything they touch, they fuck up the only competent people they have.

    22. Re:This seems hard to swallow by Anonymous Coward · · Score: 1, Informative

      he set the routers to return to default under power failure. Actually that was a really smart move, these are in city building, probably stolen all the time. The router is only worth a few bucks, access to the network from a stolen router is priceless. The "consultants" tried to unplug them and read the settings to hack in. The routers did EXACTLY what he told them to...

      Has this ever been verified?

      When this was originally claimed, the city did not yet have the passwords. They hired consultants to gain access to the routers, but the consultants warned them that IF he had set the routers to return to default, they would have a problem.

      You claim the consultants tried to unplug the routers, but if they had done so, the network would have been down. It has been reported that the network had zero downtime until he gave the passwords to the Mayor (rather than some random middle manager who he probably wasn't even allowed to give the passwords to).

    23. Re:This seems hard to swallow by masonc · · Score: 1

      You have to ask, who were his supervisors? Did they not know they had no documentation or passwords before they decided to fire him? If you had a key admin who had sole access to vital information, wouldn't you review your position prior to firing him, such as, implement a policy to store passwords and configs in a secure safe, update your backups, etc. What was the rush to fire him? In my opinion, they got what they deserved. This is a case of bad management and hasty decisions and they should have been censored for their lack of foresight and for elevating this to a ridiculous level. The fact that Childs set conditions under which he would turn over the information indicated he was not keeping the information for malicious reasons. Game over.
      By and large I regard System Admins like Doctors. They have a right to special access to computer systems, and by implication, special responsibilities to protect that information. They should be held accountable for any misdeeds, punished more harshly for misuse of information, and trusted to access data in a way no layman would be.
      I had a situation where there was insinuations I had access to emails I should not of. When I explained I had access to the whole server and any information that passed through it, they realized it was ridiculous to make such accusations. I have had clients give me access to their bank account passwords, credit cards, just about every confidential document they own.
      If you don't trust System Administrators, then how will you have computer systems? Someone has to be trusted and with that trust comes an overriding responsibility to protect those systems, and that's what I see at play here. Childs may have overplayed his own responsibilities but that's not criminal.
      The reality is, most of the legal system is completely lost with regard to information systems and is terrified of the computer boogey man. They have no idea what they are dealing with.

      --
      CM www.cometenergysystems.com Blog: http://caribbeanrenewable.blogspot.com/
    24. Re:This seems hard to swallow by z_gringo · · Score: 1

      He didn't write the configs to flash memory. So that if the router had to be powered off, he would need to create the config from memory. This was his fucked up way of trying to make himself indispensible.

      --
      -- -- Warning. Do not stare directly at the sun.
    25. Re:This seems hard to swallow by bernywork · · Score: 1

      That seemed to be a claim, but that's not actually correct. The configs WERE written to flash, but if you did a password recovery on the device, the configs were wiped. This was to prevent someone getting access to usernames and passwords stored in the flash in case the equipment was stolen from an office.

      --
      Curiosity was framed; ignorance killed the cat. -- Author unknown
    26. Re:This seems hard to swallow by tinkerghost · · Score: 1

      Judges set bonds, not prosecutors.

      They also deny bail, Childs was denied bail when he was initially arrested under the theory he posed a threat to the network. I don't know if he has since been offered bail or not.

    27. Re:This seems hard to swallow by JavaRob · · Score: 1

      Would you have given over the root passwords for your network and servers in those circumstances? Especially since you're likely to take the blame and/or get sued if some monkey screws something up and then blames it on you.

      People keep making this point, but it isn't a good one. I mean, there's a whole crowd of people there; no one would question that he'd given *all* of those people access and they were all then responsible for whatever went wrong if they went onto the system. They couldn't just blame him, particularly if he's capable of tracing config changes and so on (which he should be). It wasn't his choice to make. It's their system to break if they want.

      OK, Childs had a bit of a God complex, but after years designing something that intricate, and being the only 24/7/365 support for a few years due to budget cuts, it's understandable. They've basically charged him for having the tools, access and knowledge to actually do his job.

      I'm not sure about the legal charges (they sound a bit dicey to me), but I'm quite sure he deserved to be fired. It's simple incompetence to set up any important system that fails the "bus" test so badly. I.e., if he got hit by a bus one day, they would have been screwed. He should *never* have been the only one with access -- if they couldn't afford a second admin to work with him, he should have had current passwords & setup details updated in a sealed envelope in his boss' desk (or something like that) -- whatever would be required to replace him without losing service in case of disaster.

      That bit just blows my mind, that they let him setup this whole fragile thing from the start. They should never have turned it on before he'd documented this stuff.

    28. Re:This seems hard to swallow by Crashspeeder · · Score: 1

      Just because you have access to a system doesn't mean anything you do is authorized. Even if you have admin privileges you're not allowed to throw scripts on there to steal passwords. That'd be unauthorized. Hijacking the system would fall under this category of use.

    29. Re:This seems hard to swallow by Anonymous Coward · · Score: 1, Insightful

      If there's nobody to replace you, due to budget constraints which are beyond your influence, then there's nobody to replace you, period. It wasn't a matter of keeping the "other guy" out of the loop. There was no other guy. Whether or not he had a dead man's switch (instructions in his will, etc.) is unknown, because he was still in the position to hold and use the access credentials. He was questioned by people unknown to him (some even outside the room) and without the legal authority to have those keys. It was right not to give up the credentials without the proper formal request from an authorized person. A system which works until someone with hardware access changes all access credentials isn't fragile, btw.

    30. Re:This seems hard to swallow by arkhan_jg · · Score: 1

      Oh, I'm not disagreeing it was pretty much inevitable that he'd be fired. Effectively telling your boss to fuck off when he gives you an order is unlikely to be good for your long term job prospects. As you say, he could have written them all down beforehand and stuck them in a safe somewhere, to increase the bus factor. (my colleague that I trust has all the root passwords, just in case)

      The fear over getting blamed for someone else's mistakes isn't complete horseshit though; look at the things they've tried to stitch him up with since, including outright falsehoods and complete misunderstanding of the tech (11000 modems hidden in filing cabinets!) Given there appears to a serious lack of competent technical staffing in the department, and the management are just breathlessly bad, it's entirely possibly they'd screw up the changes afterwards, blame him for 'setting up a booby trap' and then sue him for damages.

      They should never have let it get to this situation - that's a clear failure of management. It appears pretty likely they already had an agenda to get rid of him in the first place, thus the secret audit that kicked it all off. Was he overly paranoid? Quite possibly - but since it looks like they really are out to get him, that's not really paranoia any more.

      If they manage to successfully prosecute this guy on the criminal charges they've already laid against him, with the dodgy evidence and complete lack of technical understanding by the prosecution, then every competent network tech in the state is at risk for the same charges.

      --
      Remember kids, it's all fun and games until someone commits wholesale galactic genocide.
    31. Re:This seems hard to swallow by Grimbleton · · Score: 1

      And that does nothing to argue with my statement, based on the discussion of what they can charge you with.

      (P.S., they've convicted based on nothing more than that)

    32. Re:This seems hard to swallow by neomunk · · Score: 1

      You can't honestly believe that this experience is limited to governments and that corporations are somehow immune. This is, of course, a problem with bureaucracies in general, and has nothing to do with the public/private status of said organization.

    33. Re:This seems hard to swallow by delcielo · · Score: 1

      Would you have given over the root passwords for your network and servers in those circumstances?

      Yes. I would. I wouldn't like it; but it's not my right to withhold them from the rightful owners. being insulted or mistreated does not make it right to do what Terry did. You can argue that the City was stupid, or even malicious; but they didn't do anything illegal.

      It's their network. Not Terry's.

      This case will cause grief for sysadmins for a long time to come because it completely validates the perspective of auditors who consider us to be the biggest risk to a company's data systems.

      The short-sightedness around here is actually quite surprising to me.

      --
      Hot Damn! It's the Soggy Bottom Boys!
    34. Re:This seems hard to swallow by TheVelvetFlamebait · · Score: 1

      A key is a physical object, and company property.

      A password is different, more like the combination to the vault.

      OK, let's break this down.

      A password is not company property. Why? Because a password is information (not physical).

      A piece of information is not property. Why? Because you can't deprive someone of information like you can property.

      BUT Childs did deprive the "owners" of the information. It is possible! Does this then make passwords property?

      --
      You know, there is a difference between trolling and pointing out the flaws in your reasoning. Just saying.
    35. Re:This seems hard to swallow by LionMage · · Score: 1

      Yes, but when you work for any kind of government agency, you have additional restrictions placed upon you that you might not have in a corporate job. Public sector has a lot of compliance issues to deal with, more than private sector IMHO. The big difference, though, is that the government has some truly scary means at its disposal to force compliance, and if you manage to piss off the wrong people (i.e., clueless or assholish people in power), you can get swatted pretty hard -- a lot harder than in the private sector, generally speaking. In the private sector, if there's any legal action, it's usually civil. In the public sector... well, we saw what happened in this case, didn't we? This never should have escalated to the point where people were discussing the option of jail/prison time. And if this were a case of criminal wrongdoing in the corporate world, there's no way the authorities would have acted anywhere near this fast or this severely.

    36. Re:This seems hard to swallow by Vancorps · · Score: 1

      while you are correct that this is not limited to government entities I think it is worse when it is government related. I think any business out there would have handled this very differently and Childs' would have ended up in jail if he worked for a business.

      Because the city was out to get him the police naturally followed suit and so did the DA as they all serve the city.

    37. Re:This seems hard to swallow by Vancorps · · Score: 1

      You seem to think that admins aren't the biggest risk to a company's data?

      As a sys admin I can safely say that a few wrong keystrokes and a lot of data is gone requiring me to go back to tape to fix.

      The person with all the access is the person that can do all the damage whether intentional or not. I've made some pretty bone-headed moves in my day that have caused a little data loss resulting from a missing XO option on a robocopy because I was too tired to handle the one-off task. This is why you automate as much as you can as often as you can because machines are a hell of a lot more consistent.

      Childs' had no obligation to give up passwords to people he didn't know, plain and simple. In fact, he had no obligation to give up passwords to anyone he did know. The employment was terminated, any and all interaction afterwards is voluntary for either party.

      He didn't set any traps, he did his job as any competent admin would have from a technical standpoint but lacked the political skills to remedy upstream stupidity. That stupidity is demonstrated by the simple fact that he was indeed the only one with the passwords which should have been a flag before the firing. Of course he could refuse to give up the passwords while still being employed with the end result being the termination of his employment like would happen in any corporate setting.

      This is gross mismanagement and now they are looking to fry someone that had the balls to call them on it publicly even going to jail to prove his point.

    38. Re:This seems hard to swallow by JavaRob · · Score: 1

      If there's no other guy, it was his responsibility to make sure his boss always had access to the information another network admin would need to replace him -- sufficient documentation of the system including all passwords required to administer it.

      And sorry, but yes: the system was fragile. If only one person has the access required to manage the system in any way, then the moment something happens to him (incapacitated, or simply with a dead cellphone battery on vacation when something goes wrong...) they're screwed. It's not much comfort that "it's running now" when you have no way of fixing the problems that will arise 1 week, 1 month, or 1 year down the line.

      Who would intentionally pay someone to set up a network for them with a configuration set in stone?

    39. Re:This seems hard to swallow by neomunk · · Score: 1

      You do have a point there, at least in regards to major industrial nations. To be fair though, the difference between going to jail and losing everything you've worked hard for isn't much consolation when it's happened to you.

      In third world nations the situation looks more balanced, as you're just as dead when Chiquita decides your life is forfeit as when the neighboring warlord does.

    40. Re:This seems hard to swallow by Cederic · · Score: 1

      it's not my right to withhold them from the rightful owners

      No, but it is your responsibility to withhold them from unauthorised people. Since the people listening included a number of people that explicitly lacked authorisation it would at best be irresponsible and unethical of you to share the passwords, and potentially illegal and actionable.

      Under those circumstances would you
      - pretty much guarantee a criminal charge by sharing the passwords
      - risk potential prosecution for rightfully withholding passwords

      Lets face it, the guy was fucked either way.

    41. Re:This seems hard to swallow by mabhatter654 · · Score: 1

      They only unplugged 3-4 before they got the message... that's when they stopped doing it and the prosecutor went nuts on the guy for the passwords. They WERE going to have to rework the network settings from scratch... but he turned over the passwords, so they shouldn't have had to do that.

      At this point, he's no threat at all. In fact the prosecutor isn't coming up with charges that warrant much more jail time than he's already served as there's been no "damages" or even potential damages discovered. Like any non-admin they're reaching for straws that because routine stuff has "broken" with no intervention he "planned" it... you'd be surprised how many highly paid, intelligent people think that little of IT people.

  6. popular trend in the courts lately by v1 · · Score: 5, Insightful

    If you don't like what someone does, but strictly speaking it's not really illegal, then find something else they did, (something that maybe a lot of people do and get left alone for) that has some silly, overly-broad definitions you can twist, and soak him for that instead. (ether as substitute punishment for the former that you can't make stick, or just plain in retaliation for doing something you didn't like)

    As usual, the legal system that makes me sick to my stomach some days.

    --
    I work for the Department of Redundancy Department.
    1. Re:popular trend in the courts lately by Anonymous Coward · · Score: 1

      "There's no way to rule innocent men. The only power government has is the power to crack down on criminals. Well, when there aren't enough criminals, one makes them. One declares so many things to be a crime that it becomes impossible for men to live without breaking laws." - Ayn Rand

    2. Re:popular trend in the courts lately by Anonymous Coward · · Score: 0

      this happened a lot in the Dark Ages, I think it was called witch hunting...

    3. Re:popular trend in the courts lately by pentalive · · Score: 1

      Ayn Rand was a founding father?

    4. Re:popular trend in the courts lately by Ihmhi · · Score: 1

      Ayn Rand isn't even a man...

    5. Re:popular trend in the courts lately by msuarezalvarez · · Score: 2, Funny

      At least, that's what he has managed to convince his followers of...

    6. Re:popular trend in the courts lately by Big+Hairy+Ian · · Score: 1

      Famously Al Capone & Tax evasion.

      --

      Build a Man a Fire, and He'll Be Warm for a Day. Set a Man on Fire, and He'll Be Warm for the Rest of His Life.

    7. Re:popular trend in the courts lately by Anonymous Coward · · Score: 0

      No wonder the government of California is going broke - they're spending the taxpayers' hard-earned money on stuff like this instead of actually providing useful, necessary services.

      Well, I don't live in California, and this episode makes me even more reluctant to lend them a dime, regardless of the interest rate.

    8. Re:popular trend in the courts lately by Anonymous Coward · · Score: 0

      Famously Al Capone & Tax evasion.

      Actually, how Al Capone got his money (bootlegging and prostitution rackets) was illegal at the time. However, they could never gather enough admissible evidence of his direct involvement to try him for it. The tax evasion case worked because Al Capone didn't have a plausibly legal explanation for his readily apparent wealth. Therefore he couldn't tell the truth to the IRS without incriminating himself, presuming he even cared about such things.

      To me there's a non-trivial difference in prosecuting someone for only part of the actual crimes they commited versus using a warped interpretation of criminal law to punish someone when it really is a matter for the civil courts.

    9. Re:popular trend in the courts lately by compro01 · · Score: 1

      IRS Publication 525 (2008), Taxable and Nontaxable Income

      Illegal activities. Income from illegal activities, such as money from dealing illegal drugs, must be included in your income on Form 1040, line 21, or on Schedule C or Schedule C-EZ (Form 1040) if from your self-employment activity.

      --
      upon the advice of my lawyer, i have no sig at this time
    10. Re:popular trend in the courts lately by Walkingshark · · Score: 1

      This isn't really a "lately" thing. They've been doing this to people since laws were invented. Thats why you hear stories about mafia guys going down for tax evasion.

      --
      The world you experience is only a close approximation of reality.
  7. Obligatory KITH link. by ebbomega · · Score: 3, Funny
    --
    Karma: Non-Heinous
    1. Re:Obligatory KITH link. by EddyPearson · · Score: 0, Flamebait

      I had never seen this show before. Now that I have, I consider the last 20 years of ignorance a blessing. The script reads like a 13 year old wrote it.

      Awful.

      --
      You feel sleepy. Close your eyes. The opinions stated above are yours. You cannot imagine why you ever felt otherwise.
    2. Re:Obligatory KITH link. by n1ckml007 · · Score: 3, Funny

      I'm crushing your head.

  8. I would love by malkir · · Score: 1

    For some outspoken person in the courtroom to just ask the judge and prosecuters if they even have rudimentary knowledge of network administration and the tools common for such a profession.

    So will I now be eligible for lawsuit since I have multiple means of accessing my businesses networks?

    1. Re:I would love by Anonymous Coward · · Score: 0

      If I remember correctly in another case called something like "Apple vs. Microsoft" only two people in the jury had college degrees and none owned a personal computer.

      But the Court thought them smart enough to understand the nuances of GUI design...

      The point being, rudimentary knowledge of anything is of no interest to the court. They'll have Expert Witnesses for that.

    2. Re:I would love by plover · · Score: 2, Interesting

      During voir dire the lawyers probably asked if any of them were network professionals and dismissed those that were.

      The court wants only the presented evidence and facts to enter the case, not the external, uncontrolled ideas of some hacker ranting in the jury room. When I served on jury duty, the judge made it plain that in that case the law was only what he told us it was. We weren't to consider things from outside of the courtroom.

      It's kind of like designing code. He's trying to minimize external dependencies.

      That said, it still seems pretty stupid.

      --
      John
    3. Re:I would love by I'm+not+really+here · · Score: 1

      Where is his jury of peers then? A guy who flips burgers at the local McDonald's and doesn't know a thing about networking or the tools of the trade is certainly not his "peer". Neither would a CEO of a multinational pharmaceutical company be his peer. Only others who have a general knowledge of his general field (various IT folks, engineers, and others who could readily understand the technology involved in the criminal case) should really be considered "peers." I'd file for a mistrial if no one on the jury knew anything about network administration in some form or another.

      --
      Before commenting on the Bible, please read it first
    4. Re:I would love by Anonymous Coward · · Score: 0

      the judge made it plain that in that case the law was only what he told us it was. We weren't to consider things from outside of the courtroom.

      God forbid something like "truth" or "facts" snuck into the room through a juror's head.

    5. Re:I would love by tomhudson · · Score: 0

      Where is his jury of peers then?

      I don;'t think you know the meaning of that word.

      "Peers" were originally your betters, not your equals. Peers comes from the English peerage. A "jury of your peers" literally meant those who lorded it over you. Duke, Marquess, Earl, Viscount, and Baron. Don't see no commonfolk there, guv'nor.

    6. Re:I would love by Peyna · · Score: 1

      I want you on my juries. It's good to know some people actually take their oaths and admonitions as jurors seriously.

      In fact, the more I think about it, the more I would like a very technical oriented individual as a juror, since they're more likely to follow the rules given to them for a specific situation, and logically apply the facts they see to those rules.

      Now if only jury venires tended to have people in them other than those without jobs.

      --
      What?
    7. Re:I would love by shadowturtle · · Score: 1

      You forgot "common sense"

    8. Re:I would love by Anonymous Coward · · Score: 2, Insightful

      How does that get rated "interesing". Par is the Latin word for equal (still used with that spelling for things like golf), and peer is the modern English derivative. The Romans came somewhat before the British Peerage.

      I assume British Peers they are called that because they are expected to treat each other as equals, even if they have contempt for the poor suckers.

    9. Re:I would love by Anonymous Coward · · Score: 0

      How does that get marked "insightful"? Peer may be the English derivative of a Latin word, but the Romans never spoke English and its proper usage in English refers to the peerage, regardless of its origin in antiquity.

    10. Re:I would love by tomhudson · · Score: 1

      How does that get rated "interesing". Par is the Latin word for equal (still used with that spelling for things like golf), and peer is the modern English derivative. The Romans came somewhat before the British Peerage.

      We got the phrase "trial by a jury of your peers" from England, not Rome. Context counts.

      I assume British Peers they are called that because they are expected to treat each other as equals, even if they have contempt for the poor suckers.

      You assume wrong.

    11. Re:I would love by plover · · Score: 1

      You can be a smart person, know nothing about networking, and still be an effective juror.

      Consider a case about a technical topic on which you may know very few specifics; let's say it's about someone infected with a strain of salmonella. The lawyers for the defense may present an expert witness who studies bacteria. This guy comes up and says "I look at bacteria all day, and this isn't the same strain as the one the plaintiff claims it is. Here is a picture of what I looked at: see this curly tail? That's only curly on strain X. Now look at the picture of the plaintiff's bacterium. It has a straight tail, meaning it's not strain X. Different strains mean that your client didn't get his salmonella from my client's restaurant."

      The plaintiff's expert then comes out and says "in the old days we used to look at salmonella tails, but today we sequence the genomes. You can see here that this is a strain that is only two mutations separated from the other, and the chances of that happening in this case are very high because of the time difference in taking the samples. Therefore, my client did get salmonella from your client's restaurant."

      Now, you don't have to be a biologist or geneticist to understand and evaluate the facts as they were presented. What the court is asking you to do is sort out which of the experts is right. And frequently, they both are, to some degree.

      It's kind of like Star Trek, where everything has a complicated technical explanation, then someone comes around and makes a simple analogy, like someone putting too much air in a balloon.

      --
      John
    12. Re:I would love by plover · · Score: 1

      Common sense is pretty much the attribute that both sides desire in jurors (except in a criminal trial where the defendant is actually guilty, in which case the lawyer tries to stack the jury with easily swayed idiots.)

      --
      John
    13. Re:I would love by N1AK · · Score: 1

      I absolutely agree with that definition of a peer. Exactly where would the line be drawn about whom your peers were? The last thing I want is legal system where you can dodge crimes because they are the sort of crimes 'a selective group of people similar to you' don't want to punish.

      There is merit to the idea of having 'specialist' juries for certain forms of crime, for example accounting, but this still has a lot of downsides. The biggest of which is it makes loading the Jury to decide the desired way will become easier.

    14. Re:I would love by plover · · Score: 1

      Oh, what I missed saying here is why an "expert juror" could be a bad thing. The court doesn't explore your expertise, and doesn't know if you're qualified. You might be a world-renowned bacteriologist, or you might be a guy who has a 20 year old doctorate in biology back when they only taught the "tail theory of classifying salmonella" or whatever.

      And the lawyers don't have the time or knowledge to vet every juror in depth. It's better to get jurors who are intelligent, but not necessarily experts in the subject matter.

      --
      John
    15. Re:I would love by Hatta · · Score: 1

      I would love for the people responsible for his jailing to be thrown in jail. This is a major problem with our system. Kidnapping is wrong, whether the state does it, or whether an individual does it. When an innocent person is kidnapped by the state and held for months there need to be consequences for those responsible.

      --
      Give me Classic Slashdot or give me death!
    16. Re:I would love by melikamp · · Score: 1

      This example is better than you likely realize. After I heard the first witness, I was totally convinced, but the second witness completely reversed the argument. If I was on the panel, I'd have no idea whom to believe.

    17. Re:I would love by poot_rootbeer · · Score: 1

      The court doesn't explore your expertise, and doesn't know if you're qualified. You might be a world-renowned bacteriologist, or you might be a guy who has a 20 year old doctorate in biology back when they only taught the "tail theory of classifying salmonella" or whatever.

      Have you never served on a jury? The first thing the attorneys on both sides will do during jury selection is say to the prospective jurors, "this court case involves salmonella poisoning. If any of you have a background in biology studies, even if it was just high school coursework, please raise your hand now."

      Neither side WANTS an expert juror to hear the case, because of the risk that he or she would discourage the other jurors from agreeing with the carefully orchestrated expert testimony that they will be incorporating into their argument.

    18. Re:I would love by plover · · Score: 1

      Yes, that was exactly my point.

      --
      John
    19. Re:I would love by jbengt · · Score: 1

      A jury of peers means that a commoner is tried by other commoners, not by noblemen, and noblemen are tried by similar noblemen, not commoners. That reduces the chances of verdicts that are about "stickin' it to the rich bastard", or "teach the rabble a lesson", rather than the facts and laws.

    20. Re:I would love by I'm+not+really+here · · Score: 1

      Exactly. Think about it - a common user is in the jury. That user is only familiar with network administration insomuch as it interferes with their enjoyment of their job (unable to access YouTube, etc.). This individual could be biased simply because of position ("stickin' it to the arrogant IT Admin"), rather than facts and laws. Other IT industry managers (not just IT Admins, but other managers in similar level positions with similar level experience and responsibilities) would be better able to understand both sides of the story. A jury of end users (some likely with a thing against admins telling them what they can do) is certainly not a jury of his peers.

      --
      Before commenting on the Bible, please read it first
  9. Pinstripes? by iminplaya · · Score: 1

    I haven't seen pinstripes on a prisoner since the Three Stooges.

    --
    What?
    1. Re:Pinstripes? by Peyna · · Score: 1

      Our local inmates wear Hamburglar outfits. The only thing missing is the hat.

      --
      What?
    2. Re:Pinstripes? by actionbastard · · Score: 1

      Seems to work for this guy...BTW, love the chopper!

      --
      Sig this!
    3. Re:Pinstripes? by gnapster · · Score: 1

      You must not live in Phoenix, Arozona.

    4. Re:Pinstripes? by sunking2 · · Score: 1

      It's all about pink now. Much to DMX's chagrin.

  10. Don't be rediculous... by Pichu0102 · · Score: 2, Insightful

    All the authorities would have to do is 'point out that you have a modem or two, and suddenly you're wearing pinstripes of the jailhouse variety.'"

    Of course they wouldn't do that.
    They'd use that fact as leverage to extract whatever they want from you first.

    1. Re:Don't be rediculous... by Anonymous Coward · · Score: 0

      How can I re dick you less if I've never dicked you in the first place? Unless you meant ridiculous...

    2. Re:Don't be rediculous... by Biff+Stu · · Score: 1

      Besides, pinstripes are sooo dated. Think orange jumpsuit, baby!

  11. Wow by yerktoader · · Score: 1

    Wow...7 months and the charge is dropped? That smacks of injustice, but IANAL.

    I don't know what Venezia's background is...It would be interesting to hear from NewYorkCountryLawyer on this and the RAMBUS decision.

    1. Re:Wow by Concerned+Onlooker · · Score: 1

      Just think of it as a short Gitmo stint.

      --
      http://www.rootstrikers.org/
  12. Plus a quarter million to fix the problem... by mrbene · · Score: 2, Interesting

    So not only did he withhold passwords.

    And have modems attached to computers.

    But it's going to take 250,000$ to fix.

    Can the defense claim insanity on behalf of the prosecution, 'cause I think we've just hit bat country!

    1. Re:Plus a quarter million to fix the problem... by dbIII · · Score: 1

      Oh really? I suggest reading Bruce Sterling's "The Hacker Crackdown" to get a history of how these costs are overstated when somebody wants a show trial.

    2. Re:Plus a quarter million to fix the problem... by jamstar7 · · Score: 2, Interesting

      Like AT&T trying to show that they had to buy a spendy mainframe for the exlusive use of one tech writer and then a supervisor for said tech writer so they could pad the 'damages' in a trial by the cost of the mainframe, 6 weeks 'work' by the tech writer at 40 hrs/week & the same for the supervisor, when the very same manual that was 'stolen' was for sale for like 10 bucks?

      --
      Understanding the scope of the problem is the first step on the path to true panic.
    3. Re:Plus a quarter million to fix the problem... by Anonymous Coward · · Score: 0

      That's a nice one. I also remember hearing that Sun accused Kevin Mitnick of stealing their entire software development budget for several years because he had a copy of Solaris kernel code that was floating around IRC at the time. It came out to an 8-digit figure, and they were selling it for three digits if not at the time then shortly afterward.

    4. Re:Plus a quarter million to fix the problem... by Ellis+D.+Tripp · · Score: 2, Interesting

      Very similar to the way that the "street value" of seized drugs are reported after a bust.

      If a large pot grow gets busted, the total crop gets valued as if it were broken down into tens of thousands of nickel bags and sold at retail.

      --
      Remember "News for Nerds, Stuff that Matters"? Help make it a reality again! http://soylentnews.org
    5. Re:Plus a quarter million to fix the problem... by _Sprocket_ · · Score: 1

      The suggestion by dbill to read "The Hacker Crackdown" is good. But I'll throw in some more insight.

      There are some WAGs (wild ass guess) involved. But there's real numbers too. The problem is whether these numbers are really appropriate.

      A part of the money spent on these incidents probably should have been spent before they became emergencies. Like everything else, preventive measures are not only cheaper but less damaging in the long run. Instead, moneys are spent from emergency funds paying emergency rates for contractors who charge a lot to deal with high pressure situations. And, of course, money that should have been spent to do these things before they became an incident get tagged on to the bill.

      The second gotcha is evidence. Law enforcement (especially Feds) will seize equipment to maintain it as evidence of the intended-to-be-prosecuted crime. It is more common now to eventually return what can be returned and withhold hard drives, etc. Nevertheless, equipment is out of service for, at least, some time and must be replaced. That replacement gets tacked on to the bill.

    6. Re:Plus a quarter million to fix the problem... by pxc · · Score: 1

      Did you not read the last line mrbene wrote? He's on your team, buddy!

    7. Re:Plus a quarter million to fix the problem... by dbIII · · Score: 1

      It's an "oh really?" to the people that told infoworld this before they wrote the linked story. I don't think we can trust those that are running trial by media on Terry Childs on those figures based on how things have been inflated so much in the past. Some of the stuff they have leaked to the press (1000 modems, "intimidating" the new security person by asking WTF they are in someone else's office at night etc) is getting spun beyond reality.

    8. Re:Plus a quarter million to fix the problem... by Anonymous Coward · · Score: 0

      Oh really? I suggest reading Bruce Sterling's "The Hacker Crackdown" to get a history of how these costs are overstated when somebody wants a show trial.

      IIRC, one of the points he made was that security conslutants will start by recommending that management hire a "team" of other conslutants to "thoroughly evaluate the damages", solely to balloon the purported damages to a dollar amount that makes the "crime" count as a felony. This accomplishes two things -- a) it grants extreme leverage on the accused as the stakes are now much higher and b) it guarantees greater attention from LE in general, which is often reluctant to commit resources to prosecuting a misdemeanor.

      This is common in fields other than IT as well. IIRC, when some guy years ago clean-climbed the Transamerica pyramid in San Francisco, TA management was encouraged to hire a structural engineering outfit to minutely examine the path the guy had taken, looking for "structural damage". By blowing enough money to bring costs to felony level, they could lean on the guy for such things as promises not to do the same anywhere else in future as a giveaway for not prosecuting. Presumably he would have to retroactively fulfill some additional obligations if he repeated.

      How ridiculous -- one guy clean-climbing a building -- how much "damage" can he be expected to do to a structure built to withstand an 8.x magnitude earthquake? Certainly less than the damage due to wind flexing on a bad day. Yes, I have been to the top inhabited floor of the building. It's occupied by the president of the corporation (rarely) and by his secretary. The other half of that floor consists of the boardroom. No, I think I'd not like to be there during severe weather, at least if barf bags were not provided, but it sure would be a hell of a place to watch a storm coming in from the Pacific.

  13. Section 502 by russotto · · Score: 5, Informative

    Section 502(c) states in part

    Except as provided in subdivision (h), any person who commits
    any of the following acts is guilty of a public offense:

    (6) Knowingly and without permission provides or assists in
    providing a means of accessing a computer, computer system, or
    computer network in violation of this section.

    OK, "knowingly" makes sense, but "without permission"? The man was the network administrator; he was authorized to make decisions about how the network is accessed, it goes along with the job. Who was he to get permission from, himself? If he made bad decisions, by all means dismiss him, but prosecuting him is unreasonable.

    And since they dropped the most serious charge, can we admit his 8th amendment rights were stomped and pissed-upon by the 5 million dollar bail requirement?

    1. Re:Section 502 by Greventls · · Score: 1

      After he is let go, he no longer has permission.

    2. Re:Section 502 by russotto · · Score: 1

      He didn't set up the modems after he was let go, and these charges are for "providing a means of accessing", not "accessing".

    3. Re:Section 502 by nettdata · · Score: 1

      The man was the network administrator; he was authorized to make decisions about how the network is accessed, it goes along with the job. Who was he to get permission from, himself?

      Oh please...

      You have NO way of knowing that it was his decision. And it's a government... odds are that he was NOT allowed to make that decision.

      I know that in my shop, the network admins do not have that kind of autonomy. They can make all the recommendations they want, but it's not their decision.

      For all we know, he may have asked his superiors for permission and they failed to give it, and he went ahead and did it anyways.

      --



      $0.02 (CDN)
    4. Re:Section 502 by mysidia · · Score: 5, Insightful

      After he is let go, he no longer has permission.

      However, he cannot be prosecuted on the basis of actions he took at the time he had permission to take them.

      There would be a 4 word phrase for that: ex post facto law. Explicitly prohibited by the constitution.

      Along with Bills of Attainer, which is almost what throwing someone in jail without trial for a year with a $5 million bail amounts to, he has been declared guilty by the state and is being punished without trial.

      A few years later when the finally gets a trial, they'll say "oops, my bad", and let him go, after using various means of persuasion to ensure he doesn't proceed with any lawsuit for the false imprisonment.

    5. Re:Section 502 by plover · · Score: 4, Funny

      I can't find the "Mod: +7 True, but fucking pathetic" button.

      --
      John
    6. Re:Section 502 by Anonymous Coward · · Score: 0

      There would be a 4 word phrase for that: ex post facto law. Explicitly prohibited by the constitution.

      Explain that to Congress, who have been ex post facto passing copyright extensions for the past 70 years, then?

      Fitting that the captcha that just came up was "lawless"...

    7. Re:Section 502 by Entropy2016 · · Score: 4, Interesting

      While I agree that what's happening to him is likely unjust, I would like to point out something...

      However, he cannot be prosecuted on the basis of actions he took at the time he had permission to take them.

      I have to call bullshit here. Ex post facto laws are explicitly unconstitutional but that doesn't prevent government from passing laws which have ex post facto effects. To anyone who claims that there isn't a distinction, I must say that you obviously are not a lawyer. A good example is CERCLA: The Comprehensive Environmental Response, Compensation, and Liability Act. If you dumped hazardous waste somewhere 50 years ago, hazardous waste which at the time was legal to dump where you dumped it, when you dumped it, you are NOT protected from legal action by the government. You WILL be held financially responsible for getting that mess cleaned up. Now in the case of CERCLA, I'd say that while it's harsh, it's necessary & justifiable. (Probably not so much so with the prosecution's case against Terry Childs).

    8. Re:Section 502 by mysidia · · Score: 5, Informative

      You're confounding civil law with criminal law. They are in entirely different ballparks.

      New laws can always impose new responsibilities on you, financial or otherwise, and those responsibilities may be increased by your past actions. But they can't change something you did in the past that was within the law from being a legal action to being a crime.

      It is either a crime at the time the act is performed, or not a crime.

      They're not attempting to hold Childs financially liable. They're attempting to charge him with a crime.

    9. Re:Section 502 by Entropy2016 · · Score: 1

      I interpreted the line of yours I quoted to be a statement discrediting ex post facto behavior in general (not specifically criminal). If they are charging him criminally then yes you're hopefully right.

      That said, there are exceptions that permit ex post facto law in the case of US Administrative Law. If I recall, he was working for the state of California. Not sure if that could affect his case or not, but I wouldn't' rule it out without doing some legal research.

    10. Re:Section 502 by Peyna · · Score: 1

      That wouldn't really be ex post facto. You're making a factual argument that there was consent. Consent is an affirmative defense, which means the burden is on him to prove it. Ex post facto would be the situation where the law did not prohibit his actions, but then was later changed to prohibit his actions, and he is prosecuted for actions that took place prior to the change in law.

      Nor is your other example a bill of attainder. The defendant was charged by the state with a crime, and brought before a (hopefully independent) judge. That judge decided that the amount of bond necessary to guarantee the defendant's attendance at trial was $5,000,000. It is not punishment, it is just the only reliable mechanism available to us to make sure people show up to court when they're supposed to.

      --
      What?
    11. Re:Section 502 by mysidia · · Score: 1

      Perhaps. Observation: 502(c) is not really US Administrative law, in the traditional sense, it is California penal code; Computer Data Access & Fraud Act'

      If he had the needed permission, when he "provided" means of accessing a computer or network, then presumably he wasn't in violation of (6).

      The permission is no longer relevant now, but he would have had permission to gain access to and administer the network when he performed the acts in question -- setting up/procuring modem access.

      Also, given his unwillingness to share passwords, I would think it unlikely he would have provided anyone else the means to conduct any of those illegal activities.

      (6) doesn't really say anything about securing or obtaining means to access, only about providing someone the means in violation of (other parts of) the section.

    12. Re:Section 502 by 91degrees · · Score: 1

      can we admit his 8th amendment rights were stomped and pissed-upon by the 5 million dollar bail requirement?

      I think that the "Excessive bail shall not be required," part of the 8th Amendment has been comprehensively stomped on for some years now. The fact that the majority of people need to effectively take out a high interest loan to pay bail makes a mockery of the system.

    13. Re:Section 502 by Anonymous Coward · · Score: 0

      The man was the network administrator; he was authorized to make decisions about how the network is accessed, it goes along with the job.

      Possibly. Depends on the way things were set up at his job. In some cases, he would've had the authority. In other cases, he'd have needed anything from a manager's okay, to written authorization from his ISO and/or CIO. Remember, this is government, it carries with it a certain level of bureaucracy.

  14. Jeeezzzzzussss by MightyMartian · · Score: 1, Insightful

    I can't believe this megomaniacal prima dona is now somehow the posterboy of the IT people. There were ways for this nutbar to get out of the quandary while still saving his ass. Instead, he holds a network [b]that does not belong to him[/b] for ransom.

    --
    The world's burning. Moped Jesus spotted on I50. Details at 11.
    1. Re:Jeeezzzzzussss by Dun+Malg · · Score: 5, Insightful

      I can't believe this megomaniacal prima dona is now somehow the posterboy of the IT people. There were ways for this nutbar to get out of the quandary while still saving his ass. Instead, he holds a network [b]that does not belong to him[/b] for ransom.

      Well, it's just like 1st Amendment cases involving pornography, marching down the street in neo-Nazi uniforms or hooded bedsheets, or the like. You have to fight the idiots who would deny basic rights or make a mockery of law unilaterally, even when they go after the dirtbags. Letting them ignore the law when they beat down the unpopular is just giving them a free pass to do the same to you in the future, when it strikes their fancy.

      --
      If a job's not worth doing, it's not worth doing right.
    2. Re:Jeeezzzzzussss by socsoc · · Score: 4, Funny

      Those damn IT people and their correct usage of HTML tags on a tech website, always holding BBCode tags hostage for ransom...

    3. Re:Jeeezzzzzussss by db32 · · Score: 1

      Just to play devil's advocate it WAS his network assuming he paid taxes. Arguably he was trying to protect the tax payers investment. I haven't exactly kept up on it, but I thought he even told the judge/lawyer something to that effect (I'm not giving him the passwords because he is an incompetent tool that will break it all). Now...whether he went about doing this in the correct fashion is certainly another issue, but if every citizen protected public investments like that we wouldn't have a 10 trillion dollar debt.

      --
      The only change I can believe in is what I find in my couch cushions.
    4. Re:Jeeezzzzzussss by Ossifer · · Score: 1

      No, it was NEVER "his" network, even if he paid taxes. It continues to belong to the City/County of San Francisco, where I MYSELF pay taxes. Terry Childs was NOT a resident of San Francisco (his home is in the East Bay). Even though I am an SF taxpayer -- I don't claim ownership of city property.

      I can't believe how you people defend this guy--it's ridiculous. The man has a history of VIOLENT criminal activity (not that that has bearing on his recent criminal activity), he should never have been TRUSTED with this position.

      I am an IT professional (not a hacker with an IT job) who is fed up with the Mordachs and the IT Nazis that seem to be so pervasive amongst my colleagues. Childs had a dispute with his bosses (competent or not) and his reaction was to hold the city hostage. HE BELONGS IN JAIL.

    5. Re:Jeeezzzzzussss by Fulcrum+of+Evil · · Score: 1

      It was his network to run - that was his job. We are defending this guy because he's being railroaded, and that could affect us in the future.

      --
      "We returned the General to El Salvador, or maybe Guatemala, it's difficult to tell from 10,000 feet"
    6. Re:Jeeezzzzzussss by db32 · · Score: 1

      I looked around and I couldn't find anything even mentioning him having a "VIOLENT" criminal history. In fact, all I could find was references to how insane it is to put a non-violent offender behind bars the way they did. So...again...not that I agree with what the guy did (as I previously stated), but I would be interested to hear why you are insisting that he is a violent criminal that needs to be put in jail.

      I am going to go ahead and guess that you have been one of the lucky ones that never had to work for a dangerous flaming asshole. I have had the joy of working for meglomaniac style bosses without a clue on more than one occasion. In one instance I told him "This is not right, we should not do this, it is known to not work" and I got "Do it anyways because I said so"...then when it failed and the customer lost all their data guess who got fired to make the customer happy...

      --
      The only change I can believe in is what I find in my couch cushions.
    7. Re:Jeeezzzzzussss by Ossifer · · Score: 1

      From a quick google search: "He [Childs] has already served four years in Kansas prison on aggravated robbery and aggravated burglary charges..."

      Actually I have worked for such a boss, and dealt with the situation professionally. I warned him of the action he wanted to take, he wanted to anyway, and so I went to his boss, who wasn't a "dangerous flaming asshole". Problem solved.

    8. Re:Jeeezzzzzussss by Ossifer · · Score: 1

      No, even if you don't believe things the city buys for itself somehow don't belong to the city, but to the workers who are tasked to use them, Childs was one admin among many. He's not being "railroaded", but he dug his own grave. It will only affect you if you take similar illegal actions.

    9. Re:Jeeezzzzzussss by db32 · · Score: 1

      " stemming from an incident that occurred when he was a teenager." is the end of that sentence by the way.

      Good for you that he wasn't the top of the chain and you had someone higher to appeal to. It certainly makes things easier. I have also been lucky enough to be in the situation where the next two steps up were colluding and the third step up totally bought their nonsense despite 20+ people trying to raise the problem to him.

      Also...just in case you missed it before going on the rant, you should probably go look up what devil's advocate actually means because I specifically said that at the beginning of my post.

      --
      The only change I can believe in is what I find in my couch cushions.
    10. Re:Jeeezzzzzussss by Ossifer · · Score: 1

      There's usually someone higher up that will listen: ..., CEO, chairman of the board, investors. If you really feel the warning is so needed. If you chain of command is colluding against the good of the company, you MUST report it to the higher authority.

      And, yes, I know what "devil's advocate" means--apparently this devil's advocate is a raving lunatic.

    11. Re:Jeeezzzzzussss by Fulcrum+of+Evil · · Score: 1

      I didn't say that he owned the thing, just that it was his network to run, and he did with management's blessing for years. He wasn't one admin among many, he was the guy, with a bunch of other admins who broke things more than they fixed them. And yes, he is being railroaded - what do you call $5M bond for a sysadmin, firing someone, then demanding passwords at a police station with unknown parties present, and charging him with doing the things that he did as part of his duties. Again, what illegal thing did Childs do?

      --
      "We returned the General to El Salvador, or maybe Guatemala, it's difficult to tell from 10,000 feet"
    12. Re:Jeeezzzzzussss by Ossifer · · Score: 1

      Bond is up to the judge, upon consultation with prosecutor and defense attorneys. If you think bail is too high, get a better lawyer. Are you seriously suggesting that sysadmins as a class of people should have lower bail amounts in general vs. the general public? This bit about him being the only useful admin, is quite obviously his perception that he has successfully propagated. Is it the truth that he was the only admin in the whole city who wasn't incompetent?

      What illegal things did Childs do? Well, read the indictment and wait for the jury to answer that. The defense has not been able to convince a judge that the charges should be thrown out...

    13. Re:Jeeezzzzzussss by Fulcrum+of+Evil · · Score: 1

      Are you seriously suggesting that sysadmins as a class of people should have lower bail amounts in general vs. the general public?

      Are you seriously suggesting that the bail is remotely justified?

      Is it the truth that he was the only admin in the whole city who wasn't incompetent?

      Just how many people do you think are competent to run a network the size of SF? Now, how many will be willing to work for the city of SF? I think it's possible, even plausible that he is the only one who knows the score, or at best on of very few.

      Well, read the indictment and wait for the jury to answer that. The defense has not been able to convince a judge that the charges should be thrown out...

      you missed the part where they threw out the big charge, and most of the other charges are for things that Childs had as part of his job. Seriously, modems?

      --
      "We returned the General to El Salvador, or maybe Guatemala, it's difficult to tell from 10,000 feet"
  15. Someone needs a geography lesson ... by tomhudson · · Score: 4, Insightful

    FTFA:

    'If Childs is convicted on the modem charges, then just about every network administrator in the world could be charged with the same "crime,"' Venezia writes

    Even if convicted, the Childs case doesn't establish jurisprudence for 95% of the world.

    1. Re:Someone needs a geography lesson ... by ElectricTurtle · · Score: 1, Insightful

      Yeah, too bad it's in the 5% that matters, given that CA has pretty much the highest tech density in the world, sets all the trends, and it's also home to ICANN.

      --
      I support the Slashcott and will not be reading or commenting from 2/10/14 to 2/17/14. Beta is steaming pile of dog shit
    2. Re:Someone needs a geography lesson ... by Anonymous Coward · · Score: 0

      and every country out there seems to have a sexy relationship with adopting all of the US's failed policies like the DMCA

      OR

      that the US just assumes that the whole world is under its jusisdiction

    3. Re:Someone needs a geography lesson ... by Peyna · · Score: 1

      Thankfully, trial courts don't make any precedent at all.

      --
      What?
    4. Re:Someone needs a geography lesson ... by Anonymous Coward · · Score: 1, Insightful

      Even if convicted, the Childs case doesn't establish jurisprudence for 95% of the world.

      Standard IANAL disclaimer here.

      Even though there is no legal hold over say, China, it will establish precedence. So the legislatures over ther can then point to the Childs case as a basis for their laws

  16. bullshit by Anonymous Coward · · Score: 0

    those guys should have learned to use a computer then. I would hire that guy back and fire the rest,...

  17. Who's in charge? by __aaaehb3101 · · Score: 5, Informative

    While I haven't been in this specific situation(ie. jail), I have been in a similar situation.

    At a previous employer(this is one of the reasons I no longer work there) my supervisor demanded that I give him all my passwords. I asked him why he needed them I could give him any specific access he needed on demand.

    When I was hired I was given a number of NDAs to sign one of them specifically covered the process I used to connect to various remote systems, and the passwords I used. My supervisor(with no IT or technical background of course) continued with his demands for all my passwords, for days. After repeatedly trying to explain that even if I was to give him my passwords, without understanding how you use various access levels to accomplish tasks, he could end up causing massive problems.

    In an attempt to meet these demands, I asked for a signed release from the specific NDA that covered my passwords and process. He informed me that he did not have that authority, so I asked him how I could honour my NDA if I gave him information I was not permitted to give anyone. BTW my supervisor did have his own passwords, and had a process to have new ones created.

    Long story short, I refused and then a few days later I arranged to transfer to a different department. With this case as a guide I would legally have been wrong no matter what I did, glad I'm out of IT right now.
    (If anyone cares, I later found out the reason my supervisor wanted my passwords was that his id/passwords had been burned through lack of use and using the wrong passwords. And he did not want his supervisor to find out he had had no access for weeks. His supervisor would have been notified if anyone requested a password reset or new ID.)

    1. Re:Who's in charge? by bullettech · · Score: 1

      it is three faster's

    2. Re:Who's in charge? by Sycraft-fu · · Score: 1

      Well in your case, you'd be covered. The problem here isn't specifically with him not handing over his personal passwords, the problem is that he's locking people out by doing so. Now while it is a poor system where only one guy has top access, that doesn't change anything. If your passwords don't stop the lawful owners from getting at their stuff, then there's no problem. The problem is when your passwords are the only way to get at it. Then if you refuse to hand it over, you can be in trouble.

      It would be the difference between a user account and an enable account on a switch. If everyone has their own user account then there is no reason for them to need yours. They can take it away from you, if they don't want you to have it, but they can't demand that they need it. However there's only one enable password. So suppose you are the only person who knows it, and you refuse to give it up. Now you've locked them out of their own switches. It isn't that they want your password, it is that they want the password to the privileged level of the switch. You can't refuse them access to their own hardware. You wouldn't necessarily have to give them your password, but you'd have to change it to one that you did give them.

      Also in the case of any larger organization, the way it gets handled is decided higher up. If a supervisor demands something they shouldn't have access to, you take it up the chain. In large organizations it is probably HR that you'd talk to. You say "My supervisor is demanding my passwords, however company policy states I am not to give them out, what am I supposed to do?" They'll decide. At that point you are covered. If it is a decision you are worried about, you get it in writing. Either way, doesn't matter. If they say "Yep, you have to hand over your passwords," ok fine, you do that. If problems come up because of that you simply point to the decision and say "I am doing as I was ordered."

      The problem in this case is it sounds like he decided to be a petulant jerk about it. They wanted to axe him, but couldn't because he was the only guy that knew the system. Ok well fair enough. So the decide that he shouldn't the the only one with the passwords. Maybe they were going to try and hire someone else, maybe just hedging their bets. He said no, and wouldn't give them the passwords. Things finally got escalated to the top, the COO of IT said "Hand them over" along with threat of arrest if he didn't. So he gave them fake passwords. Thus they made good on the arrest threat.

      Basically he was being a dick. Maybe he really thought it was the right thing, but he was still being a dick about it. Well, they've decided to be dicks in return, and being the government, they've got a lot of ability and practice in that arena. You don't want to get in to a "Who's the biggest asshole," contest with someone who is willing and able to be a bigger asshole than you.

      Regardless of what happens with the charges, the moral for admins is simple: You do what the powers that be tell you with regards to access. If they demand access, you give them access. You don't have the right to say no. If your supervisor, or someone else who probably shouldn't have access is making the demand, go to the powers that be and see what to do. However whatever their decision is, you abide by it. Make recommendations, tell them why it isn't a good idea, but in then end do what they say.

    3. Re:Who's in charge? by Eric+in+SF · · Score: 1

      Educate me on how you can sign an NDA with a granularity that excludes your direct supervisor from learning something you know?

    4. Re:Who's in charge? by Ossifer · · Score: 0, Troll

      Lucky you didn't work in my IT department. I would have fired you on day one.

      As an employee it's your responsibility to alert/inform your supervisor of the risks of his/her requests/demands. That's commendable, but it's your duty to accept what you feel might be a bad decision, and to follow orders.

    5. Re:Who's in charge? by PCM2 · · Score: 2, Insightful

      Yikes. Should I feel fortunate that I've never had a civilian job that required me to "follow orders"? Or am I merely to infer that you are an asshole boss?

      --
      Breakfast served all day!
    6. Re:Who's in charge? by Anonymous Coward · · Score: 1, Insightful

      He was following orders - the NDA he signed, the text hardcopy, stating that he wasn't to give out his password.

      Perhaps you should fire yourself for contravening orders, even though you feel that they may be bad.

    7. Re:Who's in charge? by Anonymous Coward · · Score: 1, Insightful

      Bull. You aren't required to accept bad decisions from a supervisor when they violate company policy.

    8. Re:Who's in charge? by Anonymous Coward · · Score: 0

      You seem to have forgotten the part whereby giving his supervisor the passwords would have violated his contract with the company (the NDA).

      If you tried firing me for something like that, there's a very good chance that as the new owner of the company after the wrongful termination suit, I'd fire you. :)

    9. Re:Who's in charge? by LoveMuscle · · Score: 2, Insightful

      I can't tell if your joking or if you're a douche.

      He was following orders. He had a legal agreement with the company not to share his passwords with ANYONE which presumably included his boss. What his boss was asking contradicted that agreement. Since his boss admitted that he didn't have the authority to override that agreement, what he did was 100% correct, even if it did cause his loser boss heart burn.

      Had he been fired for that he would have had excellent cause for a big wrongful termination suit. You can't ask an employee to do something (don't share their passwords), then fire them for doing it (not sharing their passwords) without consequences.

    10. Re:Who's in charge? by Fulcrum+of+Evil · · Score: 1

      You didn't read the whole post, did you? The GP had an NDA which forbade him from divulging passwords to anyone, offered any access the super needed and asked for clarification. Sounds like a stand up guy to me.

      --
      "We returned the General to El Salvador, or maybe Guatemala, it's difficult to tell from 10,000 feet"
    11. Re:Who's in charge? by Anonymous Coward · · Score: 0

      If the company made a specific contract with a particular employee(NDA) what right do you, a nominal superior of that worker, who is just another employee of the company think you can direct a lower level employee to break a contract, and/or breach company policy. You only follow order if, it is not illegal, and the order is within the right of the boss to give. if we speak of Duty, Duty guides us in our interpretation of orders recieved. But orders recieved are NOT automaticly our duty to do.

    12. Re:Who's in charge? by Anonymous Coward · · Score: 0

      You do realize that the NDA constitutes company computer security policy. So by giving the password when he's not supposed to, he would be committing a felony in this brave new world we live in. If you don't realize that, fine. If you do realize that, but still stand by your opinion, I hope I never, ever get stuck working for you.

    13. Re:Who's in charge? by hughk · · Score: 1

      When I have passwords, I have a document that says that they are my personal responsibility. If we are talking about a non-personal id such as the management password on a router then when I share it with someone, we have shared responsibility until they change it. That is, they can screw things up and claim actually it was me sabotaging the system. This is why organisations that care about security have lots of special procedures around password disclosure.

      --
      See my journal, I write things there
    14. Re:Who's in charge? by julesh · · Score: 1

      He was following orders. He had a legal agreement with the company not to share his passwords with ANYONE which presumably included his boss. What his boss was asking contradicted that agreement.

      Probably not, no. Unless the NDA was very unusual, it only prevents disclosure to third parties. A representative of his employer is not a third party. The way it looks to me misinterpreted its scope, and tried to apply it in a situation it wasn't intended to cover.

    15. Re:Who's in charge? by __aaaehb3101 · · Score: 1

      ... but it's your duty to accept what you feel might be a bad decision, and to follow orders.

      That's right I do have to follow orders, that's exactly what I did. I followed the written order(the NDA) that I signed not to give my passwords to anyone. This left a clear audit trail showing everything I had done.

      And BTW I burned all my access passwords as I was required to do by the same NDA when my transfer was approved.

    16. Re:Who's in charge? by __aaaehb3101 · · Score: 1

      Educate me on how you can sign an NDA with a granularity that excludes your direct supervisor from learning something you know?

      That's just it, my supervisor could look at or change my IDs and passwords anytime he felt justified in doing so, but it would leave an audit trail. And as I stated above my supervisor had burned most of his own IDs/password by a combination of not using them and entering the wrong password too many times. My supervisor did not want his supervisor to find out, and my supervisor thought that by using my access he could get around the audit trail.

      The NDA specifically stated that I was not to give my ID/passwords to anyone unless directed to do so by court of law. I did not write the NDA, lawyers did. I just signed the NDA and followed it.

    17. Re:Who's in charge? by Peter+Simpson · · Score: 1

      So, you'd give your passwords to your supervisor upon request.

      You do realize that anything done using your passwords would come back on you? Then, you're in the unenviable position of explaining why you, in violation of the NDA you signed, gave your passwords to your supervisor, who promptly responds "I never asked him for his passwords" (to save his own ass).

    18. Re:Who's in charge? by cgenman · · Score: 1

      Actually, no. An employee's first responsibility is to the law. Their second responsibility is to follow corporate policy. Their *third* responsibility is to follow their supervisor's requests.

      In this case, their supervisor's request violated both the first and second responsibilities, which both have priority. There were proper policies in place at the company which would have allowed the supervisor access they needed without compromising security.

      This is especially true in financial or IT sections of a company, where corporate policy is specifically structured to deny access to corporate resources, thereby preventing misusage.

      What company do you work at, so that we can avoid it?

    19. Re:Who's in charge? by Anonymous Coward · · Score: 0

      This is absolutely correct. An Admin should never give anyone...anyone their own passwords for their own account. Doing so would enable that person to wreak all kinds of havoc that could then only be traced back to the Admin themself. If the manager had asked to have his account(s) granted admin access and had the authority to do so, then fine. If he had asked the Admin to unlock his account or reset the password for him, fine. However, giving out the passwords for your own account(s) is like just handing over your identity to someone else, with all the risk that it carries.

      It is my understanding that the passwords in the Childs' case were local admin passwords for the network equipment, however, and not a username/password tied to a particular user such as Childs himself. In this case, they should have been kept on file, not in his head and he should have been using a username/password for himself to do any administration. Buy a TACACS or RADIUS server for goodness sake!

    20. Re:Who's in charge? by StikyPad · · Score: 1

      While I haven't been in this specific situation(ie. jail), I have been in a similar situation.

      Gay porn?

    21. Re:Who's in charge? by Cederic · · Score: 1

      Interesting. I've signed NDAs in the past that prevent me from discussing my work with my boss.

      FFS, they explicitly stated that other employees in the same company are excluded from the information.

      Obviously I'm in the habit managing my boss well enough that this sort of thing never causes me problems anyway..

    22. Re:Who's in charge? by Cederic · · Score: 1

      Lucky you didn't work in my IT department. I would have fired you on day one.

      You'd also be facing a wrongful dismissal tribunal, no doubt accompanied by serious discussions with HR and your own managers.

      You can't fire people for obeying their contract, especially for specifically adhering to NDAs (which go beyond general employment contracts).

      Shit, you'll be telling us you'd fire someone for refusing to hack a competitor's systems next..

    23. Re:Who's in charge? by Ossifer · · Score: 1

      that's crap -- we all know the OP was BS'ing about an NDA preventing him from providing passwords to his boss.

    24. Re:Who's in charge? by Cederic · · Score: 1

      Frankly nobody in my company has the authority to ask for my password. Anybody with the authority to access resources I have access to also has the authority to request either their own access, or an administrative override on my access (i.e. admin changing my password).

      If my boss wants my password he wont get it.

      If my boss wants information I have signed an NDA for, he wont get it unless the person with whom I signed the NDA gives me authorisation to share that information.

      Maybe I work in organisations with more complex hierarchies than you do.

    25. Re:Who's in charge? by __aaaehb3101 · · Score: 1

      Correct If I was quoting Hunter S. Thompson. I was quoting a line from the book The Last Dancer by Daniel Keys Moran. The older version of slashdot allowed longer sigs. I didn't noticed mine had become truncated until now.

    26. Re:Who's in charge? by bullettech · · Score: 1

      I was thinking of the speedfreaks myself having read all of daniel keys moran's books

    27. Re:Who's in charge? by Anonymous Coward · · Score: 0

      Duty? Orders? WTF?!

      Where I work sharing passwords is violation of Acceptable Use Policy. Exceptions are specifically listed, securely documented and have procedures associated with them.

      My boss CANNOT ask for my password for anything. Why in hell would he need it? If he needs access he already has HIS OWN.

      This is called accountability and allows auditing and many other processes to occur.

      So. You're fired.

    28. Re:Who's in charge? by Anonymous Coward · · Score: 0

      Soo.. Douche it is then.

    29. Re:Who's in charge? by Ossifer · · Score: 1

      Wow, you're impressive.

    30. Re:Who's in charge? by Anonymous Coward · · Score: 0

      Well, I've never signed an NDA, but I'm sure you just use a pen and sign it. Where I work there are rules of conduct we must agree to. One of the rules is you must never share your passwords with anyone. Not IT. Not management. Of course this doesn't apply to system password, like this bonehead was trying to keep from the rightful owners of the system.

  18. Free Terry Childs! by zobier · · Score: 1

    Free Terry Childs!

    --
    Me lost me cookie at the disco.
    1. Re:Free Terry Childs! by Amazing+Quantum+Man · · Score: 2, Funny

      Free Terry Childs with purchase!

      --
      Fascism starts when the efficiency of the government becomes more important than the rights of the people.
    2. Re:Free Terry Childs! by liquidsin · · Score: 2, Funny

      *Free Terry Childs must be of equal or lesser value to that of purchased Terry Childs. Must be a California resident to claim prize. Valid only while supplies last.

      --
      do not read this line twice.
    3. Re:Free Terry Childs! by PiSkyHi · · Score: 1

      Buy 2, get 1!

    4. Re:Free Terry Childs! by Anonymous Coward · · Score: 0

      2in1 ... lulz

    5. Re:Free Terry Childs! by FearForWings · · Score: 1

      This product is known by the State of California to cause cancer...or that at least is one explanations for how the politicians of SF reacted.

      --
      I don't know about angles, but it's fear that gives men wings. -Max Payne
    6. Re:Free Terry Childs! by andy_t_roo · · Score: 2, Funny

      "Warning: This Product Attracts Every Other Piece of Matter in the Universe, Including the Products of Other Manufacturers, with a Force Proportional to the Product of the Masses and Inversely Proportional to the Distance Between Them."

    7. Re:Free Terry Childs! by Pfhorrest · · Score: 1

      Free Tibet. Limit one per customer. While supplies last. Offer void in China.

      --
      -Forrest Cameranesi, Geek of all Trades
      "I am Sam. Sam I am. I do not like trolls, flames, or spam."
    8. Re:Free Terry Childs! by grimarr · · Score: 1

      It should be "inversely proportional to the square of the distance between them."

    9. Re:Free Terry Childs! by spazdor · · Score: 1

      Inversely Proportional to the square of the Distance Between Them.

      /pedant

      --
      DRM: Terminator crops for your mind!
    10. Re:Free Terry Childs! by Anonymous Coward · · Score: 0

      Wow.. aside from being wrong, many of the warnings on that page are remarkably unfunny.

  19. Analysis by GiMP · · Score: 4, Informative

    First, I'll remind everyone that the code 502 in question is only applicable in California.

    The phrasing of the law at the root of this discussion is, "Knowingly and without permission provides or assists in providing a means of accessing a computer, computer system, or computer network in violation of this section."

    What I imagine the prosecution will argue is that Terry Childs had no right or explicit permission to configure remote access. The defense will likely counter with the fact that as their Systems Administrator he had implied permission as part of his job's duties. Depending on the outcome, this might trigger Systems Administrators to seek contracts shielding themselves from such risks, or seeking express, written permission for everything they do. Of course, considering how badly companies abuse their employees, and how many employees are naive enough to not protect themselves legally, it will likely just be ignored and we'll see more cases like this.

    1. Re:Analysis by GiMP · · Score: 4, Interesting

      The other possible outcome is that they'll say that he had permission to configure access, but when that privilege was renounced, that he should have removed remote access... in which case, I question how they would ever expect to let anyone go if they would have to go through such trouble each and every time?

      The truth is that often enough, companies don't change passwords, or at least not all of them, when a Systems Administrator leaves. Even in very small shops, it is very difficult to keep track of all the places passwords might be hiding, where remote access might left enabled. For other employees, it isn't as tough, they might have access to one or two systems, but for an SA? You might never be able to lock them out completely, and simply rely on trust, morals, and the law. For instance, an SA might have set up a router just to test new IOS releases on, test, etc. Nobody else would have used it other than that SA, and nobody else would have known of it of it or thought of it. Such a router could be on the network for years without being noticed. Such issues will only become more apparent with "VM Sprawl", where you might have thousands of virtual machines. Without strict auditing, and even with it, you'll easily miss a stray virtual machine floating out there.

      The point is, once you give someone access to your network and your systems, to the level that a CTO, Senior Systems Administrator, or Network Administrator might have access, you can't ever be certain of locking them out of your systems, and you shouldn't be able to punish them for not remembering to lock themselves out -- only because it is too easy to make such mistakes or to have such oversight.

      Personally, whenever I've left a job, I've done my best to forget everything possible that was specific about their configuration. I'd rather not remember the IP addresses of their machines, their passwords, or anything else -- there is too much liability.

    2. Re:Analysis by scientus · · Score: 1

      The other possible outcome is that they'll say that he had permission to configure access, but when that privilege was renounced, that he should have removed remote access... in which case, I question how they would ever expect to let anyone go if they would have to go through such trouble each and every time?

      Thats called an ex-post facto law. He cant be guilty of the statute if he had the authority to set up the system before, there has to be a specific law stating that when his duty ends he must relinquish, and under what pretenses.

    3. Re:Analysis by pavon · · Score: 2, Informative

      That is the second time I have seen ex-post facto used this way in this thread. I'm not a lawyer, but I have always understood ex-post facto to refer to laws that are enacted after an action occurs that changes the punishment for that action. That hasn't happened here - AFAIK the laws were already on the books when he setup the routers.

    4. Re:Analysis by makomk · · Score: 1

      The other possible outcome is that they'll say that he had permission to configure access, but when that privilege was renounced, that he should have removed remote access... in which case, I question how they would ever expect to let anyone go if they would have to go through such trouble each and every time?

      The trouble with that is that revoking his access would require accessing the system... which he was no longer authorised to do at that point, even though he could still do it. In fact, if he had done so, I think that would be grounds for prosecution under most computer crime laws. (IANAL, though.)

    5. Re:Analysis by phorm · · Score: 1

      but when that privilege was renounced, that he should have removed remote access.

      How? He was no longer authorized to administrate the network. This would mean he likely was also not authorized to make the changes required to lock himself out.

      When employees with sensitive information leave (voluntarily or no), it's generally best-practice to have those left behind ensure that their access is revoked as completely and quickly as possible, with the exception of certain situations (an employee leaves no good terms but continues to provide occasional support remotely, etc).

    6. Re:Analysis by Anonymous Coward · · Score: 0

      So they're using the wrong term, but the point stands.

      At the time he set things up, he had the authority to do that.

      You cannot retroactively rescind that authority he had.

      As far as I can tell from the story, this guy has an asshole manager who has fucked up his life. With a decent defence lawyer the guy will be found not guilty, and set free. Hopefully he will be able to sue for: (a) loss of earnings, (b) loss of liberty, (c) mental and medical trauma from being imprisoned, and I'm sure the lawyer will come up with more.

      The guy himself might be a twat, but that's not the point here.

    7. Re:Analysis by Tarsir · · Score: 1

      The point is, once you give someone access to your network and your systems, to the level that a CTO, Senior Systems Administrator, or Network Administrator might have access, you can't ever be certain of locking them out of your systems...

      So Firewall has a plausible plot after all. Who knew? :P

    8. Re:Analysis by GiMP · · Score: 1

      I'm not arguing it makes sense, only that it might be the prosecution's case. Of course, there are two possible scenarios, one is where someone leaves voluntarily, and the other is when they are removed from the position. Clearly, when someone is removed, they don't have the opportunity to remove their access, legally.

      What is apparent in this whole case is the ineptitude of the city. From what I've read, it seems the city never made sure that anyone else had vital information, they fired him prior to getting that information, and Terry Childs saw no point in providing free assistance and information to an entity that let him go. In fact, as far as I'm concerned, according to my understanding of the case, the only thing that might possibly be illegal here, as far as Terry Childs is concerned, is that he still retained and remembered those passwords after he left their employment!

    9. Re:Analysis by phorm · · Score: 1

      Agreed. It seems that however unreasonable this guy was in the beginning, his incarceration and punishment to-date have already greatly exceeded a reasonable amount.

      Scary to see what they can do to you if the really want to, because I can't say that - had he complied more - they wouldn't have found another way to screw him over just as much or more.

  20. welcome to slashdot by circletimessquare · · Score: 1, Insightful

    where the most pedestrian news is given the most ridiculous fear-driven spin, made front page in breathless write up, and a bunch of yammering legal ignorants wlll ape right along

    and then these same people will ridicule stereotypes outside their domain who supposedly fall for propaganda and hysteria all the time

    take a look in the mirror friend

    no, slashdot, this case does not set the precedent you believe it does

    CONTEXT. its a magical concept. consider it some time

    --
    intellectual property law is philosophically incoherent. it is your moral duty to ignore it or sabotage it
    1. Re:welcome to slashdot by Anonymous Coward · · Score: 1, Insightful

      Context: This guy has already been in jail for seven months for what looks like normal sysadmin work.

    2. Re:welcome to slashdot by ozphx · · Score: 1

      Context: The guy acted like a dick, and generally a simple guide to law is: Don't be a dick.

      --
      3laws: No freebies, no backsies, GTFO.
    3. Re:welcome to slashdot by Cederic · · Score: 1

      The law is such an utter cock at times that you're fucked whether you obey it to the letter, obey it in intent or just try and obey part of it because it's contradictory.

      In this situation it appears he obeyed the law and is getting fucked over anyway. Had he acted any differently he would have broken multiple other laws.

      Not much of a choice is it.

    4. Re:welcome to slashdot by ozphx · · Score: 1

      "I will speak only to the Mayor" when you clearly have mental problems is pretty ridiculous. Even if the Mayor had time to see him, I'm certain his minders wouldn't allow it.

      Its an egotistic stunt by a self-important fucktard - on the level of Stallman trying to get an audience with the French president after being told to fuck off repeatedly.

      --
      3laws: No freebies, no backsies, GTFO.
    5. Re:welcome to slashdot by Cederic · · Score: 1

      I'm not suggesting that Childs isn't a self-important fucktard. I have no idea, although the evidence tends to support your theory.

      That doesn't mean he's not correct in refusing to break the law by divulging computer access codes to unauthorised people. You get in serious trouble for that sort of shit.

    6. Re:welcome to slashdot by ozphx · · Score: 1

      Yeah... TBH if I was in that situation I'd probably just give the nice police officer the codes, tell him hes unauthorised to look at them, and then wash my hands of the whole thing.

      If anyone complains I'd scream coersion / brutality / threats against my person / bestiality, whatever it took :P

      --
      3laws: No freebies, no backsies, GTFO.
  21. Hysterical overreaction by Stormie · · Score: 1

    I posted this in response to the Groklaw Summarizes the Lori Drew Verdict article, but it's 100% valid here as well:

    Look, the fact is, if The Man wants to get you, The Man will get you. It doesn't matter what the laws are, exactly - they'll find something to hit you with.

    That was true before the Lori Drew trial (Terry Childs charges), and it's true now. The precedents set by this case in no way make being on the internet (owning a modem) one bit more "risky". If you don't do anything to bring down the wrath of The Man, you'll be fine. And if you do, you're screwed, online or off.

    1. Re:Hysterical overreaction by JohnFluxx · · Score: 1

      And complaining about that is a hysterical overreaction? WTF?

    2. Re:Hysterical overreaction by Stormie · · Score: 1

      Complaining that this case "puts all admins in danger", or that you can now be thrown in jail for owning a modem, is a hysterical overreaction.

    3. Re:Hysterical overreaction by dbIII · · Score: 1
      IMHO we're seeing Terry Childs in the hotseat here and not Nancy Hastings whose hard drive was taken away for no legitimate work purpose I can see becuase Terry was the one the caught the new security person exceeding their authority and kicked up a fuss about it. He is being sacked for taking photos as evidence to present to management, but now that has turned into "intimidation".

      If I saw someone acting so suspiciously I would also confront them. If it isn't your job to pull apart computers full of confidential information I would object unless the people authorised to see that information agree. If the new "network security" person starts taking desktop hard drives to poke about on I would definitely take it up with their superiors.

      The incredible overreaction makes me think somebody is being overprotective of an upset Jeana Pieralde, IMHO due to having to cover for appointing somebody that is acting innappropriately to show they did make a good choice, or due to some personal attachment and the want the young lady to owe them a favour. Office politics can be incredibly sordid and banal - I really do think this guy went to jail so that some sleazy arsehole can improve his chances to get into Jeana Pieralde's pants, or perhaps he was already there and she got the promotion (and the dismissal of Nancy Hastings who would have been senior) as a reward.

      It amazes me that this has got as far as criminal action. There are often bizzare overreactions when computers are involved in what would otherwise be fairly trivial situations.

    4. Re:Hysterical overreaction by JohnFluxx · · Score: 1

      Not really. (Ab)using laws sets precedents. If the guy ends up going to jail for just owning a modem, then how is it an over reaction to say that you can be thrown in jail for owning a modem?

    5. Re:Hysterical overreaction by Stormie · · Score: 1

      The overreaction is in believing that your situation is in any way different today to how it was yesterday, BEFORE this guy got thrown in jail for owning a modem.

    6. Re:Hysterical overreaction by JohnFluxx · · Score: 1

      Of course it's different - what do you think 'setting a precedence' means?

    7. Re:Hysterical overreaction by Stormie · · Score: 1

      If you read my first post again, you'll see that I think it means very little.

    8. Re:Hysterical overreaction by AK+Marc · · Score: 1

      That was true before the Lori Drew trial (Terry Childs charges), and it's true now.

      But I think that Lori Drew was guilty of breaking the law. Not the laws she was charged with, but she did break the law. She lied in order to knowingly cause actual harm to a minor, and due to that deliberate actual harm caused, the minor died. That's child abuse, harassment, stalking, manslaughter (possibly murder, since she was intending to cause harm, but not kill). But to charge her with illegal access to a computer system is silly. The DA wanted to put her in jail as an example and figured that they could get an easy conviction on the computer charges, rather than the tougher battle in charging her for the crimes she actually committed.

      This guy pissed off some higher ups by interrupting a computer "audit" (the first audit I've ever heard of that was undocumented until after it happened) by someone that made a huge stink about it. Then he was canned. Then they asked him to honor the employee/employer relationship they already ended. There's no harm caused to anyone in that. The worst that should have happened is the city should have sued him in civil court to get back the passwords (and likely, he would have ended up in jail if he was ordered to give them up in court and refused). But to throw him in jail *before* any actual legal proceedings is absurd. To hold him this long is illegal (not that he'll win that case, if he files it) and they never once "asked nicely" for anything from him. They treated him like a criminal since before he was fired, and he responded by clamming up. If his employer didn't run the police and the courts, I expect he'd never have seen the inside of a jail cell, and this is about government corruption in all branches as much as anything else. The Governator should immediately pardon him of all crimes he did or may have committed while working for the city or related to his termination. Even if he did everything they assert and did it with bad intentions, he still caused no downtime and cost them no money (excepting their over-reaction) and shouldn't have been in jail this long even if convicted.

    9. Re:Hysterical overreaction by Cederic · · Score: 1

      Thank you for posting the most concise summary of the situation as I see it, addressing the issues as I understand them.

      It may be that there is information we are unaware of, but there is a scary amount of blinkered naivity, prejudice and ignorance being posted elsewhere on this topic so it's nice to see someone describing it all so sensibly.

  22. The citys also runs the jail system so that speeds by Joe+The+Dragon · · Score: 1

    The citys also runs the jail system so that speeds that part up out side of a city things likely do not go that fast.

  23. Slacker!!(insert severe sarcasm here-It's a joke!) by rts008 · · Score: 1

    Then you will never truly achieve 'BOFH' status, Grasshopper.

    Open your mind, and the lusers files! It can be beau coup fun!

    Transcend your permissions, and make backups of your PHB's pR0n folder-blackmail can be sooo fun!

    Become One with the database, there is more exploitable info there than you have time to exploit!

    Achieve One-ness with the Network, and your C*O's password-the benefits can be multi-million$'s if played right

    Go forth in the world, and achieve greatness! Be Bold!, Be Brutal!, Be Unforgiving(log everything), and Exploit it!....It is the American(USA) Way[tm].

    --
    Down With Slashdot BETA!!! I've been around the corner and seen the oliphant; you can only abuse me from your perspecti
  24. Re:This is bad? by Anonymous Coward · · Score: 0

    Paul Venezia is not a lawyer, but it sure looks like he stayed at Holiday Inn Express recently.

    Every sysadmin is guilty of having modems? Is he high? Which sane sysadmin plugs in unauthorized modems into the production network and then actively tries to hide them?

  25. The passwords were the property of the city by DJRumpy · · Score: 1

    It seems to me that he has no legal standing. IANAL, but if his supervisor tells him to give them the passwords, it is not his place to decide who it is 'safe' to give them to and who is not safe. That is his employers decision.

    His colored past aside, he could be a very upstanding citizen and he would still be completely in the wrong for not releasing the information that his employer tells him to. He gained that information in the employee of the city and that information is the city's property.

    In my opinion, he has some sort of conflict with his employer and he's using the passwords to leverage grief against them, not trying to protect the fiber network.

    That said, the charges about the modems seem a bit far fetched as it sounds like they were there for perfectly legitimate reasons. Hopefully he has documentation to back his claims up that they were job related. I don't think they'll be to forgiving given his past record.

    1. Re:The passwords were the property of the city by hughk · · Score: 1

      I have signed a piece of paper which forbids me revealing my passwords to anyone. My boss can never demand my password. If I get run over by a bus or whatever my boss can request a new password for my account.

      Before my boss gets that password someone will check to see if access to my user if plus his own will give him the ability to override validation checks by impersonating me.

      --
      See my journal, I write things there
    2. Re:The passwords were the property of the city by julesh · · Score: 1

      It seems to me that he has no legal standing. IANAL, but if his supervisor tells him to give them the passwords, it is not his place to decide who it is 'safe' to give them to and who is not safe. That is his employers decision.

      Yes, and the fact he did not follow his employer's request gives his employer a right to fire him for gross professional misconduct. Not institute criminal proceedings against him.

    3. Re:The passwords were the property of the city by The_Other_Kelly · · Score: 1

      >It seems to me that he has no legal standing. IANAL, but if his supervisor tells >him to give them the passwords, it is not his place to decide who it is 'safe' >to give them to and who is not safe. That is his employers decision.

      Umm. Actually, they could simply have just fired him when he had first refused.
      And they did fire him, after his refusal to yield the passwords in "open air".

      He was arrested for refusing to supply the passwords, and of being a *potential*
      threat, *after* he had been fired.

      At which point, of course, they were his "ex-supervisors", outside of any
      contractual obligation. Even if the passwords are considered as the cities property (which is a very dodgy concept), we are still talking about contract breach, and a small claims court civil issue.

      Instead of that he got 7 months in the pen. Deeply, deeply unpleasant.

      + Check out the arrest reports and DA complaint.
      + Now look at the actual charges.
      + Ask yourself what the hell a corporate security officer was doing
          removing (or copying) hard drives from network administrators, at night.
      + Note that his colleague, the other network admin, is standing up for him.
      + Be surprised when you find out *he* proposed security policies, including
          dead-drop password safes, but the same management denied him ...

      In all of his actions, he appears to have acted with impeccable professional and personal integrity at IMMENSE personal cost, (he's losing his house).

      His is a principled stand, 7 months in jail on $5M bail for .... *having* a modem!

      For what? What "leverage" does he have? Except the moral high ground!

      Honestly, would you like to work for these managers?
      Would you rate them as "exceeding expectations"?
      Would you trust them with ... anything? Like a cities networks!?

      I'd be happy to have Mr. Childs as a colleague or an employee.

      I wouldn't waste glances on the management of San Fran's. net, since in all
      actions so far, they have demonstrated nothing except that they are mean hearted, small minded, incompetent (beyond belief! they put the IOS config with cleartext passwords into the PUBLIC DOMAIN!!!!) ... bastards.

      But make up your own mind.

      --
      (R)ule in Hell or (S)erve in Heaven [R]?
    4. Re:The passwords were the property of the city by DJRumpy · · Score: 1

      It is not a 'dodgy' concept. It is intellectual property. I wasn't speaking to his prison sentence. I was speaking to his refusal to follow his supervisors instructions. I would immediately fire someone like this.

      As to who would work for those people? I already work for similar people as do most IT staff. They have the technical skill and their mgmt typically does not. You do your best to explain consequences and concepts but in the end, it is their decision, not yours and not his.

      I would have surrendered the passwords as instructed and that would have been the end of it. If things went to hell and a handbasket as a result, they would have had nothing on him. This is where that 'high ground' kind of falls to the wayside considering his criminal record. It's just not believable from a character perspective that he took the moral high ground.

      Do I agree with his sentencing and time spent in prison? I don't know what the penalties are for things like theft, but 7 months doesn't seem all that unusual considering the potential financial impact of the information he carries.

  26. IT laws are in conflict with each other by zerofoo · · Score: 5, Interesting

    I've managed networks for regulated industries like Finance, Banking, and Medical industries. All of these industries have laws regarding access controls and information security.

    SarbOx, GLBA, and HIPAA, all REQUIRE access controls on data and systems. As network admin, I can't know the CEO's password, and he can't know my password. This is essential for creating an audit trail and only allowing access to systems and data based on individual authority.

    Laws that make it a crime to withhold passwords (or access) are in direct conflict with the above mentioned laws. If you leave your job and give your "admin" password to the CEO, you could be violating the above laws since you just gave the CEO a way to rob the company, and cover his/her tracks.

    It's insanity to think that you could be committing a crime by doing your job.

    -ted

    1. Re:IT laws are in conflict with each other by blitziod · · Score: 1

      besides it does not matter. Sharing a password that you know as a result of your employment is wrong. Using it without permission or after employment is wrong. Simply not telling people the passwords is your right( although it might be being a jerk). Analogy: I hire a locksmith to reset the combination to my vault. He knows the combination, he set it. I have a dispute with said locksmith over another matter and tell him i will no longer need his services. Then i lose, forget or whatever the combination. I call him up and ask him. He tells me to get lost and not call him anymore call somebody else. Is he a criminal no. i have a file clerk that uses her own system of filing at my company for years. I fire her. I can't find an important file. I call her up and ask where it is. She tells me to get lost..my tough luck.

      --
      The only way to bust a doper--is when you yourself become a smoker!
    2. Re:IT laws are in conflict with each other by SaDan · · Score: 1

      I've also been in similar situations with regards to oversight and accountability with regards to secure systems.

      I took great pleasure in watching the manager of my department go through every piece of networking equipment and remove my account information the day before I left that company.

      Never accept anyone's password for any reason, and never offer your password up for any reason.

    3. Re:IT laws are in conflict with each other by DigiShaman · · Score: 1

      It's insanity to think that you could be committing a crime by doing your job.

      The world hates the Sysadmin. So it's rather fitting as we are criminals to begin with (in their eyes). I need another line of work away from IT. Too much of a liability these days.

      Now get back to work you Cheeto fingered software pirate e-mail snooping pr0n collector!

      --
      Life is not for the lazy.
    4. Re:IT laws are in conflict with each other by JavaRob · · Score: 1

      The difference here is that his passwords were required to keep the system running. There were no other admin accounts that could be used to maintain the system if he were hit by a bus.

      So it's more like if you hire a locksmith to reset the combo to your safe... and he does, but then says "I'm right around the corner; just ring me up whenever you need to open the safe". Because he won't give you the code.

    5. Re:IT laws are in conflict with each other by JavaRob · · Score: 1

      The important difference here is that he had set up a system where *he* was the only one with the admin access required to maintain it.

      If he had set up multiple accounts with the required access, sure -- the new admin could just wipe out Childs' access when he left, and no one would *need* to ask for his passwords.

      But he didn't create a normal system. He created one with a huge single point of failure, himself.

      Have you ever managed a significant network where only one person had admin access?

    6. Re:IT laws are in conflict with each other by ClosedSource · · Score: 1

      I suspect that he knew exactly what he was doing and now that he's in trouble he's pretending it was a manner of "doing the right thing".

    7. Re:IT laws are in conflict with each other by Cederic · · Score: 1

      Your analogy is flawed.

      To make it more accurate, you would need to hire a locksmith to reset the combo to your safe, and pay him a retainder to open your safe for you any time you asked him to.

      At a future point you refuse to pay him, tell him his services are no longer required, and then get your clumsy mate to ask him for the combination to your safe. Then put him in jail for saying 'your mate is not qualified to open the safe without breaking it'.

      Because frankly if he gives your mate the code he's going to go to jail for conspiracy to rob your safe and/or conspiracy to break your safe.

      Such is the law, such is the situation, and such is the extent of the flaws in your analogy.

    8. Re:IT laws are in conflict with each other by Cederic · · Score: 1

      I suspect you're right. Unfortunately being shit at his job to the point of maliciousness is not illegal.

      Had his employer explicitly demanded that he document his passwords and make them available to the appropriate members of the organisation (city) before sacking him then they'd have an infinitely stronger civil case against him.

      They'd still be on dodgy grounds for criminal prosecution.

      Right now, they have no grounds (that I can see, in my common sense non-legal view of the world) for criminal action against him. Which makes his multi-month sojourn in a secure facility pretty harsh.

      Just because he's a cock of the highest order doesn't make him a criminal and doesn't make it acceptable to lock him up for months without trial.

    9. Re:IT laws are in conflict with each other by JavaRob · · Score: 1

      Do you honestly think Childs would have been risking jail if he'd *given* them the passwords when asked? That's a bit amazing. Even if they'd gone in and fucked everything up, he had a room full of witnesses that he'd given full admin control over to them.

      More importantly, the whole unprofessional paranoid situation should have never happened in the first place.

      I think the legal case against him currently seems dicey, but it's very clear he deserved to be fired. It's incompetence (or malice) to set up any important system with one huge single point of failure and no recovery plan.

    10. Re:IT laws are in conflict with each other by ClosedSource · · Score: 1

      He's not in trouble because he's a jerk, but because he didn't give them the passwords. Sometimes jerks fail to use common sense.

    11. Re:IT laws are in conflict with each other by Douglas+Goodall · · Score: 1
      Thank you. That is one of the few posting I have read that gets to the heart of the matter. Unfortunately, IT is a job a large responsibility and built in conflict. The IT worker is in close contact with all levels of the enterprise. Requests made of them come from hopeful low level employees and powerful high level employers. All want what they want as soon as possible, and usually without any understanding of the big picture. More and more it looks like computer professionals need legal training as well.

      In one project, I was the Software Engineering Director with the responsibility to safeguard the source code. After the release of a product, I quit my job. The next day police arrived and took me into custody. They demanded all copies of the source code and materials in my possession. I was accused of taking the only source code disks. They left me in a cell for a few hours. Then they marched me into my ex-job site in handcuffs where I walked over John Draper's desk and in several seconds located the source disks sitting in plain sight. I was released after signing a piece of paper indicating I had only been administratively detained. I should have declined to sign that paper and hired a lawyer. That is what I get for working with an asshole like John Draper. The software project was Easywriter for the IBM-PC, written for IBM and the employer was Captain Software and Information Unlimited Software (IUS). John Draper couldn't find the disks after a few seconds and started yelling, "Doug stole the code, Doug stole the code..." IUS called the police, and my rights were trampled on. I don't see any way I could have prevented this except maybe by showing better judgement in who I worked for. But any employer can lose their mind and start making accusations at any time, and the average employee does not have the resources to hire qualified representation.

  27. And we have security because.. by Anonymous Coward · · Score: 0

    "Initially Childs refused to hand over administrative passwords to the city's routers, which had been configured to wipe out all configuration information if they were reset. "

    What point would there be to security if one could reset a router and only erase the password.

  28. Puts all admins in danger of... by jafiwam · · Score: 0, Troll

    looking like insufferable, arrogant assholes.

    Look, any way you slice this, Terry Childs held something at ransom or rendered useless that didn't belong to him.

    Period. No fucking more arguments about that. The routers were not in his living room, and therefore NOT HIS.

    The code, hardware, and configuration all belong to his employer. By withholding information about the configuration, he stole from his employer on the way out.

    I don't care if he feels like he was mistreated or they might screw up the network after he left. Maybe if he spent more time not being a shit while he was there, leaving would have been easier. Or, I don't know, acting less like a typical waste of biomass bureaucrat doing nothing but protecting his little fiefdom and doing his job properly.... Making sure the job and one's successors succeed is critical to any IT role (if just for the "hit by a bus" factor) and this guy failed miserably at that.

    Let his dumb ass rot in jail. He fucked himself and he deserves what he is getting. Take his car, computers, and 70th level Wizard away too because he represents the WORST qualities of the computer professional he could possibly be.

    1. Re:Puts all admins in danger of... by ani23 · · Score: 1

      wish I had mod points but I wholeheartedly agree with this statement.

    2. Re:Puts all admins in danger of... by darkmeridian · · Score: 2, Insightful

      The Terry Childs case reminds me of 24. A corrupt government analyst exerts pressure on a techie to give up a password, which is promptly used for illegal activity. Then the innocent techie gets fucked and Jack Bauered. Yeah. Give the password to any boss figure who asks. That cannot go wrong.

      --
      A NYC lawyer blogs. http://www.chuangblog.com/
    3. Re:Puts all admins in danger of... by twostix · · Score: 5, Insightful

      "By withholding information about the configuration, he stole from his employer on the way out."

      I don't know about this Terry Child fellow or anything to do with what he's alleged to have done. But that is one bat-shit insane sentence.

      Are you saying that an individual cannot just quit his or her job and walk out the door? And if they do should rot in jail and be stripped of all possessions? On the basis of a private companies say-so? WTF?? Who the fuck modded this bullshit up??

      They fired him, he walked...but he's forever beholden to them and every employer he's ever worked for because he holds some knowledge about their network?

      What a fucked up world you live in, sorry but you're a little fascist, any individual, from the CEO to the Janitor has every right to leave a position and never look back, if the world implemented your policy we'd all be too terrified to work for anyone! Some HR schmuck wants to fuck with you after you leave, HE DIDNT TELL US SOMETHING WE NEED PUT HIM IN JAIL AND STRIP HIM OF HIS POSSESSIONS! Jafiwam demands it!

      You the only IT person for a small company and want to quit? TO BAD! Don't dare walk out the door, if you do according to Jafiwam the little fascist you deserve to rot in jail and have all your possessions stripped away from you. Oops didn't document what that script does, STEALING! JAIL FOR YOU. Didn't tell them about that Cronjob before you left? STEALING! Didn't document that object properly, didn't let them know about that revision, didn't pass on that message? STEALING, STEALING, STEALING!

      Didn't write a 2000 page manifesto brain dumping every tiny little bit of trivia and knowledge that you have about their business, STEALING!

      The idiocy is truly unbelievable around here sometimes.

    4. Re:Puts all admins in danger of... by mergy · · Score: 1

      Wow - stated quite well. Mod up on this please.

    5. Re:Puts all admins in danger of... by AK+Marc · · Score: 4, Insightful

      Terry Childs held something at ransom or rendered useless that didn't belong to him.

      What was the ransom he demanded? How was a network with zero downtime rendered useless?

      The code, hardware, and configuration all belong to his employer. By withholding information about the configuration, he stole from his employer on the way out.

      They had the configuration. They could pull out the flash card with the configuration on it and put it in a new router and it would work great. Of course, without the passwords, they couldn't log in to see it, change it, or any of that, but that didn't prevent it from being 100% operational, as well as being something that could be backed up, replaced, and all that without problem.

      He fucked himself and he deserves what he is getting.

      He was fired, then after being fired, was asked to fulfill an obligation to an organization he no longer had an obligation to. He may not have been professional. He may have been an ass. But he did nothing illegal, let alone criminal. If they threw people in jail just for being asses, I'd nominate you to be at the front of the line.

    6. Re:Puts all admins in danger of... by u38cg · · Score: 1

      Oh dear me. Childs was in a position of responsibility. That means he had a duty to act responsibly, even when asked not to. If my manager asked me for my password, and I turned it over to her, *I* will have broken the rules and *I* will be in trouble. Given that I can do an awful lot of damage with *my* password, there are good reasons for this.

      --
      [FUCK BETA]
    7. Re:Puts all admins in danger of... by Anonymous Coward · · Score: 0

      What a fascist piece of shit you are. He should rot in jail because he kept his mouth shut and walked away? He didn't do a god damned thing you jack booted monkey.

      Man, am I glad I don't live in your warped world, I would seriously kill myself.

      This man deserves his entire life stripped away because YOU feel he gives a certain profession a bad name? Are you insane? Do you not have a soul? Man, do you take your job too seriously or what? You don't matter to the world bub, you are an IT fucktard. Get over it.

    8. Re:Puts all admins in danger of... by Anonymous Coward · · Score: 0

      Are you saying that an individual cannot just quit his or her job and walk out the door? And if they do should rot in jail and be stripped of all possessions? On the basis of a private companies say-so? WTF?? Who the fuck modded this bullshit up??

      Actually, there's some situations where it makes sense and (I believe) is already implemented:

      - if a doctor walks out the door without telling anyone the status of his latest patients
      - if a consultant walks out off a project the day before a major presentation
      - if a military intelligence analyst (even a civilian employee and hence not a 'deserter') walks off the job without telling anyone the latest status of contacts
      - if an the lead oil drilling engineer on an oil platform jumps on a boat and takes off
      - if an accountant leaves a week before annual reporting
      - if a store manager stores all the cash in a safe that he has chosen to code to, and walks off without telling anyone this code

      You might argue that certain jobs carry with them an expected responsibility for some action to be taken in the event of leaving.

      I also think you are exaggerating - noone has claimed that not documenting a script is the same as stealing. Passwords, however, should have a similar status to physical keys or bank safe codes.

    9. Re:Puts all admins in danger of... by mhs1973 · · Score: 1

      Terry Childs did not render anything useless. By withholding the passwords he rendered morons who didn't know shit about shit useless and they threw a tantrum.

      The problem he has now, is the same problem that any admin with the level morons that he had to deal with has.

      He will not be able to convince any jury of his inocence as only other admins are his peers. And the jury won't be other admins.

      His employers hired consultants who didn't know what to do (save writing invoices) and therefore broke what they didn't understand.
      If said consultants were worth their salt so to say, they would have talked to Childs about his network structure and how things were configured. With this knowledge they could have determined what would happen when they did what they did.

      Not only should compensation be paid to Childs, but the people who accused him should be thrown into prison.

    10. Re:Puts all admins in danger of... by dbcad7 · · Score: 1

      It's about the responsibility given to you when you were hired to do the job.. It would be the same thing if you had keys to the building, company credit cards and cell phone.. If you quit, you would give them all back.. If fired you would be asked for them.. If you quit with the keys to the building, never to return, there would be a cost involved in changing the locks.. If you used your keys to enter the building after quitting there would be criminal charges involved..

      Being fired is not fun.. but relinquishing the responsibility you had is part of being professional.. and giving up that responsibility does not ONLY mean your absence as an employee. Whoever was to take over the responsibilities he had should have been given the passwords, the minute he was told that he would not be working there anymore, just as if he were giving up his key to the building... It's kind of like making a clean break with a girlfreind.. make sure she has ALL her stuff, so you don't have to deal with it anymore.

      --
      waiting for ad.doubleclick.net
    11. Re:Puts all admins in danger of... by tinkerghost · · Score: 1

      Look, any way you slice this, Terry Childs held something at ransom or rendered useless that didn't belong to him.

      Or he was performing his job of maintaining system security by refusing to give up the system root passwords to an unknown number of people listening in on a speakerphone. That's not holding anything for ransom, it's being responsible. He gave the passwords up directly to the mayor - IE no middlemen.

      Making sure the job and one's successors succeed is critical to any IT role (if just for the "hit by a bus" factor) and this guy failed miserably at that.

      Double check the storyline - he brought this up months before the shit hit the fan & was shot down with "their's no one we can spare to learn this shit - take care of it". He was fucking told to be God. Now their whining because he didn't magically make the documentation appear with no help and no time. The story specifically indicates that people assigned to work with him were routinely yanked away to cover other shitstorms.

      Bluntly, his manager tried to fire him & when it failed he sandbagged him with an unreasonable request and has escalated that into criminal proceedings. Yes, in secure environments, verbal requests for passwords are unreasonable. Note that the charges related to not handing over the passwords aren't included in the formal charges being brought against him. That's a fairly good indicator that the DA understands that this is a cluster fuck of egos. The supervisor's ego was bruised when his firing got overturned & he's gone way outside the box to get back at Childs.

      Was Childs following best practices? I would say no since there wasn't a sealed list of the passwords in a vault somewhere. On the other hand, the rest of the city wasn't exactly following best practices either.

    12. Re:Puts all admins in danger of... by jafiwam · · Score: 1

      This all boils down to does the admin have the role of saving the institution from itself or not.

      If the admin has this role, it's tyranny of the one. (The asshole admin syndrome.)

      If the admin does not have this role, it's stupidity of the top.

      Even AS an admin, I would rather let the collection of top managers (who could be educated, or could get other resources) rule over the mid-to-low level asshole that thinks he's protecting something other than his own pride by withholding or not doing shit.

      There were lots and lots of ways to provide passwords after being asked in the conference call that would have been secure. Simply saying "hold on, let me email them to you" to the top guy there (and then doing it) would have mitigated any real responsibility. Childs chose to not just do what they wanted in a more secured CYA way, he chose not to do it at all. That crossed the line into hubris, not responsibility.

      So screw him. Let him rot. He COULD have just said "here they are, oh, by the way, I quit. When your shit is screwed up because you damaged it, let me know and I will work on contract basis for $1k per hour" and then walked with his reputation to find another job. Instead, he chose to fight a stupid battle and now he'll be unhirable a lot of places. Have fun pumping gas moron.

    13. Re:Puts all admins in danger of... by phorm · · Score: 1

      There are lots of cases wherein providing the information requested can get you in a lot of trouble in itself. As mentioned in other threads, there are many companies where the sysadmin-level and supervisory-level passwords are kept segregated, mainly because giving any one person (even your boss) gives too much ability to perpetuate fraud.

      In other situations - and this one may have been more of a concern in this case - it's a case of the blame game. You leave the passwords with somebody who's not supposed to happen and/or is incompetent. They fuck things up royally, and then blame it on a malicious act by you. Blame-my-predecessor is a pretty common game, hence see the fairly popular three envelopes joke. The end result of that could be the same as or worse than how things ended up now, depending on the level of (in)competency of the person who now has access (imagine that they lack enough knowledge to screw things up while royally, but have enough to wipe out or tamper with logs leaving false evidence).

      Sounds like the guy had a bad attitude yes, but it also sounds like that made the perfect excuse for an opportunistic manager to rake him over the coals post-firing.

      My own practice is to keep a secure document with access procedures (passwords/keys/etc), and generally if I leave a company I still provide some support afterwards.

      I've never been canned (although I have been downsized in an understandable situation where a company was going downhill) by wrathful management though, so I'm not sure how that would play out. Even with a list of passwords, there are still VPN's, SSH keys, and many other access levels that would have to be revoked to lock out my accounts properly, but I suppose setting my shell to /bin/false would do well enough in most cases, though there might be 100+ servers to go over in this regard.

    14. Re:Puts all admins in danger of... by AK+Marc · · Score: 1

      Giving up the passwords to "unauthorized" people, even if ordered to do so by someone authorized, is a crime. He should be in jail if he did do what they asked on the conference call.

    15. Re:Puts all admins in danger of... by mdielmann · · Score: 1

      It would be the same thing if you had keys to the building, company credit cards and cell phone.. If you quit, you would give them all back.. If fired you would be asked for them.

      Ah, but the question that Childs asked is, "Who am I authorized to give the keys to?" Should he just give them to Bob the Janitor, or someone who actually has the authority to take them. He clearly had a breach of trust with his supervisor, and possibly the CIO (if that wasn't his supervisor). After the secret audit, and him reacting reasonably to someone unauthorized removing equipment he was responsible for, the expectation that he should relinquish sensitive information to them is laughable. So he picked someone with sufficient authority (although not necessarily qualifications) to hand the information to.
      I don't see what he did wrong. Perhaps he handled it poorly, but that's a different thing altogether.

      --
      Sure I'm paranoid, but am I paranoid enough?
  29. A Moot Point ? by shashark · · Score: 3, Funny

    Count 1: disrupting or denying computer services is moot

    Joey: It's a moo point
    Rachel: You mean a moot point ?
    Joey: No...no, a moo point ... like a cows opinion, doesn't matter ... it's moo.

    1. Re:A Moot Point ? by isorox · · Score: 1

      Slashdot quoting Friends. And being modded up. There's something strange going on...

    2. Re:A Moot Point ? by Joe+the+Lesser · · Score: 1

      Well, you can joke about a train wreck after a certain number of years has passed. Same principle.

      --
      "I only speak the truth"
      Karma: null(Mostly affected by an unassigned variable)
  30. Not necessiarly by Sycraft-fu · · Score: 1

    Just because you are the administrator of something, doesn't mean you can do whatever you like with it, or that you have full decision making powers over it. Your employer, contractor, whatever ultimately gets to decide how things work. For example you might feel that SSH is the best way to access servers remotely. However your company might not like that, they want to monitor the traffic, so they insist on telnet over VPN only. You can argue with them, but if the ultimately say "This is the way it's going to be," you don't have the right to just go behind their backs.

    You can look at it somewhat similarly to a bank's relationship to your money. When you deposit your money at the bank, you make them the custodian of it, the administrator of your account. However, you aren't giving it over to them to keep, it's still your money. They can do with it only what you allow. They couldn't for example, take your money out of an FDIC insured savings account and stick it in to an uninsured investment account. Even if they made you money doing so, it still wouldn't be ok if you didn't tell them that was what you wanted. They administer your accounts yes, but in the way you specify.

    I'm not defending the city here, but just because he was the network administrator didn't give him the right to add access as he saw fit. Many companies (and government entities) have very strict rules on how access can be had to systems. The rules are often stupid, and often somewhat counterproductive, but it is their right to have those rules. You don't get to decide that you don't like them.

    So if there was a "no modems" policy, or if the policy said "Any new access has to be approved by the board of whatever," then he wasn't doing what he was supposed to. Doesn't matter if they were to make his job easier, you don't get to skate policy just because of that.

  31. Information is not property. by digitaltraveller · · Score: 1

    So what if Childs is an asshole, it's his right as an American to be one.

    Boo-hoo if the SF IT dept risk management plan couldn't handle a rogue employee refusing to give up the password.

    It's a pretty dangerous precedent if people can be legally forced to disclose information against their will.
    Isn't that what the 5th amendment was for?

    Prosecutor:
    Does your mother have AIDS? YOU MUST ANSWER
    Witness: ...Yes
    Prosecutor:
    BURN HER AT THE STAKE!!!!

    Yay Mcarthyism

  32. obama has you by the nut sack by Anonymous Coward · · Score: 0

    and he's spending your money to try to get out of debt. he may as well be betting in vegas with tax payer cash.

    1. Re:obama has you by the nut sack by Orion+Blastar · · Score: 1

      That was a lousy troll there, AC. Next time try a little bit harder on the troll and less on the Obama-bashing. Since you couldn't Bush-bash anymore, you tried an Obama-bash which only makes you look racist.

      --
      Remember, Slashdot does not have a -1 disagree moderation, and no, troll, flamebait, and overrated are not substitutes.
    2. Re:obama has you by the nut sack by Logic+Worshiper · · Score: 1

      I'm as strong of an Obama supporter as they come, but nothing in that comment was directed at Obama, nor was it racist. "The man" can mean corporations was well as the government.

    3. Re:obama has you by the nut sack by Anonymous Coward · · Score: 0

      I saw nothing racist in the troll. Stupid, yes, but not racist.

      Maybe you're reading something that isn't there to justify your own bias?

    4. Re:obama has you by the nut sack by Anonymous Coward · · Score: 0

      Incidentally, which part of the admittedly weak troll was "racist" in any way?

    5. Re:obama has you by the nut sack by Orion+Blastar · · Score: 1

      The "Obama has you by the nut sack" and "he may as well be betting in vegas with tax payer cash." portraying two negative stereotypes of African-Americans. Grabbing someone by the nut sack and gambling money away. If you cannot see that, you are blind.

      --
      Remember, Slashdot does not have a -1 disagree moderation, and no, troll, flamebait, and overrated are not substitutes.
  33. Sounds kind of like the "Criminal tools" charges by Cherveny · · Score: 1

    Sounds kind of like the "possession of criminal tools" charges so many cases have added on, when said "tools" are ANYTHING used to commit the crime. Always seemed to me just a way for prosecutors to add an extra set of random charges for extending a sentence, or extra bargaining room for a plea.

    --
    --- It's not my fault this post looks redundant. I just type too slow.
  34. But they get all this FREE: by Anonymous Coward · · Score: 0

    Now that the convicted/condemned get cable, they don't want to leave. Notice the overcrowding (over?), that's not because more are coming in, but few are going out. They LOVE IT! FREE: Three square meals, medical and dental, sex out the ass *well, literally it would be sex in the ass*, so what more could a looser want? And all this is not only FREE as in BEER, it's FREE as in ... whatever that other FREE is -- freetards, help me out here.

  35. labor union for IT by ub3r+n3u7r4l1st · · Score: 1

    We need a united labor union for IT. Somebody needs to start it. This union should provide legal assistance to its member, in return for its dues. Only that the serious, prolonged abuse of IT staff everywhere will be stopped.

    1. Re:labor union for IT by SaDan · · Score: 1

      Sorry, abuse in IT? Go get different job, or grow a spine. No one in this country is forcing you to work anywhere you don't want to be.

      Spare me the crap about the economy. I live in an area that saw 22% unemployment just over twenty years ago, this is still a rebound for us.

    2. Re:labor union for IT by Anonymous Coward · · Score: 0

      If I were forced to join an IT union, I would probably quit working in IT..

    3. Re:labor union for IT by Anonymous Coward · · Score: 0

      IT workers aren't the only workers who are exploited and/or abused, that's the point of labor unions everywhere. You think it doesn't take a spine to start a labor union?

    4. Re:labor union for IT by troll8901 · · Score: 1

      *open eyes really big*

      Which area??

      The only event I can infer is the stock market crash.

    5. Re:labor union for IT by SaDan · · Score: 1

      Rockford, IL. Manufacturing took a massive dump in the 80s, and we're still on the rebound.

    6. Re:labor union for IT by SaDan · · Score: 1

      It may take a spine to start a labor union, but what's the point? So the rest of the spineless jerks can pile on one platform?

      I have no faith in people who cannot speak for themselves or stand up for what they believe in outside of a herd.

    7. Re:labor union for IT by troll8901 · · Score: 1

      Sorry to hear that. Confirmed in the article. Hope your city recovers quickly.

  36. What a crock of shit. by DaveV1.0 · · Score: 0, Flamebait

    This article is a total crock of shit. This case does not put all admins in danger unless the author believes all admins are arrogant assholes. But, that might be the case as the author certainly appears to be one himself.

    The fact is that by withholding the password, he denied access to the systems. ANY admin with integrity would have turned the passwords over to his boss when he left the company.

    --
    There is no "-1 offended" or "-1 you don't agree with me" mod options for a reason.
    1. Re:What a crock of shit. by almondo · · Score: 1

      Actually, he may be an 'asshole' with more integrity than you understand. One strict interpretation of Sarbanes Oxley elements (albeit probably not intended) does prohibit such a disclosure in the context of systems affecting revenue(and networks he administrated did fall in that category), and would place the city in non-compliance. The reality is that the SOX rules that were supposed to govern shared accounts have really created some seriously misguided ambiguity. Unfortunately, what seems logical and intuitively right also seems to be directly at odds with compliance law. It's a cluster fsck with some inodes over-subscribed by politicians who can't count or add. To make matters worse you can have NDA crap that is pathetically written that imposes post employment disclosure prohibition that further complicates the issue. Without reading his NDAs I don't know exactly what he was facing but in over 20 years of consulting I have seen some real idiocy on paper mandated by lawyers, and in fact I have walked away from gigs where the paperwork was so contradictory at inception that it was impossible to comply with one doc without violating another. I backed out and walked away, no harm no foul. In short, I would say that the manager tried a heavy hand when proper direct pressure was more appropriate. A demand to seal and vault global enterprise credentials (root/enable/etc) could have been complied with, and a subsequent de-vault for documented appropriate cause would have complied with SOX where a demand for direct unauditable disclosure violates several SOX auditing factors.

    2. Re:What a crock of shit. by ishobo · · Score: 1

      One strict interpretation of Sarbanes Oxley elements...and would place the city in non-compliance

      If you knew what you were talking about, you would know that the Sarbanes-Oxley Act only applies to U.S. public companies and their accounting firms.

      --
      Slashdot - The great and glorious cluster fuck of Internet wisdom.
  37. Not quite as simple as that by Sycraft-fu · · Score: 5, Informative

    He has a right to speedy trial (as per the Constitution). This is a right that defendants can and do exercise some times. Basically your attorney tells the court that you want to exercise your right to speedy trial and the judge tells the prosecution "Ok, get your shit ready, this moves forward soon." In California, the speedy trial statue is 60 days. Judges can set a shorter date, if there's good reason to do so, ie prosecution isn't gathering new evidence, just stonewalling. So, if his attorney pushed that, he'd have already gone to trial. However, it is also often not done. The defense often wants time to prepare a case, in particular if the prosecution has a good case and the defense needs time to poke holes in it. After all, you don't want to push for speedy trial if it means you won't be ready and you are just going to lose.

    So the reason this hasn't gone to trial is almost certainly the decisions of his lawyer. Had the government really had zero case, a speedy trial motion would have been filed and granted and they'd have already lost. You don't see this very often because those cases are usually dropped. A DA would much rather drop a weak case they are going to lose than go to trial and lose it.

    1. Re:Not quite as simple as that by Locke2005 · · Score: 1

      So the reason this hasn't gone to trial is almost certainly the decisions of his lawyer. No, the decision of his lawyer was probably to tell Childs "Do you have $30,000 to pay me to argue this for you in court? Because if you don't perhaps we should wait and see if the prosecutors come to their senses." Sure, if money is no object, you demand a speedy trial. If you're a normal person, you probably don't have that much cash in your back pocket. Good luck to Childs in finding a lawyer willing to take on a false imprisonment and malicious prosecution case on a contingency basis. And yes, once you keep somebody in jail for 7 months, you virtually HAVE to convict them of some offense for which the penalty is "time served". I agree Terry Childs is a paranoid jackass, but if he can afford good lawyers, the city is going to be in a world of hurt.

      --
      I've abandoned my search for truth; now I'm just looking for some useful delusions.
  38. Random musings by Joe+U · · Score: 1

    Look, the fact is, if The Man wants to get you, The Man will get you. It doesn't matter what the laws are, exactly - they'll find something to hit you with.

    Admins could always get some insurance, unionize or something similar. The whole 9 yards, set policy, set code of ethics, when to have a nationwide walkout, etc...

    (Yeah, I know that won't happen anytime soon, heck, the whole thing will most likely fall apart with a Linux/Mac/Windows fight in about 15 mins, but it's a nice idea)

    1. Re:Random musings by Anonymous Coward · · Score: 0

      You don't need a union to organize and set up ethics codes and whatnot.

      Frankly, I'd be surprised if there isn't some kind of Society of Network Engineers or similar professional organization.

    2. Re:Random musings by Anonymous Coward · · Score: 0

      That would fall under "or something similar"

    3. Re:Random musings by AK+Marc · · Score: 1

      A union is a professional organization. IEEE could be considered a union (not that they'd want the stigma, but most professional engineering organizations could be considered unions).

  39. Pinstripes by Anonymous Coward · · Score: 0

    Thy haven't used striped uniforms for years, Today it's more like orange and chrome.

    1. Re:Pinstripes by Larryish · · Score: 1

      And gray.

      The Missouri DOC uses "state grays", which are a medium gray color.

      Much easier on the eyes than day-glo orange.

  40. I'm almost about to side with the City. by icannotthinkofaname · · Score: 1

    After skimming TFA and googling for more information on this, all I see is that Childs appears to have abused his technological powers as a network administrator.

    No network administrator is going to be at risk for anything as long as they play nice and don't pull crap like bringing a city's network activity to a screeching halt just because they're pissed off or whatever.

    Sure, you can be as paranoid as you want about security, but there is no reason why an entire city's network activity should be cut off, nor should there ever be any reason to refuse restore it. Well, okay, in recent years in the US, maybe there could be reason, but this is not the case with what Childs did.

    The only problem I have that prevents me from being completely against Childs right now is that I don't know what "Section 502" is that charges 2-4 mention, so I don't know if he was actually in violation of that at all.

    Unrelatedly, I'm new here and I have a question: How long before I make a habit of noticing fantastic-looking headlines and immediately checking for a kdawson story?

    --
    Let q be a radix > 1. I am in ur base-q, killing 10 d00ds.
    1. Re:I'm almost about to side with the City. by troll8901 · · Score: 1

      Unrelatedly, I'm new here and I have a question: How long before I make a habit of noticing fantastic-looking headlines and immediately checking for a kdawson story?

      Many months, when you've begun demanding higher standards of news coverage from Slashdot.

      I've begun reading in Q3 2008, begun writing in mid-Nov 2008 and I still don't bother checking if it's kdawson. I'm still highly fascinated by the +5 Interesting/Insightful comments written by other people, and I still don't RTFA. :)

    2. Re:I'm almost about to side with the City. by makomk · · Score: 2, Informative

      No network administrator is going to be at risk for anything as long as they play nice and don't pull crap like bringing a city's network activity to a screeching halt just because they're pissed off or whatever.

      If that was the case, then Terry Childs wouldn't be under arrest. Despite the impression you may have gotten, he didn't bring the "network activity to a screeching halt" - it carried on working perfectly, and I think even the city eventually admitted this. (You've probably been reading misleading news reports based on equally misleading press releases by the city.)

    3. Re:I'm almost about to side with the City. by icannotthinkofaname · · Score: 1

      Yep. Like I said, I could still support Childs if I had more info.

      Can't remember what I read yesterday, so I can't have you verify how misleading my sources were.

      If Terry doing his job was disruptive to the City, then this whole thing is completely stupid. I'm sure Terry has his reasons for what he did, but because he's a network administrator and is leagues ahead of the average computer user in terms of what he knows, the trick is going to be making the City understand his reasons why he did whatever it is he did.

      After R'ing a couple more FA's (this time linked to from /.), seems like all he did was be more paranoid about network security than his boss(es) liked. The trick, then, is going to be making the judge/jury understand why what he did was just doing his job (and having an idea of the average computer user, that looks pretty unlikely).

      Again, knowing Section 502 that he's accused of violating would help. After a quick but not a thorough search of Google, I have no idea what this section of San Francisco or California law is.

      --
      Let q be a radix > 1. I am in ur base-q, killing 10 d00ds.
    4. Re:I'm almost about to side with the City. by Anonymous Coward · · Score: 0

      Unrelatedly, I'm new here and I have a question: How long before I make a habit of noticing fantastic-looking headlines and immediately checking for a kdawson story?

      Usually about 5 minutes.

  41. Re:Section 502 Interpretation by b4dc0d3r · · Score: 1

    Knowingly and without permission
    provides or assists in providing
    a means of accessing a computer, computer system, or computer network
    in violation of this section.

    The section lists the rules, but he has to knowingly provide access, In other words, he has to do it intentionally.

    More importantly, the rules are No Hacking data, phreaking, DOS, release virus, general black hattery... Or providing the tools to do it. No one would say a modem is a hacking tool would they? More so than a gigabit network?

    http://law.onecle.com/california/penal/502.html

  42. You can get fired for doing your job by Orion+Blastar · · Score: 1

    employment contracts are legal slavery, network use contracts doubly so.

    You can get fired for just doing your job, it has happened to me two times. If you don't give them your passwords, they will use spyware to capture your keystrokes and steal your password and spy on your computer usage as well.

    Even if when you use the Internet for research and development on programming web sites that are "fair use" they are used against you as surfing during work hours even if your manager told you to visit those web sites to learn new skills and find new technology to improve the programs you are responsible for. Meanwhile managers surf MSN, stock quotes, eBay, and so do coworkers and it is never counted against them.

    When a manager is vague on what they want, and don't hand over meeting notes or descriptions of what they want the program to do, it is a "communication issue" with the programmer, not the manager, and the programmer is being a bad employee again.

    The programmer does his best to make the program do what the managers want, even without the information needed. But it is not good enough, and sent back for a rewrite with a vague description to make it less like Outlook but more like a four windowed item list sorted by ID. When you ask which ID, they refuse to tell you if it is an employee ID, a matter ID, a client ID, a workgroup ID. Then you ask what you want in the data columns and rows, which they don't understand what a row and column are or what data means. So you say pieces of information on the up and down positions, and then they get mad at you for dumbing it down for them. The programmer is annoying the manager and project leader (who all have no programming or technical experience) and talking down to them. Another communication issue.

    Since they know my passwords, they checked into the server to check my source code, and then scribbled all over it with gibberish and checked it back in. Forcing me to revert the changes and it looks like I was the one who did the wrecking of code because the managers used my password for various things that they got via spyware on my system.

    --
    Remember, Slashdot does not have a -1 disagree moderation, and no, troll, flamebait, and overrated are not substitutes.
    1. Re:You can get fired for doing your job by bjourne · · Score: 1

      Ok... I'd stay of the crack pipe for a while if I where you.

    2. Re:You can get fired for doing your job by Orion+Blastar · · Score: 1

      I don't smoke crack, I have schizoaffective disorder you insensitive clod!

      --
      Remember, Slashdot does not have a -1 disagree moderation, and no, troll, flamebait, and overrated are not substitutes.
  43. That's not a modem by Profane+MuthaFucka · · Score: 1

    It's a computerized terror phone.

    And this article? It's the libertarian wet-dream of someone who never went to law school. It's not like having ONE MORE silly interpretation of the law is going to make it any easier for the cops to arrest you. Not when a cop already has a thousand possibilities for that already.

    --
    Fascism trolls keeping me up every night. When I starts a preachin', he HITS ME WITH HIS REICH!
  44. Re:Slacker!!(insert severe sarcasm here-It's a jok by SL+Baur · · Score: 0, Flamebait

    Then you will never truly achieve 'BOFH' status, Grasshopper.

    I do believe that whatever else happens with this case, Mr. Childs(, Sir!) has achieved Hall Of Fame BOFH status and I so nominate him.

    I think he's right and SF is stupid, but I think all people in NC are stupid, including me for working here.

    Split Northern California and Southern California in half, cede Northern California to Zimbabwe or anyone convenient and the budget problems in what's left of the real California will be mostly solved.

  45. Future sys admin dialogue? by DeathElk · · Score: 2, Funny

    Tony: Hi Mike, how ya doin'? How was Joilet?

    Mike: Oh, it was bad. Thursday night they'd serve a wicked pepper steak.

    Tony: Can't be as bad as the cabbage roll at the Terra-Phelavo penn.

    Steve: Or that oatmeal at the Cook County slammer.

    Tony: Well, they're all pretty bad.

  46. Will SOMEBODY please think of CHILDs? by Anonymous Coward · · Score: 0

    k thx bye

  47. since when does a charge in one U.S. State... by marcushnk · · Score: 1

    Have such a direct effect on the laws across the world?
    I very much doubt that him being convicted would have any effect my me being charged with the same thing here in Australia.

    Someone needs to tell those yanks that U.S. != World :-P

    --
    "Consider how lucky you are that life has been good to you so far. Alternatively, if life hasn't been good to you so far
    1. Re:since when does a charge in one U.S. State... by actionbastard · · Score: 1

      It would affect any person charged with a similar 'crime' in any court in the U.S. because the case is being tried in a court of 'competent jurisdiction'. If Child's attorneys botch this and he goes down on these charges -and loses on appeal- the precedent that this would set could effectively screw a whole lot of people in the future.

      --
      Sig this!
  48. Not so fast by westlake · · Score: 1
    No criminal charges, just a civil liabilities. That is what should have happened to Childs, no more no less.

    The civil judge can - and will - demand the keys. He will find you in comptenpt. He will put you in jail. For no set term. He just might be able to set the per diem for your stay in the Roach Motel.

    1. Re:Not so fast by pavon · · Score: 1

      Agreed, but he DID hand over the passwords to the Mayor a couple of weeks after he was arrested, and without any court order to do so. That was months ago, and he is still sitting in jail awaiting trial for other criminal charges. The charges are all bunk - really stretched interpretations of laws that were already very overbearing to begin with. The set bail is bunk - there is no reason to think that Childs will skip town, in fact his stubborn behavior thus far strongly indicates that he wants his day in court to vindicate himself.

  49. hoist by your own security petard by bzipitidoo · · Score: 0, Redundant

    The city has physical access, and the information is not encrypted. They don't need passwords. That they've somehow got themselves stuck needing passwords means they or Cisco messed up. They shouldn't blame former admins for that.

    I really wonder about these devices that have "security" features that will in essence enable them to brick themselves. Hard enough keeping equipment running smoothly without having to deal with a self destruct feature in the finest traditions of Star Trek drama. I'm sure the things have a button to reset everything to factory defaults, but I suppose using that would wipe the configuration. Can't the configuration be read off the devices? Shouldn't it already be saved elsewhere? If it isn't possible to work with these devices when given physical access, then that's a problem. The devices shouldn't have such features, or if they are supposed to, then the city should have bought other devices.

    So the system is set up with a huge, fixable flaw. So, fix it. But no, they'd rather lynch someone. Why aren't they also suing Cisco for having put such a nasty flawed feature in their products?

    --
    Intellectual Property is a monopolistic, selfish, and defective concept. It is "tyranny over the mind of man"
    1. Re:hoist by your own security petard by Dr.+Ion · · Score: 1

      Amazing.. it appears you didn't even look at the post you replied to.

    2. Re:hoist by your own security petard by _Sprocket_ · · Score: 1

      So the system is set up with a huge, fixable flaw. So, fix it. But no, they'd rather lynch someone. Why aren't they also suing Cisco for having put such a nasty flawed feature in their products?

      No, the system was set up as intended using a well-known, well-understood security feature. It will not "brick" the hardware. Please feel free to re-read the post you replied to and, for further insight, do some basic Googling. It is a lack of understanding that is the cornerstone of this whole fiasco.

    3. Re:hoist by your own security petard by bzipitidoo · · Score: 1

      I already waste enough time posting. No, I'm not going to search out every tiny little thing. Maybe you could just tell me? Without having to resort to a search yourself, of course. You did say it was well known. Perhaps it is, to Cisco networking specialists, which obviously I am not.

      Yes I did read the post. I don't know how hard it is to change out the flash memory in those things. I was envisioning some special tool to open up the box, then some kind of special, proprietary, hard to find chip, like an EEPROM BIOS in a DIP form. In short, something that couldn't just be done in a few minutes. But if it's a common type of flash memory (CF? SD?), then it's all much easier than I was thinking.

      --
      Intellectual Property is a monopolistic, selfish, and defective concept. It is "tyranny over the mind of man"
    4. Re:hoist by your own security petard by mabhatter654 · · Score: 1

      it's not bricking the hardware. Locking out the firmware is a good idea. Once you swap out the firmware chip, then you have to reset the firmware.. lose the settings so an unauthorized person has a nice router, but not any info about YOUR network, security achieved. At worst you need to do a call out if some office wannabe geek tries to fix it.

    5. Re:hoist by your own security petard by _Sprocket_ · · Score: 1

      I already waste enough time posting. No, I'm not going to search out every tiny little thing.

      Have you ever considered a career in local or even national news? You seem to have an aptitude for it; not willing to let things like easily researched facts get in the way of your chance to write about the subject.

  50. What about ssh? by actionbastard · · Score: 1

    If modems are made illegal, could ssh be made so, too? Basically this is a case where a person who has discretionary authority to act in a responsible manner to complete his job duties, granted to him by his position, being charged with not relinquishing that authority when he was terminated on grounds that had nothing to do with the performance -or lack thereof- of his job. He should have been relieved -or re-assigned- when he engaged in the sexual harassment of a female employee. If that had happened, we wouldn't be talking about the failure of both the prosecutor or the court to understand complex technical issues for which they have no understanding.

    --
    Sig this!
  51. No nukes == limited sovereignty by HornWumpus · · Score: 1

    Note the differences in how we dealt with Iraq and North Korea.

    It's a simple fact on the ground.

    Reconciling that with nuclear non-proliferation is a difficult proposition requiring Kissingeresq levels of weaseling and hair splitting.

    Iran appears unconvinced. India and Pakistan remember hearing threats but things appear to be working out otherwise.

    Libya on the other hand was apparently impressed enough by America's irritation after 9/11 to publicly give up all chemical and nuclear weapons programs and invite the UN in.

    --
    John McAfee 'It was like that time I hired that Bangkok prostitute; to do my taxes, while I fucked my accountant'
    1. Re:No nukes == limited sovereignty by WNight · · Score: 1

      North Korea doesn't have anything worth taking. That's all it was. Nukes might be a threat, but nobody believes NK actually has them in any usable fashion. There's a big difference between a static nuke test and using it to stop invaders.

      No, the fact is that Bush Jr. had been planning to invade Iraq from long before 9/11. If Iraq had a test like NK did he'd have used that as an excuse to invade, not been deterred.

    2. Re:No nukes == limited sovereignty by Cederic · · Score: 1

      Agreed, and to add the one single word that really matters:

      Oil.

  52. Don't go poaching by tqft · · Score: 1

    In UK/NZ/Australia - poaching laws go way back.

    Fisheries and Games inspectors have a lto of power - including search you appear to be fishing so we will check your catch.

    If what you have done is illegal and goes before a magistrate they can take your fishing ear - including rods, tackle, boat & car (if you were using them when fishing).

    And any bank robber dumb enough to use their own car on a job would probably find it first impounded as evidence and 2nd seized and sold when they were convicted.

    --
    The Singularity is closer than you think
    Quant
  53. modems by jipn4 · · Score: 1

    Get them approved in writing by senior management. If you don't, it really does look suspicious.

  54. Lots of sysadmins on Slashdot by Toonol · · Score: 1

    And they seem very sympathetic to Childs. I'm not, and I'm not.

    The servers, any batch files, init configuration, passwords, were all property of the city, either physically or as work done for hire. I don't see any problem with Childs being penalized for his (seemingly quite arrogant) withholding of that information. It doesn't matter if his employer would promptly crash the system permanently with that info; it's theirs, not his. His boss says to hand over the passwords, he needs to hand over the passwords.

    If I hired a guy to work on my machine, and he locked something important down with a password and then wouldn't tell me, damn right he's getting sued.

    That said, childs shouldn't be getting serious, long-term jailtime. I would think it should just be contempt of court: Sit in jail until you are willing to talk. He wasn't "hacking".

    1. Re:Lots of sysadmins on Slashdot by Bronster · · Score: 1

      He said he'd only give it to the Mayor, since nobody else was authorised to have that much power over the network. Sounds fair enough to me. And then he did hand the passwords over.

      As plenty of other people have said, you really don't want to be handing out the passwords to a room full of people, especially if you don't trust those people.

    2. Re:Lots of sysadmins on Slashdot by Cederic · · Score: 1

      I would think it should just be contempt of court

      Had he refused to obey a court order to provide the credentials you may be right.

      Reality as I understand it is that no such court order exists, and he did hand over the credentials as soon as he could be sure it was appropriate to do so (i.e. not an open forum containing multiple individuals to whom he could not legitimately tell passwords without being charged with various conspiracy and/or hacking laws).

      He was willing to talk, just not to any random person. That the random people may have the same employer does not make them authorised to receive such sensitive information.

      That he was no longer employed also pulls into question his obligation to remember/provide the credentials anyway. I can't remember my passwords at previous employers; why would I?

  55. Terry Childs should get a Tron suit... by mergy · · Score: 1

    Like the Tron guy (you know the guy who made his own budget tron suit). http://www.tronguy.net/images/headshot.jpg I think I would be cool with Terry if he wasn't such a putz or a-hole and he had a tron suit on or something nutty when they brought him to jail. Overall, he gives people the sysadmin stereotype they all want - hostile, paranoid and a jerk, so it got a lot of play in the media. It is frustrating because many of us fight this stereotype constantly and make huge gains only to have a Terry Childs attitude reinforce the negative stereotype of a sysadmin who does not have a sense of who and what he is working for. Yet, even with all of that, I think if he could get in a Tron suit of some sort, I would give him another shot and it could twist the stereotype into a crazy geek rather than an asshole geek.

  56. Think of the poor laymen on that jury. by Anonymous Coward · · Score: 0

    It will be like Slashdot. A bunch of IT "experts" arguing about proper network management.

  57. Comment removed by account_deleted · · Score: 4, Insightful

    Comment removed based on user account deletion

  58. why do you lawyers like people in jail by cheekyboy · · Score: 1, Flamebait

    Seriously... why?

    Oh but when a REAL crim of the century Madof steals billions, 1000s of lawyers say NOTHING and let him live life of luxury, yet steal a coke from a 711 and bang to jail , which yields the lawyers MORE FEES thru representation.

    Why not throw every senator and politician in jail then for withholding contractual secrets and state secrets from the public which PAYS their salary.

    Jails arent for knee jerk 'im here to piss you off' punishment because I have more power.

    Its to protect the public mainly from more harm.

    --
    Liberty freedom are no1, not dicks in suits.
    1. Re:why do you lawyers like people in jail by fifedrum · · Score: 1

      some mod got a bee in their bonnet, there's nothing flamebaitish about your post, every word you wrote above is true, Madof stole billions and nothing happens to the guy.

      wonder who he bought that the 711 coke stealing guy (and the fellow in the story) couldn't buy

  59. UK admin arrested too by Anonymous Coward · · Score: 0

    .. Its a hard life as a sysadmin

    http://www.theregister.co.uk/2009/02/10/indymedia/

    "a systems administrator, was arrested on Monday and questioned for about eight hours. He has been bailed without charge to appear at a police station in May. His home was searched and computer equipment and paperwork seized."

    "The Register understands that the man arrested was not responsible for either of the comments and is not an Indymedia activist or administrator. Rather the server was hosted by UK Grid under a contract in his name, along with several others on behalf of unrelated clients. .. He was arrested under sections 44-46 of the Serious Crime Act 2007, which came into force on October 1 last year. The relevant sections criminalise "intentionally encouraging or assisting an offence", "encouraging or assisting an offence believing it will be committed" and "encouraging or assisting offences believing one or more will be committed".'

  60. overstating damages is a crime for insurance by cheekyboy · · Score: 1

    So if my laptop gets lost or broken, I cannot go to my insurance company and ask for $250,000. Its a crime.

    Why is that not a crime for lawyers/prosecutors?

    Its IS a real CRIME! in REAL peoples eyes.

    --
    Liberty freedom are no1, not dicks in suits.
  61. LA is bankcrupt, hope they suffer by cheekyboy · · Score: 1

    unlike Zimbabwe, LA cannot print $$$, they can tho offer IOUs as tax returns, where in retaliation, companies/people can pay their due taxes with those IOUs.

    By the time he gets out he wont get any money out of the state, but I hope he can sue individuals for money, just like OJ was.

     

    --
    Liberty freedom are no1, not dicks in suits.
  62. What is this "world"? by Anonymous Coward · · Score: 0

    >'If Childs is convicted on the modem charges, then just about every network administrator in the world could be charged with the same "crime,"' Venezia writes.

    "In the world"? Excuse me ?
    He probably means "in the USA". Your local law is not my law...

  63. USA is not the world, Mr. Venezia... by fantomas · · Score: 1

    "then just about every network administrator in the world could be charged with the same "crime" "

    Somebody want to tell Mr. Venezia that US law doesn't cover the whole world? Maybe he should get a passport and travel a bit, or at least read wikipedia and discover there are other countries out there beyond the US borders that have their own jurisdictions.

    Heck even Bush occasionally admitted the USA couldn't just invade everywhere.

  64. That CEO would not be in jail though by Anonymous Coward · · Score: 0

    or facing counts of theft, retention of property, keeping a computer that isn't his and industrial espionage.

  65. Mu by Anonymous Coward · · Score: 0

    Mu.

  66. TL;DR by Anonymous Coward · · Score: 0

    Fact: Most mid-level, corporate IT manager-types abuse their perceived 'power' on a daily basis.

    Fact: That's what happened here.

    Fact: ROOT becomes an asshole when approached with a stupid question by user@localhost. No exceptions.

    Fact: This is borderline malicious prosecution and the fucking idiot lawyers don't understand the underlying technology enough to realize it.

    Fact: Neither does the moronic mid-level manager.

    Corollary Fact: Corporate America acts like this constantly and therefore deserve whatever hell anyone can inflict on them - up to and including napalm server death.

    Conclusion: If KingKong lives in the jungles of Cambodia, you must acquit.

  67. In Soviet Russia ... by Nicolas+MONNET · · Score: 1

    No, seriously, in Soviet Russia, most people in the ghulags had been convicted on charges of doing black market.

    Thing is, everybody was doing black market.

    1. Re:In Soviet Russia ... by v1 · · Score: 1

      Thing is, everybody was doing black market.

      I have no knowledge of that particular wedge of history. I assume that was a case of where "black market" was defined basically as "doing business without the government getting a cut"?

      --
      I work for the Department of Redundancy Department.
  68. No, that was correct... by gillbates · · Score: 1

    Since when have geographical boundaries *ever* been an obstacle to the US enforcing its laws wherever it pleases?

    --
    The society for a thought-free internet welcomes you.
    1. Re:No, that was correct... by tomhudson · · Score: 1

      Since when have geographical boundaries *ever* been an obstacle to the US enforcing its laws wherever it pleases?

      That's right - Vietnam was such a smashing US military success.

      Iraq was "mission accomplished" how many years ago?

      Afghanistan?

      Trade cooperation is the only long-term model that works, which is why trade protectionism is just another way for the US to shoot itself in the foot, by

      1. costly subsidizing of less efficient parts of industries (*cough* GM, Chrysler, Bank of America, Citi, *cough*), and
      2. less clout for such things as influence over issues such as economic policy, human rights, environmental policy, etc.
  69. three valid questions though, by DragonTHC · · Score: 1

    What if your job responsibilities include developing security policy and protocols?

    What happens if management wants you to violate those and provide open access to untrustworthy or unqualified people?

    Would they have you arrested for following the policy and protocols they agreed to?

    I can't help but wonder what impact this could have for all honest and qualified administrators.

    --
    They're using their grammar skills there.
  70. Why are you defending him? by evan1l38 · · Score: 1

    The thing that is odd to me is that if someone locked any of us out of our own boxes and refused to give us access, we'd all be spitting tacks.

    Childs locks an entire city out of their own boxes and I'm reading "Hey, the boxes didn't crash, so no harm done!" Do you guys really believe that? Would you defend someone who locked you out of your own system, even if they said it was for your own good? Would you say "Hey, the box is still up, so it's fine that I'm locked out!"? I really don't think you would.

    I just can't defend the guy. He was an ass, he caused his own problems when he could EASILY have avoided them just by not being an ass, he admits that he caused his own problems and that it wasn't worth it (in the last Childs slashdot article linked) and frankly if he did this crap to ANY of the guys defending him here, they'd be the first ones demanding his head.

    Yes, his managers could have handled this better and probably were asses as well. The boss being an ass-hat doesn't cancel out Child's ass-hattery.

    Oh well. It's easier to grandstand and defend him when you aren't the one affected I suppose.

    Personally I pity his coworkers who now have his huge undocumented mess to deal with. As far as I am concerned, you could take his entire admin style and write it up as a counter-example of what to never, ever do or allow to happen to your systems.

    --

    Evan Reynolds evanthx@hotmail.com
    Two peanuts crossed the street. One was assaulted.

    1. Re:Why are you defending him? by pacinpm · · Score: 1

      You are wrong. Sysadmin is like a soldier on guard which has to shoot anyone who knows no password. Even if it means shooting a general.

    2. Re:Why are you defending him? by evan1l38 · · Score: 1

      To use your analogy, though, this is a soldier on guard that made up his own password and won't let anyone know what it is. Which is not particularly helpful when you have legitimate traffic that would like to pass through but can't because no one knows the password.

      But frankly I don't think it's a particularly valid analogy. ;-)

      --

      Evan Reynolds evanthx@hotmail.com
      Two peanuts crossed the street. One was assaulted.

    3. Re:Why are you defending him? by SignalFreq · · Score: 1

      I agree, bad analogy. Also incorrect information.

      1) Mr. Childs did agree to release the password to the Mayor. He refused to release them to the people who demanded them because he believed they had an agenda that might compromise the security of the system.

      2) At worst, Mr. Childs is guilty of a civil violation. The city, however, used a very weak case based on three modems in Mr. Childs' office to prosecute him with criminal charges. They have held him in jail for 7 months now, based solely on this fact. The judge set the bail (after prosecutors urging) at $5 Million, well beyond anything Mr. Childs could post. These modems turned out to be 100% legitimate and used for 1) paging Mr. Childs about network errors 2) testing connectivity 3) emergency fail over to a backup site. One of the modems existed prior to Mr. Childs even being hired.

      They accused him of criminal acts, they searched his house, they trashed him in the media, they illegally leaked his HR records, and they held him in jail all based on THREE MODEMS.

  71. Setting bonds based on what? by phorm · · Score: 1

    It seems to me that the amount/type of bonds is set based a variety of aspects, but high among those is the type of case and the arguments presented by the prosecutor as to whether the defendant is a risk or not...

  72. Getting the law into the job by Drakkenmensch · · Score: 1

    I'm pretty sure that by now, a lot of managers, supervisors, CEOs and other various suits of the corporate genus are rubbing their hands together Monty Burns style, thinking they've finally found a way to control these pesky tech types and keep their sys admins under leash. But they should be very careful about sending them to jail for being protective of the passwords whose very security is paramount to getting the job done. They're already overworked, underpaid and given nowhere near the respect they deserve - if it should become a criminal offense to hold on to passwords with little to no defense or legal recourse against the corporate juggernauts, the suits will suddenly discover that the employee pool has suddenly dried up and no one wants to be their lapdo- I mean loyal employees anymore...

  73. my question... by matang · · Score: 1

    isn't the long and short of it really "why do you care who has the passwords to a place that just fired you?" if my place of employment fired me they can have any password they want. go for it, screw something up, i don't care, i don't work there anymore. his real problem was making the job more than a job. he's only the superhero of the network in his mind.

    1. Re:my question... by codepunk · · Score: 1

      Exactly I would have just given them the passwords and said there you go have a nice life. Any call for additional information on
      architecture, setup etc will incur a $1000 hr charge 1 hr minimum for any call....a man has to eat you know.

      --


      Got Code?
    2. Re:my question... by Cederic · · Score: 1

      You would give passwords to a room of people that lacked authorisation for them?

      Have you any idea how many laws that breaks?

      Forget professional ethics, forget contractual obligations (both of which should stop you from doing such a thing) you'd be breaking a myriad of criminal laws by intentionally revealing passwords without authorisation.

      Learn the law, it's really rather very nasty.

    3. Re:my question... by codepunk · · Score: 1

      Look, my boss comes to me and asks for the passwords he is going to get them right then and there.

      --


      Got Code?
    4. Re:my question... by Cederic · · Score: 1

      I find myself utterly fucking amazed by the number of people that'll do anything their boss asks them to.

      A: If your boss tells you to break the law and you do, you get prosecuted. (He may too, but that's not much comfort).
      B: If you've been sacked, he's no longer your boss
      C: Your passwords are not your boss' passwords. He does not have the authorisation to have them.

      Maybe I'm just bloody weird in that I know company secrets that I can't share with my boss without getting sacked. Then again I know a lot of people with computer access that can't share those details with their boss without literally breaking the law.

      As I said, learn the law. It truly is rather very nasty.

  74. Vendetta by SignalFreq · · Score: 1

    There is a lot of false information floating out there. Take this SFGate article for example:

    http://www.sfgate.com/cgi-bin/article.cgi?f=/c/a/2008/07/14/BAOS11P1M5.DTL

    "A disgruntled city computer engineer has virtually commandeered San Francisco's new multi million-dollar computer network, altering it to deny access to top administrators even as he sits in jail on $5 million bail, authorities said Monday."

    How, exactly, did he alter the network from jail?

    "Childs created a password that granted him exclusive access to the system, authorities said. He initially gave pass codes to police, but they didn't work. When pressed, Childs refused to divulge the real code even when threatened with arrest, they said."

    He was the network administrator, so he was entitled to access to the system. If the city's IT policy did not require him to document important passwords, then he has done nothing wrong. They threatened to arrest him, for what could only ever be a CIVIL infraction.

    As others have discussed, the demand for the passwords came during an impromptu meeting where the people present had no business hearing the passwords. He has no responsibility to give out passwords to random people. After this ambush, he felt he could not trust the people around him and stated he would give the passwords only to the Mayor--basically the equivalent of the CEO. Again, he has done nothing wrong.

    "One official with knowledge of the case said he had been disciplined on the job in recent months for poor performance and that his supervisors had tried to fire him. "They weren't able to do it - this was kind of his insurance policy," said the official, speaking on condition of anonymity because the attempted firing was a personnel matter."

    A city official revealed confidential information to the press, knowing that it was illegal to do so (hence the anonymity) and insinuating that Mr. Childs had an ulterior motive. Smells fishy.

    They knew that he had done nothing wrong, and that at best they had a CIVIL complaint. They went hunting and found three modems in his office. They used that to arrest him on CRIMINAL CHARGES. After that:

    "Officials also said they feared that although Childs is in jail, he may have enabled a third party to access the system by telephone or other electronic device and order the destruction of hundreds of thousands of sensitive documents. Authorities have searched Childs' home and car for a device that could be used in such an attack, but so far no such evidence has been found."

    WTF? They claimed he had setup three modems and used that to Justify searching his house. On this alone they are permitted to search his home and car? What we find out 7 months later:

    "One was set up to dial out to Childs' pager any time a problem popped up on the city's network. The second was a DSL modem that had been set up even before Childs was hired at DTIS, used to connect to the Internet and test access to the city's network. The third was for emergency use only, designed to connect city computers to a disaster recovery site so that the city's network could be up and running in the event of an emergency."

    This is a personal vendetta by Management at the City.

    If this had happened at a large corporation, do you think the Police would have agreed and searched his house? Do you think the DA would have even charged him with anything? Would the judge have set a $5 million dollar bail??

    I hope Mr. Childs wins and counter sues the city.

  75. Vague 'crimes' by PMuse · · Score: 1

    It's interesting how laws are written so broadly that they cover routine, legitimate acts. What makes activity criminal, apparently, is whether the government likes you this week.

    --
    "We reject as false the choice between our safety and our ideals." --The American President (20.1.2009)
  76. Short court case by Locke2005 · · Score: 1

    Judge: "Mr. Childs, why didn't you give the city the passwords they requested?"
    Childs: "Uh... because I couldn't remember them!"
    Judge: "Charges dismissed."

    --
    I've abandoned my search for truth; now I'm just looking for some useful delusions.
  77. Anonymous Coward by Anonymous Coward · · Score: 0

    According to this affidavit by the investigator he could be charged with a Denial of Service (DoS) offense. He denied city officials access to their equipment by not giving them their passwords. I can see how he could be charged with this offense. Whether it can hold up in court is another story.

    http://akamai.infoworld.com/weblog/venezia/childs/tcramsay_affidavit1.pdf

  78. Excessive bail by Anonymous Coward · · Score: 0

    And since they dropped the most serious charge, can we admit his 8th amendment rights were stomped and pissed-upon by the 5 million dollar bail requirement?

    I'm posting this anonymously for what will soon be obvious reasons. Prosecutors routinely suggest excessive bails for any number of reasons, or argue "persuasively" for a high bail, and judges are only too happy to rubber-stamp those suggestions or arguments.

    I was arrested for what should have been a simple domestic matter (and was even assured by the cops that it was no big deal and would blow over), but the county prosecutor charged me with aggravated assault with a deadly weapon. Long story, and in no way am I trying to minimize what I did, but when I finally got my hearing and was officially charged, the prosecutor actually lied through his teeth in jail court when making his argument. (I was later told by my attorney that this was common.) The judge accepted this argument and set my bail at $18,000. In the same court, a gang banger who had two charges of aggravated assault with a deadly weapon against him was given bail of less than $4,000.

    Every attorney I spoke to after I got out told me that the bail was excessive. I could have fought for lower bail, but that would take time, and in the meantime I would have lost my job due to absence. And there was the little matter of effectively being denied legal representation because I could not contact my attorney, due to the way my county's jail systems are run and the restrictions they place on outside contact. Good luck getting a hearing.

    I wound up having to post my own bail, which is very unusual, and maxed a credit card just to raise the 10% I needed for the bail bondsman, plus I had to put my house up as collateral. In the end, the county prosecutor dropped the charges against me, and the city filed misdemeanor charges instead.

    People of every social stratum and economic means are getting their rights systematically abused, but you tend to not notice it until you're the one getting sucked into the system. Excessive bail is a powerful tool for punishment, and one that is used frequently despite Constitutional prohibitions.

  79. Guilty by ACMENEWSLLC · · Score: 1

    I'm sorry, but this article is "the sky is falling" type reporting that AP, Reuters, and CNN do. These three orginizations reported that we had captured Osama Bin Laden.

    The complaint is that he put these modems in a locked room with no authorization, and against municipal law. If I have a modem on my companies network to allow RAS, you better believe my boss approved it. He had violated many of his legal responsibilities. He set routers up with passwords only he knew, which would be nuked clear if normal console password recovery attempts were made, and locked some of these up behind doors only he had the key to.

    What if he got hit by a bus? We had a guy die on us a few years back. Procedure had him put his passwords in a locked cabinet inside a locked and secured room. The city has it's own provisions for such possibilities. Laws. He admits to not following.

    If you take any of these charges on the summary, they look innocent. But dig into the complain which was in another ./ post, then this guy really looks guilty.

  80. what happened by GregNorc · · Score: 1

    What happened to the right to remain silent?

    His papers, notes, and files are all property of the company, and IANAL, but I don't see how they can force him to talk without offering immunity.

  81. Reminds me of Randall Schwartz by Iagi · · Score: 1
    After reading through a lot of the comments here I a striking similarity between Terry Childs and Randall Schwartz. For those too young to know: http://news.cnet.com/Intel-hacker-sentence-expunged/2100-7350_3-6164113.html

    While the cases are not exactly the same, the community response was. Most admins thought that he was right and that he did not do anything wrong and that he would eventually win in court. He didn't.

    Thirteen years later his conviction for hacking into the company's systems expunged, but that is a big chunk of time to pay.

    Anyhow ... his milage may differ, but I won't bet on it.

  82. Daft opening commment by w1z4rd · · Score: 1
    "Every admin in the world" ???

    No offense mate but you dont know what you are talking about. Believe it or not most other countries dont care about your laws.

    In fact, most other country admins sit back and laugh at the poor Americans and their endless litigation.

    Seriously though.. get a grip of your judicial system its out of control. While this kind thing might hamstring American admins, those of us with a more reasonable law system will just feel sorry for you guys.

    I love getting emails form American lawyers... I always respond to them TBP (thepiratebay.org) style.

  83. This article makes no sense. by tekshogun · · Score: 1

    Ok, 502 is referring to the California Penal Code, 502 which is all about computer hacking. I just read the entire thing. The law is pretty clear on how this guy can be charged and PROTECTS administrators that operate with in the scope. Just because an admin has a modem or some other device (it could be a satellite uplink/downlink, or DSL modem, or a direct Network-over-Radio connection) to connect to their employer network does not mean they are breaking the law, in fact, most of the time, it is protected under the law. Read the Penal Code! http://nsi.org/Library/Compsec/computerlaw/Californ.txt

  84. Dial up? by Anonymous Coward · · Score: 0

    If Childs is convicted on the modem charges, then just about every network administrator in the world could be charged with the same "crime,"' Venezia writes. All the authorities would have to do is 'point out that you have a modem or two, and suddenly you're wearing pinstripes of the jailhouse variety.'"

    All this talk about modems. What is the city on dial up. 57K over a FiberWAN?

    Yes I know everyone calls either a DSL or a cable box a modem BUT! modem is an acronimn for Modulation - Demodulation. Other words changing an analog signal to digital and back. Last I checked FiberWAN was straight digital so there is no "Modulation".

    What people call modems these days are either routers or bridges.

  85. Maybe im missing something here? Shouldn't all admins have signed an NDA specifically prohibiting him from releasing the passwords? He shouldn't even be talking about what servers they are. I had an NDA that ran on for 1 1/2 years after I left a certain Job. If he left the company/city tough luck its a management oversight.Its their job to go changing all the passwords even if its going rescue mode for each server. There are reasons why you dont have a top admin hold on to all the passwords. But the moment you fire him, your on your own.