Earlier quoted context omitted.
Its not black and white. Sure Aaron built things but he also threatened to destroy JSTOR's business model. Likewise a DDoS may seem destructive but if it causes MIT to have better Ethics and Leadership as a result then its well worth the discomfort. If theres a bug in your system you sometimes have to replace some lines of code to make it better, this isn't destruction its just change.
But it won't. I certainly hope MIT makes serious changes in its leadership and ethics (if it turns out, after all, that MIT was in some way responsible -- that's still very unclear), but that's not because anyone's DDoSing MIT, it's because I can see the story. If there's a bug in your system, fix the bug. Don't delete a file in another directory and call it change.
In the Boston Globe, Aaron's lawyer says that a suggested plea deal with probation and no actual jail sentence was rejected by MIT, and that played a part in the prosecutor pushing for harsher judgement. If there is any truth in that, then there is evidence that MIT did indeed play enough of a role to have some of the responsibility here.
We won't have a full picture of what their role might have been until Abelson's report comes out. Which likely will take a good deal of time.