Yeah I saw it too. Blame it on lack of an edit button.

It was at Jabara airport in Kansas, and the 747 in question was a Dreamlifter which is a heavily modified 747 Boeing uses for cargo hauling it is manufacturing process. It has been determined that the runway in question is long enough for it to take off again, although it seems just barely.

Allows them to edit content pursuant to terms and conditions.

The resulting investigation itself would be enough of a deterrent. Having your equipment seized for examination and possibly interrogated yourself is one hell of an inconvenience, not to mention paying a lawyer. Even if you do end up being let go, it will still cost you time and money, and lots of both.

Which they wouldn't know until after they confiscate your gear and otherwise walk all over your life. No thanks.

AES GCM is already in TLS 1.2 and acts as a stream cipher, I'd like to see more AEAD modes in TLS though. The way TLS was using IV's in CBC mode cipher suites has already been fixed.

RC4 is NOT FIPS compliant. Never has been. RSA has never published a spec for RC4. The code just showed up one day on a mailing list from an anonymous source.

You seemed to have missed the point. I was proposing that the insider in a hypothetical inside job doesn't care that inputs.io crashes and burns because they just made off with 4100 BTC. As the summary mentions some people could not "panic and pull their coins out" as there were no coins to pull out.

To be clear, I'm not saying that this is what happened, merely floating it as a possibility, given the nature of BTC it wouldn't be hard to pull off.

Could have been an inside job. Collect $1.2 million in BTC from "depositors". Take all the money and run. Blame it on hackers. Profit. No one is going to investigate, there are no consequences, there is nothing to audit, and no way to seize back the funds even if some legal action were taken.

Mailing address as in a physical address that people send things to like things you bought online.

This is why we tell people to not roll there own crypto systems (particularly rolling your own cipher) if they are serious about security. http://crypto.stackexchange.com/questions/2601/is-xor-in-a-cbc-like-mode-secure

Power abhors a vacuum. There will always be a government analog (even if it just your local warlord) wherever you go as long as there are other people. This is also the reason why weakening governments simply allows corporate power grabs, I'm sure there are some who'd love to return to the days of the East India Trading Company private armies and all.

Until the OS is actually released, that is the best evidence available. I see no reason why Valve would deviate from that, given there long history of embracing the homebrew, modding and indie communities.

Unfortunately, it does appear that RC4 is broken at this point (see other commenters). The upside is that this will hopefully speed the adoption of TLS1.2 and people can start using AES in GCM mode (basically turns AES in to stream cipher with authenticated encryption as well).

Ah the good old [citation needed] as a cover up for lack of basic research. Allow me point you to the SteamOS announcement page.

http://store.steampowered.com/livingroom/SteamOS/

Where you will see under the (corny named) header 'Cooperating System' the line.

Users can alter or replace any part of the software or hardware they want. Gamers are empowered to join in the creation of the games they love. SteamOS will continue to evolve, but will remain an environment designed to foster these kinds of innovation.