Tahoe-LAFS FTW!

FTW is an anagram of WTF. Coincidence? I don't think so.

Not to my ears. I'd put Suberidai or Mayonaki Wa Jyunketsu way ahead of that dirge.
Each to their own.

Indeed. One of my professors invented the tagged delay line and the invisible cache, back when you had to build it out of discrete ECL.

SSL protects the point to point link. But unless the web site requires you to have a client certificate or other security credential, anyone can download over https and see the plaintext.

From my reading of the Mega response, the crypto applied to the static content was to ensure the integrity of the files as transmitted, not the privacy.

They are free to add an arbitrary amount of additional integrity checking of the static files, both of the cryptographic and non cryptographic nature. I wouldn't be surprised if they already do because it is trivial and a normal thing to do.

If you mean the private keys, I can assure you that they don't.
There are at least two root CA private keys that I was involved in instantiating that the US government does not have.

Maybe they're feeling the heat of competition from square and feel the need to do something to stop the exodus.

Our little business finds square a lot easier to deal with.

Oh alright then.

What makes you think that meat is unhealthy?

Let's dig up some research on the matter: http://www.jbc.org/content/87/3/651.full.pdf

That doesn't mean we need them. They may or may not be a better option. Other countries get by without a monarch.

We don't *need* them. We have them anyway. A bit like a fancy car or an iphone.

>In either case, applications are also free to use material from /dev/random or /dev/urandom to seed their own PRNGs.

Just because they can, it doesn't mean they should.

Intel's Digital Random Number Generator has a Dilbert mode (not available to mortals) in which it only outputs 9.
I had to choose between xkcd mode and Dilbert mode. Dilbert mode won.

Any resemblance between the actions of the European Commission and due process is entire coincidental.

The European Commission gets to act as investigator, prosecutor, judge, jury and executioner, with no oversight.
It's then left to the courts to clean up, years after the self serving commissioner has moved on from his or her round robin appointment at the commission.
 

>You don't understand software security, do you
Actually I do. It's my job. Well mostly hardware security, but they overlap.

SQL injections are a problem of untrusted data being mistaken for trusted code. When data cannot be mistaken for code it makes it very difficult for traditional SQL injection to happen. SQL promotes the problems of data/code confusion because it is a text string that contains both and constructing and handling that string correctly has provided lots of scope for error.

Keeping your data data and code code is great for mitigating SQL injection. It does nothing for a vast collection of other aspects of software security (E.G. xss, buffer overflow, side channels etc.), but for SQL injection, type safety in language and database API is just the ticket.