I 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.