, SecurityFocus 2003-09-10
Days before going public with his penetration of the New York Times internal network last year, hacker Adrian Lamo created five new user accounts with the LexisNexis database service under the Times corporate account, which he used to rack up $300,000 in charges over the following three months, a federal complaint in New York charges.
Expand all |
Post comment
Of course he should be tried
2003-09-11
drg (3 replies)
drg (3 replies)
Of course he should be tried
2003-09-11
The 420 Zodiac (1 replies)
The 420 Zodiac (1 replies)
Of course he should be tried
2003-09-12
Wckd (1 replies)
Wckd (1 replies)
Of course he should be tried - Enough analogies!
2003-09-12
Anonymous (1 replies)
Anonymous (1 replies)
The difference between my network and yours.....
2003-09-11
Anonymous Hacker Supporter (3 replies)
Anonymous Hacker Supporter (3 replies)
breaking into someone's house analogy doesn't work !!!
2003-09-11
Anonymous (2 replies)
Anonymous (2 replies)
breaking into someone's house analogy doesn't work !!!
2003-09-12
An idiot like the one that posted before me.
An idiot like the one that posted before me.

There is a reason Lamo was arrested.
There is a reason there is a law against his actions.
You want to discourage folks from rummaging around your personal belongings whether they belong to a person or a corporation.
There is a reason it is called private property; invasion of property, theft by taking; theft by deception. You don't want to encourage that behavior.
Folks get together, form a group a government, note rules and provide punishment for rule breakers to encourage civil obedience, public harmony and penalize destructive behavior. yeah its not perfect.
Just because the victim was sloppy, over-exposed, not popular doesn't give someone the freedom to victimize.
come-on; 3000 lexus-nexus inquiries for friends, family and fellow employees! That's not proof of concept, that's taking advantage of a exposure.
No matter how you coat it;
it still boils down to theft.
[ reply ]
Link to this comment: http://www.securityfocus.com/comments/articles/6934/22447#22447