Why San Francisco's Network Admin Went Rogue
An inside source reveals details of missteps and misunderstandings in the curious case of Terry Childs, network kidnapper.
"You could see him getting red in the face whenever he started talking about his department. And once you were on Terry's bad side (which thankfully I never was), that's where you stayed, and you'd get only the most grudging assistance from him from then on. Whether any of his complaints were valid or not, I can't really say, but I don't think that's as relevant as how Terry felt.”
Keys to the kingdom
If Childs' sole proprietorship of the FiberWAN network was normal operating procedure, how did
the tensions between Childs
and his managers come to a head? Why was Childs arrested on Sunday? There have been reports that the
city’s newly hired head
of security may have pushed for Childs to open the FiberWAN doors to other admins. My source
doesn’t know for sure, but offers
some insight:
“I don't know much about his actions in the last few weeks. It's been a couple of months, at least, since I've even spoken to him, and even then it was probably only in reference to some specific request or ticket. But I can imagine that being the subject of disciplinary action by his supervisors for 'performance' issues would be absolutely infuriating to him. I can imagine that his response would be, 'How can you say my performance is poor when I've been doing what no one else here was willing or able enough to do?'"
If Childs was pressured to give up the keys to the network that he had built and tended for so long, would he go so far as to explicitly prevent anyone else from tinkering with his charge?
“I can imagine that [Childs'] response to a demand to open up authentication to the FiberWAN would be, 'Why? So you can screw it up and bring the City network crashing to a halt?' I can even imagine that, under so much pressure, he'd take steps (deleting or hiding config backups, for instance) to make sure he was the only one in control.”
These tales offer significant insight into what may have occurred between Childs and the FiberWAN network hostage situation. Rather than a case of a rogue administrator attempting to cause damage to the network by locking out other administrators, this may be a case of an overprotective admin who believed he was protecting the network – and by extension, the city – from other administrators whom he considered inferior, and perhaps even dangerous. One important fact seems to be in Childs' favor, if reports that the network has continued to run smoothly since his arrest are true. My source corroborates this.
Paul Venezia is senior contributing editor of the InfoWorld Test Center and writes The Deep End blog.Terry Childs



