Another fix is to generate more good primes to use. Instead of hard coding them in the source. Or you could just swap to elliptic curve DH and avoid the hassle of staying on top of all that mess.

Logjam. TLDR; about 100k hours of CPU time can build a dictionary to crack most session keys in less than 90 seconds for 512bit primes.

And only because those 3 provide IPv6 support, and hence redirect that traffic too.

Have you looked at a graph of Greece's unemployment? It's jumped from <10% to >25% since the crisis began.

They need to increase the flow of money around the economy to stimulate job growth. During a downturn the velocity of money shrinks, so no free win there. It's unlikely they're going to increase exports, so a trade surplus is unlikely. They won't be borrowing more money from the banking sector any time soon. Which only leaves a government deficit to stimulate the economy, which is prevented by the Maastricht treaty.

Without leaving the Euro, Greece is screwed.

It's also hard to pay taxes when you are unemployed, which is a much bigger problem.

Er, no. Greece is in trouble because the Euro doesn't give them any way to handle a crisis. The failure of the euro wasn't just predictable, it was predicted.

Not gonna happen until all the private debt we've accumulated in the last 50 years is gone.

Make sure you aren't running out of RAM for some reason. For example, I've seen the "Server" windows service leaking memory like a sieve in Windows 8. I've seen the BIOS limit available memory to 4GB, even though there was 16GB installed. Combined, these issues caused the machine I was using to practically grind to a halt.

Everyone works with their files locally, changes are synced via a common server. Everyone has a compressed backup of the complete history of the entire filesystem for disaster recovery. Everyone should be able to browse and recover any version of any file without adding load to the server, though usability might be slightly lacking. You could also setup a FUSE filesystem on a linux box to browse the history.

You may need to partition the file storage into multiple repositories, so that people don't need to synchronise folders that they don't use.

This sounds like a symptom of how android deals with clocks and timeouts in native code. If you call poll with a timeout, and the CPU suspends, the poll timeout stops decreasing.

You can hide the videos with a simple adblock filter; "slashdot.org##article#firehose-000".

You could also make the share button go away (slashdot.org##div.popularity), but that does break the tags css.

And in C not just the result, but the behaviour is undefined. If you divide by zero the compiler, runtime libraries and the CPU can do whatever they like. They could ignore you, crash, format your hard drive or kill your pet.

For speed reasons, this is a good thing. If it looks like you might run into undefined behaviour, the compiler can assume that the inputs to the program won't trigger that behaviour. This allows all kinds of optimisations to be performed, from dead code elimination, to hoisting invariant code out of loops.

At least other high level languages define precisely what a divide by zero should do. That way you run into platform or compiler specific heisenbugs far less frequently.

From the SSD Endurance Experiment;

To me, that case layout looks like it was designed for easily displaying and identifying the card in their presentations. Though there are a large number of small form factor cases with some kind of riser / 90 degree bend.

Then there are games where holding TAB will display the scoreboard, and holding Alt will show health bars...