3 ms·
> Burgling several sheds likely wouldn't result in 52 months in prison, but "hacker" is the modern day "witch". Perhaps computer crimes are more disruptive tha
by tzs 10y ago
> Burgling several sheds likely wouldn't result in 52 months in prison, but "hacker" is the modern day "witch".
Perhaps computer crimes are more disruptive than shed burglaries, because most of us depend more on computers than we do on sheds, and it is easier for most people to understand a shed burglary and how to take steps to protect their sheds.
The 1981 Isaac Asimov short story "A Perfect Fit" took an interesting look at that. The story can be read online here: http://www.edn.com/electronics-news/4319939/A-perfect-fit http://www.edn.com/electronics-news/4319939/A-perfect-fit
- mindslight 10y agoI agree with your description of some of the motivations, but disagree with this status quo escaping criticism. If so many people depend on computers, then shouldn't actually securing them be a priority? If an individual shirks doing the work to understand account access the way they understand shed access, then are they not partially to blame for the result? This is awfully close to leaving a shed door open and then complaining something must be done about the wildlife. The story was interesting, but I found the end abrupt and incongruous. Asimov clearly demonstrates an understanding of advancing to de facto reliance, so prescribing "take it away" is overly simplistic. If the society relies on such law to prevent people from defrauding computers, then it has a gaping vulnerability to someone who just exploits the enforcement computer first. And if it doesn't rely on it, then the punishment need not be so draconian - applying a similar punishment to a violent criminal would mean that everyone from polite society would be free to attack them with impunity. Which I believe we used to do to those who evaded the law ("outlaw"), but stopped. The post-hoc "rule of law" is a Schelling point because it is the best we can do in the physical world. But the entire advancement of networked computing is to preemptively create formal mechanically-executed protocols rather than relying on ill-specified natural language ones. It's regressive to insist that the virtual environment be ruled by both regimes, causing any benefits from formalism to be erased by the ambiguity of the legacy system. Now obviously actions through computers can have physical-world effects, and if there is an intent for a real-world crime that is still justifiably illegal. Deliberately shutting off a ventilator remotely is still murder. But the current status quo is basically demanding the right to casually connect a ventilator to the Internet, have it fail due to a portscan or other Internet background radiation, and then blame "Anonymous" instead of putting the manufacturer and hospital administration in jail for gross negligence.
- tptacek 10y agoWhat would negligence liability for site owners have to do with criminal liability for hackers? When someone breaks into a warehouse left negligently insecure by its operators, the warehouse customers might sue the operators. But that suit will have no bearing whatsoever on the criminal prosecution for the person who actually broke into the warehouse. Breaking into warehouses is a crime because no matter how bad a job the owner of a warehouse does at locking their warehouse up, we don't want random people breaking into other people's property. Why would the logic for Internet sites be any different? Also, as I'm fond of pointing out: you can coherently and reasonably lobby for liability for site owners who fail to keep out hackers. But I don't think most HN readers are going to like where that leaves the industry. Hint: Facebook and Microsoft aren't going to have any real problems surviving. But indie developers? Different story.
- mindslight 10y agoI believe you've previously argued that one problem with current computer crime sentencing is that that difference between a misdemeanor and a felony is the number of iterations of a loop. My add-on to that if it is so easy to increase the scope, then perhaps such activities shouldn't even be bona fide criminal! Hence my allusions to "wildlife" and "Internet background radiation" - phenomena that can't really be ascribed to an individual's intent but will still mess stuff up. Regarding intent - we don't need sledgehammer-crime laws to cover intentional destruction of a computer system using a sledgehammer. So why do we need network-crime laws to cover intentional destruction of a computer system using network communication? It seems like in either of these cases, one should be prosecuted for intentionally destroying a computer system regardless of the chosen technique. I think this is where the culture divide originates. Because for many instances of cracking, curiosity is the sole motivation. While things can be damaged in the process (and thus one would be civilly liable), there isn't justification for criminal charge of malicious destruction. Of course, the curious cracker is still trespassing - but contrast current sentences with the general severity of meatspace trespass. Now, this specific case does seem to have more serious intent than simple curiosity. And it's hard to find a guiding analogy, since analogous situations range from publishing the contents of a journal shoulder-surfed at a coffee shop (ie "tough shit!") to publishing the contents of intercepted postal mail (another area where technical abstractions have been warped into creating extreme penalties). Perhaps if publishing someone's "protected" (in Java parlance - not public, not strictly private) information makes us feel that some wrong has been committed, then that itself needs to be the crime. Switching the paradigm to one directly based on activity (rather than access) could certainly help to curtail commercial surveillance bureaus who currently trade in this kind of information with impunity. AFAIK, "Indie developers" aren't creating life-critical devices and should be disclaiming any use of their tools for such (eg "NO WARRANTY"). Every IC datasheet doesn't contain an explicit disclaimer regarding such just for kicks. And if a shop is, for instance, creating and integrating life-critical Internet-connected medical devices based on Linux/C !? They should be scared away from that activity.