Rogue SF Network Admin to Stand Trial

Terry Olaes

I Used to be the [H] News Guy
2FA
Joined
Nov 27, 2006
Messages
4,646
Remember Terry Childs, the network admin that took San Francisco’s fiber WAN hostage back in July? A judge finally determined that there was enough evidence to try Childs on four felony charges. Ouch.

Childs' attorney has claimed that there was no destructive intent and that Childs was merely protecting the network from incompetent city officials who were trying to force him out of his job.
 
Wonder if this dumbass thought this would actually get this far and that he is one step closer to getting pwned. Hopefully this will have totally knocked any god complex out of him once and for all. I know and deal with way too many net admins who have egos the size of Texas LOL.
 
Yeah I agree, I dont think he should do anytime, maybe just probation and an agreement to not do this again.
 
Everything I've read to date indicates less dumbass, more nutjob loon.

Think "Richard Daystrom" from "Star Trek." Minus the brilliance to create a self preserving combat AI.
 
Yeah I agree, I dont think he should do anytime, maybe just probation and an agreement to not do this again.

Only if he gets a psych eval and counseling. Read up on what he did. It's not like he was some script kiddy spelunking the city WAN for harmless fun.
 
For those people in Admin positions over huge WANs, especially ones that power a city government (needless to say San Francisco's much be quite huge), he just got totally sick of dealing with all the stupid fucking people in the administration and city government. While I don't think he'll get off totally clean, there's some merit to what he did and why. It's a deep complicated thing that none of us here really has any detailed info about, so all the comments should be read from such a point of view.

The reason some Admins appear to have such egos is because when they're surrounded by the stupid fucking people, they appear to actually BE gods... ;)
 
This is the guy I would want looking after my network. Looks like he really gave a shit. I applaud him.
 
This is the guy I would want looking after my network. Looks like he really gave a shit. I applaud him.

Agree 100%. It looks like the person who cared the most about SF's network was Child's. A lot of bs was issued during the original press release such as he apparently put passwords on routers and switches which the DA claimed could not be bypassed. What a load of crap.
 
Agree 100%. It looks like the person who cared the most about SF's network was Child's. A lot of bs was issued during the original press release such as he apparently put passwords on routers and switches which the DA claimed could not be bypassed. What a load of crap.

I agree with you and the poster above you as well, especially since I work in the same type of position (not for a network of that size, but we do operate a WAN that spans two states and consists of 50+ locations). The amount of people who have no knowledge of how the network works, but inist they know what they are talking about, is astounding. You really have to learn to filter out the false data/reports you get from users and even other IT folks. Thankfully the team I work on has solid members and our boss really knows his shit.

In terms of the press release you are speaking of, I think the point of contention was the fact that yes, they could reset the passwords on the routers, but they'd have had to reset them to their factory state, thus wiping out the router configs, which aren't/weren't backed up properly. Documentation of the router configs was also allegedly done poorly, so a factory reset was out of the question. Thus, exploits and white hat hackers aside, they're pretty boned from their viewpoint. Is that something I agree with? To some extent, Child's was responsible for their dilemma, but if all of that shit was backed up and documented properly in the first place, a factory reset wouldn't have been as damaging. So the management folks are far more at fault than Childs, in my eyes.
 
I agree with you and the poster above you as well, especially since I work in the same type of position (not for a network of that size, but we do operate a WAN that spans two states and consists of 50+ locations). The amount of people who have no knowledge of how the network works, but inist they know what they are talking about, is astounding. You really have to learn to filter out the false data/reports you get from users and even other IT folks. Thankfully the team I work on has solid members and our boss really knows his shit.

In terms of the press release you are speaking of, I think the point of contention was the fact that yes, they could reset the passwords on the routers, but they'd have had to reset them to their factory state, thus wiping out the router configs, which aren't/weren't backed up properly. Documentation of the router configs was also allegedly done poorly, so a factory reset was out of the question. Thus, exploits and white hat hackers aside, they're pretty boned from their viewpoint. Is that something I agree with? To some extent, Child's was responsible for their dilemma, but if all of that shit was backed up and documented properly in the first place, a factory reset wouldn't have been as damaging. So the management folks are far more at fault than Childs, in my eyes.

Thats one thing that drives me insane at my work, BUILD A FRIGGING SPEC BOOK!

hell back up the config copy run tftp you retards AATRTHFGFJFJFLF

end rant. Yes when someone takes malicious control of your network. Null access routes and Reset. copy your configs and begin recovery. I know some places even have spares of critical equipment. My company does not -__- cisco 4 hour RMA my left tush..ok rant went on a little too far my bad.
 
We need a Terry Child's fan club! Though I wouldn't be surprised if someone has already created it.

Obviously without knowing the incompetent people Mr. Childs had to deal with concerning the network, we can't say a whole lot about this situation, but I know a few things that are more than likely true.

Child's was dealing with idjits. Child's was worried said idjits would ruin all his work.

Sounds like management wanted a "bailout" deal and didn't want to take responsibility for their bad decisions...
 
Back
Top