"You are, of course, assuming that those who want the keys can't just hack (or walk their way in) into your server, retrieve your keys and access password."

If they can do that then they can retrieve any data you're trying to protect with the key anyway -- selfsigning would change the bar to "to be able to retrieve my information, you must already be able to retrieve *my* secret" (as compared to the CA's secret).

Except when it doesn't for 6 movies in a row ...

"This is your copy that ended up on the internet, so either your subscription or your computer is compromised. Please either prove your computer is secure, or purchase a new subscription (and don't share the password for the new ones)."

bonus points awarded for linking to a pdf.

desktop cpu's typically dissipate ~50w at a moderate load (see http://en.wikipedia.org/wiki/List_of_CPU_power_dissipation for the maximum disapation of your favourite number cruncher)

the base of a heatsink is about 5cmx5cm (the actual die is quite a bit smaller than this), that's 50w/25cm2 or about 20 000w/m2.
at a temperature difference of around 100c, this generates .5w/m2.

Also, it's Seebeck coefficient of 1.5–2.2 mV K1 is 10x better than bismuth telluride (which has a Se of around 0.2 mV/K), (http://www.iue.tuwien.ac.at/phd/mwagner/node53.html). However, neither the Power Factor, nor Device Merit numbers are mentioned, and without those it is impossible to evaluate this material for suitability in high power operation, however the target audience and the power density of .5w/m2 seems to indicate that this could be more suited for low power density operations, rather than Active Cooling.

https://en.wikipedia.org/wiki/Thermoelectric_materials is an interesting relevent page ...

My reading of that list (i'm also NAL) is that: Unless we can demonstrate harm to the Sovereign, GG, or PM, or wish to declare America "an Enemy" via a declaration of war (or other outbreak of hostilities), there can be no treason through any interaction with the US.

sounds like they should've used the windows 7 eula (section 25): LIMITATION ON AND EXCLUSION OF DAMAGES. Except for any refund the manufacturer or installer may provide, you cannot recover any other damages... This limitation applies ... even if ... Microsoft knew or should have known about the possibility of the damages.

phew, for a moment there i thought you were talking about something other than the windows license :

"LIMITATION ON AND EXCLUSION OF DAMAGES. You can recover from Microsoft .. damages up to the amount you paid for the software. You cannot recover any other damages ... It also applies even if ... Microsoft knew or should have known about the possibility of the damages.

LIMITED WARRANTY. If you follow the instructions and the software is properly licensed, the software will perform substantially as described in the Microsoft materials that you receive in or with the software."

It seems to me that this a) you can't claim more than you paid, b) the software does roughly what is documented, is a universal disclaimer; it doesn't matter if you paid for it.

Fixed that for you. Furthermore there are many normal document handling operations where you don't want that operation; it is only programming environments which should auto-handle code type syntax highlighting and auto-completion. We like to call an environment for developing code an IDE.

I agree that many simple text editors don't preserve white space, but even Word preserves indentation level, and notepad++ does quite a bit of syntax highlighting for you.

Also, referring to a sibling of this post "This completely defeats the argument "simple syntax". If you need the IDE to be able to parse it ...": you don't need an IDE, but the purpose of an IDE is to aid understanding -- simple bracket matching is always going to help. even in languages where the context of the bracket is almost immediately obvious (like java), highlighting a matching bracket allows you to perceive the extent of the current code block with minimal mental effort.

if your program is slow, you have a problem. Use a thread, now you have 2 problems. --Source Unknown.

if physical contact with the media is so dangerous, have these disks mounted inside a traditional enclosure, like an old floppy disk.
Preventing accidental contact with surfaces scratching is a well solved problem ...

WSUS only equals delayed updates if it is managed wrong.
If all you want to do is minimize bandwidth, you can set WSUS to auto-approve updates.With the WSUS server checking for updates regularly, when the 3am install domain policy ticks over, all updates would be ready to roll anyway. It may mean that some updates get delayed by 1 day, but if your patches are that critical then
a) you should not be auto-accepting updates direct from microsoft via windows update (the chance of things breaking automatically is higher than the chance of something happening from a day or 2 delayed patch), and
b) you've probably thought this through anyway.

correct.
However you or basically anyone with a SSD drive can easily do better than 125MB/s -- you can even do that with a good mechanical drive. (you don't even need raid).

The real question is: what domestic use scenario regularly requires that much bandwidth, other than copying an entire cd's worth of information in 2 seconds rather than about 10. (the overhead of finding what you want to copy, and the time it takes to issue the paste command at the destination will possibly be larger than the time it takes to copy in either scenario; for most things the computer is "sufficiently" fast.

There are common code segments across large parts of that ecosystem. eg: what fraction are running any kernel between version 2.6.37 and 3.8.8? (http://arstechnica.com/security/2013/05/critical-linux-vulnerability-imperils-users-even-after-silent-fix/ ; top google link for 'may kernel exploit')

There are many different combinations of the same software options, with a few extra patches; I don't believe there are nearly 'thousands' of unique code bases, and even then there has to be very large exposed code segments common to many of them. (eg: What if a remote code exploitation flaw was discovered in Apache? )

Having said that, the variability in file paths, memory locations, patches, versions available, or even what windowing system libraries are would make any potential issue much more limited in scope compared to over 1/3 of all computers on the net affected by either a xp, or windows 7 flaw.

If there is enough dust around that this is a valid tactic, then an even more cost effective one might be to get a better dust filter on the aircon, not have carpeted floors, and a couple of other things, to minimize the dust problem.