I ask because, though I've never been near MIT, everything I read about it suggests that every one of these steps is seen as part of the game expected to be played by a few curious students now and then.
Typically, when an excessive use case is reported that is determined to originate from within MIT’s network, the Libraries report this to either the MIT Information Services and Technology (IS&T) network security team or MIT’s “Stopit” group, which deals with inappropriate behavior that occurs electronically. The Stopit group’s general response is to send the offender a warning email message. This is almost always all that is needed to get people’s attention and have them stop whatever it was they were doing that caused the problem.
[...]
This time, the requests and downloads stimulated a cascade of failures that brought down multiple JSTOR servers. Half the servers in one data center failed, and JSTOR engineers feared that the entire service might go down worldwide.
[...]
Also on October 12, the Director of the MIT Libraries reported to MIT’s Academic Council that a cyber-attack of the JSTOR database had caused a weekend shutdown of JSTOR to the entire campus.
Now take a look at the "MIT Hacker Ethic", particularly bulletpoint #2: http://hacks.mit.edu/misc/ethics.html
I guess jstor staff doesn't have access to good technical texts on how to run a network.
Breaking into a closet, and connecting your hardware gets you expelled. Regardless of the locked state of the door, entering a closet to which you do not have explicit access is breaking into said closet.
That said, I'm not as familiar as I should be with what MIT tried to do to get Aaron to stop, and whether he knew that they had deployed those because of what he did.
This was no, "Oops, I didn't realize you minded!" situation. Aaron was fully aware that MIT didn't approve of what he was doing, and he didn't care, and was actively battling to do what he pleased anyway.