That's a good description, but everyone is still missing the actual cause. Firstly, the European Union is founded on an ideology that doesn't allow for an economic crisis. Second, when the crisis hit in 2008, the Greek *private* sector *reduced* their bank borrowing. Their money supply shrank, velocity shrank too, jobs were lost, tax receipts went down. Their government debt ratio went up, not because they were borrowing more, but because GDP fell. But the Euro doesn't allow Greece to run a large deficit, nor to increase their debt level, so they can't stimulate their economy to prevent further job losses.
The Greek government weren't in good shape before, but the combination of a crisis and the rules imposed by the Union have wiped them out.
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.
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.
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.
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.
The drive's media wear indicator ran out shortly after 700TB, signaling that the NAND's write tolerance had been exceeded. Intel doesn't have confidence in the drive at that point, so the 335 Series is designed to shift into read-only mode and then to brick itself when the power is cycled. Despite suffering just one reallocated sector, our sample dutifully followed the script. Data was accessible until a reboot prompted the drive to swallow its virtual cyanide pill.
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.
In the logjam paper, they speculate that the NSA has the funds to run the first part of a number field sieve on a small number of 1024bit primes. So long as we keep using software implementations with these well known primes hard coded in their source code, HTTPS SSH & VPN connections may be vulnerable.
Not putting all of our eggs in one basket reduces this risk considerably. In response to this threat, we should periodically publish and use a new set of primes that are appropriate for DH exchanges. Though I would be happier if it were possible to generate a new prime on the first boot of a server.
Or we could swap to using a different method for producing session keys.
OpenSSL has added protection for TLS clients by rejecting handshakes
with DH parameters shorter than 768 bits. This limit will be increased
to 1024 bits in a future release.
Good. But it doesn't go far enough. How about some kind of deprecation warning if DH is using any well known prime number?
One port to rule them all. One place to find them
One cable to bring them in and be left wondering why nothing is working
FTFY. Look, I like the idea of a single cable and port standard. But there should also be a single protocol. At least you'll have USB3 to fall back on, but I imagine many sales drones and users getting confused on the finer points of compatibility issues.
Humans only have = two hands, and they take up a fair amount of vertical space too. Stack the picking arms 10-20 high, build a conveyor belt that can bring shelves to them and they start to look much more interesting. Sure each robot may take a minute to pick one item. But this is an embarrassingly parallel problem.
Sure you need a directory service. But it needs to be tamper proof. OP is suggesting that all service names should be public keys. So all DHT records that would be published / fetched can be signed. And the connection to the service can also be signed.
That way noone can guess the current key for a known service. Then the only chance of a sybil attack is to convince someone that your key is the service they are looking for. Something that should only be possible by intercepting the first request.
If the economic modelling you use does not have a recession as one of it's possible states. It is not a model of the economy.
If your model of how individual agents interact is not consistent with the rules of double entry book-keeping, you do not have a model of the economy.
If your model of a firms profits don't line up with empirical evidence... you get the idea.
When you impose that model on an actual economy, and it fails to follow your expectations. It isn't the real world that is at fault.
Paraphrasing Hyman Minsky; The natural instability of capitalism is upwards. When firms take small risks and they pay off, they learn to take bigger and bigger risks. Bankers have an incentive to fund larger and larger risks. Asset prices climb. It becomes profitable to speculate on assets without having the income to cover your interest payments. Until the debt level peaks and the whole process works in reverse. A boom becomes a slump. There's a period of pain, when bankers and firms reduce their willingness to take risks. The economy recovers, firms take small risks and they pay off....
But everyone starts the next cycle, still carrying some of their debts from the previous cycle. If there's high inflation, who cares. You can easily pay off your debts with your increased income. But when the mountain of debt in the system gets too large, inflation is impossible.
Once inflation turns to de-flation, the cycle is broken. What starts as a period of tranquility. A "Great Moderation" if you will. Suddenly turns into a crisis. Debtors go bankrupt, money is destroyed. Distressed sellers discover the market is much smaller than they thought it was. Even low risk projects fail as the economy suddenly shrinks.
But if the government sector taxes more in the good times, and runs a deficit during a slump. They can dampen the cycle. They can lessen the pain of the inevitable crash. But do you really think that the people will allow high taxation during a long period with very little trouble?
Do you really think the government caused this? A government run by economists who haven't learnt the right lessons from history. Economists who misunderstand and ignore the role of money and credit. Economists who codified their model of a perfect economy into law. A model which has nothing to do with how the real economy actually works.
If you want to understand the situation, you have to study the role of credit and money in the economy. Both of which, mainstream economics will mistakenly tell you are irrelevant. If you've got an hour, I'd recommend watching one of Steve Keen's recent lectures on YouTube.
When banks lend, they create money and spending power with every loan. When you repay a loan, or go bankrupt, that money you didn't spend doesn't flow around the economy. It didn't become someone else's income.
The people of Greece, have less money that's travelling slower around their economy. They're in a depression. It's not like they're all hoarding it under a mattress. The Maastricht treaty places limits on both the annual government deficit and the total government debt. So at this time, when their people are out of work, the government can't pay them welfare. Making a bad problem so much worse.
The Maastricht treaty is a failed economics experiment. Perpetrated by fools, who turned their economic ideology into law. Giving nations like Greece no way to soften the impact of a financial crisis. Turning an inevitable recession, into a much greater depression.
the "austerity measurements" are just measurements to make the government not use more money than they have
FTFY. This isn't about the country, it's about the government. When money is leaving the country because the private sector is repaying (or defaulting on) debts, the government is powerless to stimulate the economy. When their tax receipts are reduced during a downturn, they can't increase welfare payments to reduce the misery of the population.
Slashdot Mirror
That's a good description, but everyone is still missing the actual cause. Firstly, the European Union is founded on an ideology that doesn't allow for an economic crisis. Second, when the crisis hit in 2008, the Greek *private* sector *reduced* their bank borrowing. Their money supply shrank, velocity shrank too, jobs were lost, tax receipts went down. Their government debt ratio went up, not because they were borrowing more, but because GDP fell. But the Euro doesn't allow Greece to run a large deficit, nor to increase their debt level, so they can't stimulate their economy to prevent further job losses.
The Greek government weren't in good shape before, but the combination of a crisis and the rules imposed by the Union have wiped them out.
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.
maybe there is some security flaw with DHE that I haven't read about yet and that is why its turned off
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.
A real recovery, one for more than just the 1%, would be greatly appreciated.
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.
The drive's media wear indicator ran out shortly after 700TB, signaling that the NAND's write tolerance had been exceeded. Intel doesn't have confidence in the drive at that point, so the 335 Series is designed to shift into read-only mode and then to brick itself when the power is cycled. Despite suffering just one reallocated sector, our sample dutifully followed the script. Data was accessible until a reboot prompted the drive to swallow its virtual cyanide pill.
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...
In the logjam paper, they speculate that the NSA has the funds to run the first part of a number field sieve on a small number of 1024bit primes. So long as we keep using software implementations with these well known primes hard coded in their source code, HTTPS SSH & VPN connections may be vulnerable.
Not putting all of our eggs in one basket reduces this risk considerably. In response to this threat, we should periodically publish and use a new set of primes that are appropriate for DH exchanges. Though I would be happier if it were possible to generate a new prime on the first boot of a server.
Or we could swap to using a different method for producing session keys.
OpenSSL has added protection for TLS clients by rejecting handshakes with DH parameters shorter than 768 bits. This limit will be increased to 1024 bits in a future release.
Good. But it doesn't go far enough. How about some kind of deprecation warning if DH is using any well known prime number?
One port to rule them all. One place to find them
One cable to bring them in and be left wondering why nothing is working
FTFY. Look, I like the idea of a single cable and port standard. But there should also be a single protocol. At least you'll have USB3 to fall back on, but I imagine many sales drones and users getting confused on the finer points of compatibility issues.
Humans only have = two hands, and they take up a fair amount of vertical space too. Stack the picking arms 10-20 high, build a conveyor belt that can bring shelves to them and they start to look much more interesting. Sure each robot may take a minute to pick one item. But this is an embarrassingly parallel problem.
Sure you need a directory service. But it needs to be tamper proof. OP is suggesting that all service names should be public keys. So all DHT records that would be published / fetched can be signed. And the connection to the service can also be signed.
That way noone can guess the current key for a known service. Then the only chance of a sybil attack is to convince someone that your key is the service they are looking for. Something that should only be possible by intercepting the first request.
And I believe that those 9 lines were typed into both the oracle and google implementation by the same engineer.
If the economic modelling you use does not have a recession as one of it's possible states. It is not a model of the economy.
If your model of how individual agents interact is not consistent with the rules of double entry book-keeping, you do not have a model of the economy.
If your model of a firms profits don't line up with empirical evidence... you get the idea.
When you impose that model on an actual economy, and it fails to follow your expectations. It isn't the real world that is at fault.
Paraphrasing Hyman Minsky; The natural instability of capitalism is upwards. When firms take small risks and they pay off, they learn to take bigger and bigger risks. Bankers have an incentive to fund larger and larger risks. Asset prices climb. It becomes profitable to speculate on assets without having the income to cover your interest payments. Until the debt level peaks and the whole process works in reverse. A boom becomes a slump. There's a period of pain, when bankers and firms reduce their willingness to take risks. The economy recovers, firms take small risks and they pay off....
But everyone starts the next cycle, still carrying some of their debts from the previous cycle. If there's high inflation, who cares. You can easily pay off your debts with your increased income. But when the mountain of debt in the system gets too large, inflation is impossible.
Once inflation turns to de-flation, the cycle is broken. What starts as a period of tranquility. A "Great Moderation" if you will. Suddenly turns into a crisis. Debtors go bankrupt, money is destroyed. Distressed sellers discover the market is much smaller than they thought it was. Even low risk projects fail as the economy suddenly shrinks.
But if the government sector taxes more in the good times, and runs a deficit during a slump. They can dampen the cycle. They can lessen the pain of the inevitable crash. But do you really think that the people will allow high taxation during a long period with very little trouble?
Do you really think the government caused this? A government run by economists who haven't learnt the right lessons from history. Economists who misunderstand and ignore the role of money and credit. Economists who codified their model of a perfect economy into law. A model which has nothing to do with how the real economy actually works.
If you want to understand the situation, you have to study the role of credit and money in the economy. Both of which, mainstream economics will mistakenly tell you are irrelevant. If you've got an hour, I'd recommend watching one of Steve Keen's recent lectures on YouTube.
When banks lend, they create money and spending power with every loan. When you repay a loan, or go bankrupt, that money you didn't spend doesn't flow around the economy. It didn't become someone else's income.
The people of Greece, have less money that's travelling slower around their economy. They're in a depression. It's not like they're all hoarding it under a mattress. The Maastricht treaty places limits on both the annual government deficit and the total government debt. So at this time, when their people are out of work, the government can't pay them welfare. Making a bad problem so much worse.
The Maastricht treaty is a failed economics experiment. Perpetrated by fools, who turned their economic ideology into law. Giving nations like Greece no way to soften the impact of a financial crisis. Turning an inevitable recession, into a much greater depression.
the "austerity measurements" are just measurements to make the government not use more money than they have
FTFY. This isn't about the country, it's about the government. When money is leaving the country because the private sector is repaying (or defaulting on) debts, the government is powerless to stimulate the economy. When their tax receipts are reduced during a downturn, they can't increase welfare payments to reduce the misery of the population.