I have just received confirmation that there was indeed a DoS attack on SCO’s network, a rather sophisticated one organized by an experienced Internet engineer. The person responsible has agreed to terminate the attack in response to my earlier request[1], but it will not actually end until the timers on his ‘bots run out. I don’t actually know who the attacker is, and don’t want to; the person who phoned me was not him, but an associate — what spies call a cut-out. It is clear that the attacker was no script kiddie; he was able to come up with a subtle, selective attack that only took out a subset of sites on the subnet that hosts SCO and looked like a site outage from the outside. I had been hoping, and actually expecting, that the attacker would turn out to be some adolescent cracker with no real connection to the open-source community other than a willingness to stand down when one of its leaders asked. But no; I was told enough about his background and how he did it to be pretty sure he is one of us — and I am ashamed for all of us. Full Story
About OODA Analyst
OODA is comprised of a unique team of international experts capable of providing advanced intelligence and analysis, strategy and planning support, risk and threat management, training, decision support, crisis response, and security services to global corporations and governments.