4 ms·
I'd be grateful for corrections to any distortions or omissions in that description. I'd forgotten (or might not have heard at the time) that his conviction was
by AlexCoventry 8y ago
I'd be grateful for corrections to any distortions or omissions in that description. I'd forgotten (or might not have heard at the time) that his conviction was subsequently vacated on appeal, but that was after he already spent over a year in prison.
https://en.wikipedia.org/wiki/Weev#Conviction_overturned https://en.wikipedia.org/wiki/Weev#Conviction_overturned
- ryanlol 8y agoweev wasn't put in jail because he accessed a public url structure in an unintended manner. weev was put in jail because he wittingly conspired with others to steal AT&T customer data via a vulnerability on their website. In his correspondence with journalists and IRC logs surrounding the event he went out of his way to make abundantly clear that he was fully aware that this access was unauthorized. At the time, weev himself described his actions as "theft". You could sum a SQL injection attack down to "accessed a public url structure in an unintended manner", but that'd just be terribly dishonest.
- AlexCoventry 8y agoYou might want to tell that to the judge who overturned his conviction, and the esteemed lawyers who wrote amicus briefs for him. I agree there's a continuum from hitting URLs with predictable structures to blatant hostility like SQL injections, but the problem with the CFAA is that it doesn't draw a clear line on that continuum.
- ryanlol 8y agoThe third circuit released weev due to improper venue choice, not because he didn't knowingly break the law. I'm not sure why the third circuit would be relevant at all in this conversation to be honest.
- AlexCoventry 8y agoFair enough. I'm not really familiar with the appeal.