I do not see the " before my web address - does this mean my blog pages are unsecure and that a hacker can gain access to my photos, etc., plus place unwanted graphics images on my site? I recently had to go thru the necessary steps on my facebook account for a "secure" page.
I am a new blogger and am concerned about safety of my private information on my blogspot blog. WHy the Gmail Certification still non-EV SSL (Extended Validation SSL)? Great article on encryption decryption and https A browser that supports only DHE-RC4-SHA will *not* get forward secrecy because we don't support EDH for speed reasons.Īm I misunderstanding something, or is the aspect of the value of forward secrecy you mentioned a little bit silly? In some number of years, an adversary will be able to break the symmertric cipher keys directly, and then forward secrecy will be irrelevant. There's nothing Chrome or Firefox specific on the server side. We chose ECDHE because of the speed advantages: EDH in a 2048-bit group is plenty secure, but much slower.ģ) Any browser that supports ECDHE-RC4-SHA will get forward secrecy with Google HTTPS sites. Is there was an EDH-RC4 option on all browsers, could this have provided the feature that you wanted?ġ) Yes, the ECDHE key exchange is the part that provides the forward secrecy and ECDHE can be used with other ciphers, such as AES.Ģ) TLS also provides an option for EDH: ephemeral Diffie-Hellman in a multiplicative group. Doesn't the standard Diffie-Helman (Merkle) key exchange also provide perfect forward security? Did you feel that it was too slow or not secure enough?ģ. It's the key exchange that performs perfect forward security correct? If so, could one implement ECDHE with other symmetric cryptography such as AES?Ģ. I do have some questions as knowing your thoughts could help the community.ġ. It is sad that they don't implement these options. Thank you for bringing this to the attention of many website owners. So dropping key-stream output is something that we could implement, but it doesn't seem to offer any significant benefits for the specific case of HTTP over TLS. However, the plaintext at the beginning of the connection is already very well known (it's an HTTP request), and the same client doesn't encrypt the same data under very many keys. TLS 1.1 and 1.2 support is a nice-to-have that we hope to pick up in the future, although we have no firm plans yet.ĭropping key-stream output from RC4 helps avoid some known biases at the beginning of the connection. Thank you for adding fast security which is transparent to users. We hope to support IE in the future.)Īre you planning on moving to TLS 1.1 or TLS 1.2?Īre you planning on using an RC4 cipher that drops some packets to reduce the risk that the key can be recovered? Initially, only Chrome and Firefox will use it by default with Google services because IE doesn’t support the combination of ECDHE and RC4.
(* Chrome, Firefox (all platforms) and Internet Explorer (Vista or later) support forward secrecy using elliptic curve Diffie-Hellman. We would very much like to see forward secrecy become the norm and hope that our deployment serves as a demonstration of the practicality of that vision. Google’s forward secret connections will have a key exchange mechanism of ECDHE_RSA. You can check whether you have forward secret connections in Chrome by clicking on the green padlock in the address bar of HTTPS sites. We have also released the work that we did on the open source OpenSSL library that made this possible. An adversary that breaks a single key will no longer be able to decrypt months’ worth of connections in fact, not even the server operator will be able to retroactively decrypt HTTPS sessions.įorward secret HTTPS is now live for Gmail and many other Google HTTPS services(*), like SSL Search, Docs and Google+. In ten years time, when computers are much faster, an adversary could break the server private key and retrospectively decrypt today’s email traffic.įorward secrecy requires that the private keys for a connection are not kept in persistent storage. In other words, an encrypted, unreadable email could be recorded while being delivered to your computer today.
Most major sites supporting HTTPS operate in a non-forward secret fashion, which runs the risk of retrospective decryption. We are now pushing forward by enabling forward secrecy by default. We’re pleased to see that other major communications sites are following suit and deploying HTTPS in one form or another. Last year we introduced HTTPS by default for Gmail and encrypted search.