3 ms·
Well ya know if criminal mischief is so easy to accomplish that it occurs somewhat unconsciously, maybe that sort of soft threat just needs to be viewed as the
by mindslight 14y ago
Well ya know if criminal mischief is so easy to accomplish that it occurs somewhat unconsciously, maybe that sort of soft threat just needs to be viewed as the hostile background noise of a public network ;).
Yeah, scaling the sentence based on damages doesn't exactly make sense. Scaling based on damages that were intentionally caused might be a bit closer, but still has problems with the outrageous numbers for copyrighted information.
I can also see your above bullet points going very wrong. I mean, trying not to harp on it, but if we take Aaron's case (and just assume he ran afoul of this hypothetical law by changing his IP to continue to access JSTOR), how many of those would he have run afoul of? Seems like definitely Malicious and Obstruction, and could be argued PublicHarm. And it seems like most cases would involve Obstruction for things like ln -sf /dev/null ~/.bash_history. So we're once again triggering these scary sounding tests of harm for something that isn't ultimately that harmful.
I know it's a common moralization, but some test based on technical simplicity could fix a lot of the things that not-totally-malicious people would run up against.
- tptacek 14y agoI wrote that knowing he'd have fallen afoul of malice and obstruction (I doubt very much public harm, though). Those tests are all things I've seen in other statutes, for what it's worth. But, on the off chance that this helps clarify my mentality t you, I'm thinking we have an O(n) problem with CFAA sentencing today, and my alternative model is O(1). He also could have gone to court with some confidence that even if a jury was so petrified by "computer hacking" and so snowed by the complexity and broadness of the law, he'd stand a very good chance of establishing that he had no true malicious intent, and that his attempts to obstruct investigation were minimal (for instance, he used Mailinator, with its prima facie artificial addresses, instead of more realistic throwaway Gmail addresses).
- mindslight 14y agoWhat sentence do you think Aaron should have been facing in court? How about someone who roots and wipes a multiuser box for revenge? How do you discriminate between the two? I've got a hard time trying to come up with something "right" because it doesn't feel like Aaron's access should really be a crime at all, and JSTOR can go for civil damages or criminal copyright infringement. And it also doesn't feel like we need a law to punish someone for using a computer while defrauding a bank, because we've already got a law for defrauding a bank that even gets applied when you do it in person. And to the extent that one can cause purely virtual destruction (and hence not have any physical world laws apply), that should be the thing that is addressed as the primary crime, instead of having a lone charge of something that is usually bundled on top of other crimes to punish harder. What about punishment of cracking applying solely to damage done to the cracked systems (either categorically or monetarily, and possibly including something like your tests)? This would also put someone who successfully tries an sshd exploit and then emails the administrator completely in the right - something we've never had. What scenarios would this leave completely unpunished (with no applicable laws), and can those just be fixed with similar categories?