Twitter Implements Forward Secrecy For Connections
Fnord666 writes with this excerpt from Tech Crunch "Twitter has enabled Perfect Forward Secrecy across its mobile site, website and API feeds in order to protect against future cracking of the service's encryption. The PFS method ensures that, if the encryption key Twitter uses is cracked in the future, all of the past data transported through the network does not become an open book right away. 'If an adversary is currently recording all Twitter users' encrypted traffic, and they later crack or steal Twitter's private keys, they should not be able to use those keys to decrypt the recorded traffic,' says Twitter's Jacob Hoffman-Andrews. 'As the Electronic Frontier Foundation points out, this type of protection is increasingly important on today's Internet.'"
Of course, they are also using Elliptic Curve ciphers.
So they switch to SSL? Thats kind of the point of the DH exchange in SSL. Stealing the key later still doesn't get you access to the data since the DH exchange ensures that neither side ever transmits enough information to derive the key.
Persistent Volume manager for Kubernetes - https://github.com/dwimsey/openshift-pvmanager
My account was hacked and the hacker made a FOOL out of me!
I would tweet, "I just went to the bathroom."
And the hacker would post, "And took a HUGE #shit".
Can you believe it!
It's a good thing because with all these insightful and important posts on Twitter, the last thing we need are hackers and security agents destroying the value of Twitter! And it also destroys the further value of the Internet!
Twitter is completely open to anyone. So, what's the point of encryption? Similarly, what's the point of warrants and subpoenas for account information?
It's all there in the open for anyone to read.
In boundaries of my imagination, the user account password is pretty much the only private data that Twitter stores.
only the persons you prefer can read your twits
why bother when all it takes is a NSA letter for them to do whatever is required of them ? its not like they have a choice
unless they and their servers/business registration leave USA this is nothing but a PR attempt (much like MS and their outlook.com) , until you stop the NSA and the USA stalker culture this is a worthless gesture and does nothing to "secure" anything
That new Slashdot interface is a monstrosity. Also it's slow as fuck. Who needs 2.0 and cloud anyways ? Bring the fun back you insensitive clod !
GO FUCK OFF THE PLANET NOW
Hey thanks for spending your time to Google and post the results of research that I don't give enough of a fuck about to ever bother with. It increases my understanding without taxing me with any sort of effort at all. That's just how I like it.
Why don't you Google something important for me this time?
TTFN
I recommend Calomel SSL Validation to anyone who's interested in the security of their SSL/TLS connections. It adds a toolbar button, the color of which is determined by a weighted, composite score based on various connections security parameters: Bit-lengths, algos (e.g., AES > RC4), PFS, handshake/protocol, domain matching, etc. Clicking the button displays the complete break-down, including a percentage-score for overall connection security.
There's also a Tools menu dialog that allows one to toggle >=128 bit, >=256 bit, PFS, and/or FIPS connections exclusively, among other security and interface tweaks.
Along the same lines, I also recommend CipherFox, which has a configurable status-bar display of symmetric/asymmetric algos and their bit-lengths, and the hash function used in a secure connection. CipherFox also allows RC4 to be toggled, which is handy in conjunction Calomel.
The above are all freeware that appear to be written and published by individuals lacking a nefarious corporate agenda.
Thank you, Edward Snowden.
"Arguments from authority are worthless." —Carl Sagan
I just checked gmail.com with Calomel SSL Validation (thanks to cffrost's post ) and it appears gmail uses PFS as well. How come this wasn't news?
Isn't the whole point of Twitter to post nearly meaningless snippets of text that you want everyone to see?
Encryption seems pointless for Twitter so this seems more like a PR move than anything meaningful.
While the NIST curves are suspect, slow, and problematic in a number of other ways, there are fast and safe elliptic curves.
There are two ciphers family that will provide PFS: DHE (Diffie-Hellman Exchage) and ECDHE (Elliptic Curve DHE). Having PFS enabled for all modern browsers is just about the server offering both families with appropriate priorities, so that clients pick a PFS enabled cipher. Qualys SSL server test is a good tool for checking for an appropriate configuration, although it could make clearer that you cannot both have PFS for modern browsers, and protect against BEAST server-side.
Note that the Elliptic Curve used in ECDHE is not the one that was claimed to be compromised by NSA. We have no information suggesting ECHDE is at risk