Except the Russian AV software doesn't mind catching NSA spyware. The American AV doesn't mind catching FSB spyware. People who live within the FSB's jurisdiction should use American AV software.
If you have to give one of them six lines written by you, give them to the one that doesn't have jurisdiction over you.
Agreed. Even a minor muscle twitch at the wrong moment or needing new glasses can cause the wrong menu item in a list to be clicked.
The click sequence for test vs live should be different, starting with selecting from the test rather than the live menu. Perhaps even make the user select "enable live" from somewhere before the live menu will drop down. That makes it a lot harder to do accidentally.
On the bureaucratic side, permission to send an alert should include permission to send a false alarm and all clear for that alert.
Well, when S3 got hosed, some of the data never came back. But note that lkml.org isn't waiting to replace the board, it's switching to a VPS. In fact, it's back up now.
They have to do that so they can have an excuse to fine their corporate overlords less than they make in excess profits when they scam the world for billions.
They did the #1 most important thing and made sure the data was safe. The rest is a matter of actual need. Will the world end if the mailing list is down for a day? No, it won't.
Will millions of dollars be lost? Again, NO. Will someone spew Cheetos crumbs everywhere in impotent rage? Possibly, but not anyone who actually contributes to the kernel.
Some things actually call for a much lower error rate. Operating a nuclear plant, flying commercial jet, killing people with your gun, etc.
In two of those 3 cases, any incident results in a thorough investigation and changes to procedures and practices to make sure it doesn't happen again. In the third, it gets swept under the rug.
Had Bitcoin fulfilled the claim that you would be able to use it anywhere and everywhere, it MIGHT have maintained some degree of anonymity (if you never slipped up), but since you have to turn it into some other currency to actually spend it on anything practical, the association between that anonymous wallet and your identity will always be knowable.
Gold has plenty of value. It's ductility color and resistance to tarnishing make it prized for jewelry. Its conductivity makes it useful in electronics. Its salts even have some value in medicine.
Even dollar bills have more intrinsic value than Bitcoin. You can write notes on them and have fun defacing the portrait.
The big argument for Bitcoin retaining any value was it's usefulness and eventual use as a daily means of exchanging value. Taking a week for a transaction to clear and stratospheric transaction costs negate that future use. Even a conference for Bitcoin isn't accepting bitcoin now!
Nobody is going to accept transaction costs of more than a few percent for small transactions and nobody is going to sell anything more expensive than a cup of coffee without using an escrow and waiting until the transfer to that escrow clears before they hand over the product or service. That pretty much kills it as a means of value exchange except as a last resort.
The final nail in the coffin, it is just as traceable as a credit card or bank transfer. The people who touted it as being as anonymous as cash have been proven wrong.
Given that, what is the new theory for it retaining any value at all? It IS a fiat currency. The bit of digital data and the whole blockchain carry no intrinsic value outside of the value exchange, just like any fiat currency. If that bit of data represents anything at all, it represents the burned coal that produced the power to run the mining machine. How valuable do you suppose already burned coal is?
Like most modern financial instruments, when the music stops, a very few will make some money and a bunch of people will find no chair.
Patching browsers will kill practically all vectors for the Spectre attack. Even that is a little less urgent than fixing meltdown simply because it will take longer to get from POC to practical exploit.
It doesn't help that Intel spread some confusion. Meltdown is very serious and really does need a quick fix. Spectre needs addressing but isn't as urgent since it is quite hard to exploit successfully. Meltdown workarounds should NOT be deployed on AMD systems.
As best as I can tell, the microcode updates (BIOS) are for spectre, not meltdown.
It's good that it isn't causing you problems with your workload. OYOH, I've seen database benchmarks with a 30% loss. Not exactly a desktop load, but certainly a realistic load for a server.
I was just pointing out that this isn't the big nothing squiggleslash was claiming. The problem is real and the exploit is practical in several very large environments.
People not in those environments probably should have had a better way to sit back a few days and wait for bug reports.
If you're running on a VM in the cloud, it's not that hard for someone else to run an executable (in their own VM) on the same server. Meltdown can cross VMs.
Yes, in other words they found a replacement for the big corporate structure that worked as well or better. Note I never claimed one person would create a CPU.
Slashdot Mirror
Except the Russian AV software doesn't mind catching NSA spyware. The American AV doesn't mind catching FSB spyware. People who live within the FSB's jurisdiction should use American AV software.
If you have to give one of them six lines written by you, give them to the one that doesn't have jurisdiction over you.
Agreed. Even a minor muscle twitch at the wrong moment or needing new glasses can cause the wrong menu item in a list to be clicked.
The click sequence for test vs live should be different, starting with selecting from the test rather than the live menu. Perhaps even make the user select "enable live" from somewhere before the live menu will drop down. That makes it a lot harder to do accidentally.
On the bureaucratic side, permission to send an alert should include permission to send a false alarm and all clear for that alert.
So backed by the full faith and credit of the drug cartels? Seems legit.....
Well, when S3 got hosed, some of the data never came back. But note that lkml.org isn't waiting to replace the board, it's switching to a VPS. In fact, it's back up now.
They have to do that so they can have an excuse to fine their corporate overlords less than they make in excess profits when they scam the world for billions.
Actually, "The Cloud" has had more down time than lkml.org over the last few years.
They did the #1 most important thing and made sure the data was safe. The rest is a matter of actual need. Will the world end if the mailing list is down for a day? No, it won't.
Will millions of dollars be lost? Again, NO. Will someone spew Cheetos crumbs everywhere in impotent rage? Possibly, but not anyone who actually contributes to the kernel.
Firemen and emergency medical personnel seem to still do that.
Some things actually call for a much lower error rate. Operating a nuclear plant, flying commercial jet, killing people with your gun, etc.
In two of those 3 cases, any incident results in a thorough investigation and changes to procedures and practices to make sure it doesn't happen again. In the third, it gets swept under the rug.
Had Bitcoin fulfilled the claim that you would be able to use it anywhere and everywhere, it MIGHT have maintained some degree of anonymity (if you never slipped up), but since you have to turn it into some other currency to actually spend it on anything practical, the association between that anonymous wallet and your identity will always be knowable.
Gold has plenty of value. It's ductility color and resistance to tarnishing make it prized for jewelry. Its conductivity makes it useful in electronics. Its salts even have some value in medicine.
Even dollar bills have more intrinsic value than Bitcoin. You can write notes on them and have fun defacing the portrait.
People use gold for that. It has the advantages of being tangible and having thousands of years track record for holding value.
Nobody is going to accept transaction costs of more than a few percent for small transactions and nobody is going to sell anything more expensive than a cup of coffee without using an escrow and waiting until the transfer to that escrow clears before they hand over the product or service. That pretty much kills it as a means of value exchange except as a last resort.
The final nail in the coffin, it is just as traceable as a credit card or bank transfer. The people who touted it as being as anonymous as cash have been proven wrong.
Given that, what is the new theory for it retaining any value at all? It IS a fiat currency. The bit of digital data and the whole blockchain carry no intrinsic value outside of the value exchange, just like any fiat currency. If that bit of data represents anything at all, it represents the burned coal that produced the power to run the mining machine. How valuable do you suppose already burned coal is?
Like most modern financial instruments, when the music stops, a very few will make some money and a bunch of people will find no chair.
Patching browsers will kill practically all vectors for the Spectre attack. Even that is a little less urgent than fixing meltdown simply because it will take longer to get from POC to practical exploit.
It doesn't help that Intel spread some confusion. Meltdown is very serious and really does need a quick fix. Spectre needs addressing but isn't as urgent since it is quite hard to exploit successfully. Meltdown workarounds should NOT be deployed on AMD systems.
As best as I can tell, the microcode updates (BIOS) are for spectre, not meltdown.
It's good that it isn't causing you problems with your workload. OYOH, I've seen database benchmarks with a 30% loss. Not exactly a desktop load, but certainly a realistic load for a server.
Depending on your hardware, are you sure you're not I/O bound? Try a load with significant I/O that is nevertheless CPU bound.
I'll bet Intel wouldn't characterize THAT 10% as insignificant.
Try an I/O heavy batch process. You'll notice.
I was just pointing out that this isn't the big nothing squiggleslash was claiming. The problem is real and the exploit is practical in several very large environments.
People not in those environments probably should have had a better way to sit back a few days and wait for bug reports.
Wrong again. Even with a short memory, you should remember that Al Frankin got drummed out.
If you're running on a VM in the cloud, it's not that hard for someone else to run an executable (in their own VM) on the same server. Meltdown can cross VMs.
That's why the big rush to a workaround patch.
What did the FBI forget about investigation since the smartphone era began? And why?
1. An honest day's work.
2. Work is so haRRRRRRRRRd.
Yes, in other words they found a replacement for the big corporate structure that worked as well or better. Note I never claimed one person would create a CPU.
I'm not so sure I want to trust my data to crappy software processes.