The rest of the world and our dirty, socialist, much cheaper, single-payer medical care.
Consider these stats : the last three versions of the program -- each 420,000 lines long-had just one error each. The last 11 versions of this software had a total of 17 errors. Commercial programs of equivalent complexity would have 5,000 errors.
Take the upgrade of the software to permit the shuttle to navigate with Global Positioning Satellites, a change that involves just 1.5% of the program, or 6,366 lines of code. The specs for that one change run 2,500 pages, a volume thicker than a phone book.
Since our copyright law restricts criminal infringement to "in the course of business" (ie: you're in the business of selling infringing copies), or "distribut[ing] otherwise than in the course of a business to such an extent as to affect prejudicially the copyright owner", he'd be safe here.
The penalty qualifies, but the actions would not be criminal under NZ law.
If your DC is in the basement, or whichever floor is closest to the foundations, you've got the in-built load-bearing functionality of the whole planet, and it's free. Justifying the extra construction cost for an above-ground-level DC is hard unless the purpose of the building is to act as a DC. Consider how much a full rack weighs (a rack full of fully-loaded Sun Thumper systems is over a tonne), and then think about what's involved in engineering to carry that load many times over. Even if you only top out at a half-tonne per rack, that's still a significant load in a small footprint. It's not hard to engineer to deal with that, but it is expensive.
Come again on that one? If you have access to the hardware you can set the password to anything you want. You don't need the old password.
That's all fine and dandy if the configuration of the devices is stored in non-volatile memory, and/or you have full documentation that will allow you to rebuild the network configuration in a reasonable (this was the FC network for a major city's government, so "reasonable" is probably a couple of days at most) time.
In this case there was no certainty that the configurations were saved to NV memory (I think I read that they were actually known to have not been saved permanently), and certainly no documentation that could've had the network rebuilt inside a period of weeks. Password recovery on Cisco boxes, where it's even possible (new versions of IOS allow it to be disabled), requires reboots. Reboots lose unsaved configuration. Where you are unsure that the configuration has been written to storage and lack documentation of the network configuration, you cannot safely undertake password recovery.
Physical access has limits where you are dealing with systems that don't automatically write all configuration changes to non-volatile storage.
A bug in the hand is better than one as yet undetected.