Slashdot videos: Now with more Slashdot!
We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).
How would I implement it? Huh!
You can initiate SSL/TLS where by the only party presenting a certificate is the server to the client.
Do you think that all HTTPS clients present a certificate to the HTTPS server ? This is not how HTTPS usually works, only rare systems that are using client side SSL certificate for authentication use it. But your standard credit card transaction or login portal does not present any certificate to the server.
With STARTTLS sending you start unencrypted, enable TLS via STARTTLS command, then perform some kind of authentication inside the secure TLS channel (this can be plaintext authentication inside TLS). Now you proceed to use the SMTP have both setup a secure channel and authenticated.
The problem is simple to fix, make it cost them CPU computation time.
Implement an SMTP Client <> SMTP Server cookie system, where by an adhoc association can be established between two systems, that the client can represent an arbitrary token to help build trust and reputation around it (or simply use IP address or SSL certificate hash).
Next define a mathematical problem that is cheap (in CPU cost) to setup and verify, but hard for the SMTP client to compute, forcing it to brute force the problem (this making the client pay the greater CPU cost). This needs to scale both linear and exponential.
Allow the server to define the problem to solve and the scale of the challenge, this more trusted clients have a cheap problem, brand new clients get hit with a harder CPU problem.
Built it all into the SMTP protocol.
Now the server is in complete control of the cost a particular client must pay to send the message, the client can decide to accept the cost or bounce the message.
Now sending from a ADSL link, from a foreign country or from a well known virtual host provider can all be scaled accordingly until the point SPAM becomes too expensive to rent enough server capacity.
The opportunity of making a news story at just the moment someone in the US was confirmed as having the strain, is more a marketing ploy to ensure the company with the goods is getting attention and their phone ringing. Better to have your phone ringing offering you government money than your competitors phone ringing because some government official happens to know someone in that industry.
Is the vaccine production ready for the general population, hell no!
Did I tell you I have a perpetual energy machine that is "in development" ?
Did you see "Attack of the clones"
No need to persuade many people of your tyrannical view point over many generations to build that army.
This is also why it is funny when people say that pension funds hold their stock for a long term view.
But what can happen is the two pension funds collude to exchange assets with each other (zero sum game) over a period of time, so the fee levied for any transfers can be taken by all the snouts in the transaction cost trough. Yes if you stand back and look at the week to week they look like their are holding their positions a for the long game, but actually they found a way to extract additional profits to pay pension pot "fund managers" their bonuses.
It only makes compression useless for the "Cookie" header which is exactly what is needed to defeat CRIME.
All security sensitive data like this should be able to be trivially fuzzed. Maybe a better scheme would be to implement:
Fuzz-Cookie: $version=1; $foobar="123"; $random-nonce-1="192jsk232"; SESSIONID="0123456789secretXOREDresultHER"; $random-nonce-99="982kmn323"; $fuzzed="SESSIONID";
NOTE: Its been a while since I looked at a Cookie header directly, there are probably some major syntax mistakes in the above example.
Now you can extend it to any other kind of header using a common key and transformation technique, by prefixing headers with Fuzz-* and writing an RFC/IETF document on how the key is applied to which parts and when of the header value data.
Your suggestion of disabling compression in SSL/TLS support is already implemented.
A business called "BT Wholesale / aka OpenReach" operates as a corporate entity in its own right, that the government regulates. They more of less have last mile monopoly over the old British Telecom (which used to be the incumbent single telephone operator that was originally a public entity). So this was made private maybe 20 years ago but with certain caveats.
Such as a uniform pricing policy to all other telecom operators wishing to buy their wholesale services. Think like FRAND, as opposed to scheming and back office deals to maintain pricing.
Such as not offering the full package, i.e. only offering wholesale services. A regular home or business consumer never buys directly anything from the wholesale division. The end customer buys from the many (more than 500 in our little island) brand names, who in turn pay the wholesale rental fees out of your subscription.
Such as allowing politicians to have influence (through regulation) over certain aspects of governance. This is a good thing when there is a last mile monopoly, there is at least some kind of elected accountability. Especially when the government paid for the original construction of the network.
There is of course a parallel cable network now, that also have their own independent last mile. So in almost all urban/suburban locations another option exists, but BTs copper POTS network has a much higher coverage.
There also exists some areas (such as Kingston and Hull) which ended up with their own last mile services that operate their own telecoms independently.
Here in the UK now (with BT wholesale) the whole country is getting more street side cabinets (to within of 100 meters of every urban and suburban location) and fibre optics installed to those cabinets back to the local exchange site. The last 100 meters is still largely delivered over copper but at speeds around 80MBit/20Mbit, but I'm sure further speed increases will take places like ADSL/ADSL2/ADSL2+ in the future. This national roll out is over half way through and I'm sure within the next 3 years the original plan will be complete.
There are still issues with many rural locations being on dialup quality, hopefully as cellular like technology improves this could be utilized as back haul for rural locations. Rural in the UK might mean just being 8 miles out of town.
Just add an XOR string to the Cookie header, that is applied against the other data fields. This XOR itself can change each time a Cookie header is emitted. Now you have a non-repeating, pseudo random input for the compressor to work on. But the other party can apply a transform to the Cookie header to get back original data.
For good measure also add an additional Random-Nonce-Field-1="random-length-data" which is simply ignored and discarded by the other end. Now you can perterb the compressor in both directions, by applying a completely useless to the attacher the same data (allow it to compress) but also a Random-Nonce-Field-2 which might be different for each header, like the XOR but completely useless and to be ignored data.
Now it is upto the researches to use these tools (added to a Cookie spec change) to come up the most CPU cost efficient way to utilize them to make CRIME and other such attacks not viable.
Or maybe I am missing something glaring here ?
While retrospective regulation on old cars is a political matter (pissed of public force to comply) the regulations affecting brand new cars is not. This is a matter for the auto industry to solve and the public don't care.
Retrospective regulations changes (that affect a significant number of the population) are rare events.
Plus there is that small matter of driving on the correct side of the road (that we do). So this does influence the which hand drive the car is.
Neither suggests access was explicitly or implicitly DENIED to third parties.
All someone else was doing was taking a photo of you.
Oh you have a Terms & Conditions document in your back pocket do you!
robots.txt is great and all, but someone did actually sit there pressing a button for each website hit, the button generated a random number and this number was used to randomize the delay and User-Agent data. It was under 2500 hits after all, sheesh I can hit ebay that many times just by browsing their catalogue for an hour.
* verification (checking a read to all copies and CRC validates correctly as expected)
* scrubbing (writing some other random patterns to each block of the disk, to confirm the disk is in good order, and will take new data, it also re-energises the disk, the original data is then written back into the block, and then verified, before it moves on to another part of the disk, this operation often requires battery backed memory, since the original data is preserved robustly this way over unwanted power outage).
Ideally you should verify (the whole storage) at least once per week, and scrub (the whole storage) once per month. These operations with hardware cards can be performed slowly in the background, but often a few hours a day during offpeak will do the job.
Doing this alone can extend the life of disks, compared to writing some block of data, no accessing it for 5 years, then wondering why in 5 years time the block is no corrupted.
Both these operations provide a better health check of RAID than SMART along, since SMART only knows of a problem after it saw a problem, and that often requires you to access the problem area of disk. This is what verification/scrubbing does on your behalf continuously over a week.