I thought the whole point of asymmetric keys is that you can send the "encode" key in band and keep the secret "decode" key yourself.
Yes, but assymetric encryption is slow, because you need about 5 - 10 times the key size to get the same level of security, and the algorithms are more complex. So in practice you only use it to encrypt a symmetric key, which you will use for the rest of the session.
How do you propose the key be sent out-of-band for web browsers?
The same way that 3DES and Blowfish keys are sent currrently.
I don't think this is acceptable as slashdot news, please pull it and post again in a couple of days. Twice.
Calm down, I remember reading about this story 2 weeks ago in MSM, so while it is early for Slashdot, it is not so early as to cause panic.
Sort of. That's only half of the problem. The other half is:
And one you missed, correct data for an inappropriate purpose. For example, data that has the location corrected to take you around the back of a building to the carpark entrance isn't very appropriate for an Uber driver/self-driving-car that needs to pick you up from the front door.
My phone has a large enough screen and a high enough resolution that I just prefer to browse the full site. Can we stop the "mobile web" shit?
In 1914, the first crossword puzzle was printed in a newspaper. The creator received $4000 down ... and $3000 across.