, 2003-08-18
Federal prosecutors in California went too far when they put a man in prison for disclosing a website security hole to the people at risk from it.
Expand all |
Post comment
(shrug) - he had it coming.
2003-08-18
Penguinisto (6 replies)
Penguinisto (6 replies)
(shrug) - he had it coming.
2003-08-18
Anonymous (1 replies)
Anonymous (1 replies)
(shrug) - he had it coming.
2003-08-18
Beelezubb (4 replies)
Beelezubb (4 replies)
(shrug) - he had it coming.
2003-08-18
Anonymous (2 replies)
Anonymous (2 replies)
(shrug) - he had it coming.
2003-08-19
Mark D. Rasch (1 replies)
Mark D. Rasch (1 replies)
Re: (shrug) - he had it coming.
2003-08-18
Anonymous (1 replies)
Anonymous (1 replies)
(shrug) - he had it coming.
2003-08-19
Anonymous (2 replies)
Anonymous (2 replies)
The Sad Tale of a Security Whistleblower
2003-08-18
Anonymous (5 replies)
Anonymous (5 replies)
The Sad Tale of a Security Whistleblower
2003-08-18
Anonymous (2 replies)
Anonymous (2 replies)
The Sad Tale of a Security Whistleblower
2003-08-18
Anonymous (1 replies)
Anonymous (1 replies)
The Sad Tale of a Security Whistleblower
2003-08-18
Anonymous (2 replies)
Anonymous (2 replies)
The Sad Tale of a Security Whistleblower
2003-08-19
Anonymous (1 replies)
Anonymous (1 replies)
The good, the bad and the ugly.
2003-08-18
Mabrick (2 replies)
Mabrick (2 replies)
The Sad Tale of a Security Whistleblower
2003-08-18
Anonymous (8 replies)
Anonymous (8 replies)
The Sad Tale of a Security Whistleblower
2003-08-18
Chris Humphries (3 replies)
Chris Humphries (3 replies)
The Sad Tale of a Security Whistleblower
2003-08-18
Bob Radvanovsky (3 replies)
Bob Radvanovsky (3 replies)
It might have been better to talk to the press.
2003-08-18
Anonymous (2 replies)
Anonymous (2 replies)
The Sad Tale of a Security Whistleblower or How to cover your corporate @$$ when sweeping a problem under the rug
2003-08-19
Ashaman (1 replies)
Ashaman (1 replies)
The Sad Tale of a Security Whistleblower or How to cover your corporate @$$ when sweeping a problem under the rug
2003-08-19
Elc0chin0 (1 replies)
Elc0chin0 (1 replies)
Just where he has got the email addresses from?
2003-08-19
Anonymous (1 replies)
Anonymous (1 replies)
What about Cali's New Law?
2003-08-20
Nick Jacobsen (1 replies)
Nick Jacobsen (1 replies)
The Sad Tale of a Security Whistleblower
2003-08-22
Anonymous (1 replies)
Anonymous (1 replies)

- kept confidential client information 6 months after his employment
- obtained confidential client information 6 months after his employment
- used knowledge of internal company e-mail aliases (unlikely with the way he was spreading the load)
- caused excessive load on their mail servers by trying random/generated e-mail addresses.
Whichever one he used he was doing something wrong, as well as revealing confidential company information to their clients.
The guy was right to inform the company about the vulnerability initially, and if he had records of that discussion, then they could not blame him if/when someone discovered & abused it.
The clients had a right to know the information, but he didn't have a right to tell them. The company itself had an obligation to tell them, so should be in massive trouble if the security had been compromised (and perhaps even if it wasn't, for covering up the problem).
[ reply ]
Link to this comment: http://www.securityfocus.com/comments/columns/179/21602#21602