Information Security Stack Exchange is a question and answer site for information security professionals. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I've been wondering lately if RC4 is so flawed in all its forms, why is it that it is still being supported by all major browsers per default? Why does the typical chrome browser prefer ECDHE-ECDSA-RC4128-SHA over ECDHE-ECDSA-AES128-SHA?

share|improve this question
up vote 6 down vote accepted

RC4 has known biases, which have been measured with great accuracy. Exploiting these biases into an actual attack requires observation of many (millions) of successive connections where some specific secret data (say, a given password) always appears at the same place. Such a scenario can be forced in lab conditions but barely applies to practical, real-life situations. This is why it is usually considered "not urgent" to obsolete RC4.

Some SSL clients prefer RC4 over AES because of all the bad press about the BEAST attack (despite the fact that the same clients are not actually vulnerable to BEAST).

share|improve this answer
What about the recent rumors about practical attacks on RC4? – scai Dec 20 '13 at 10:29
The results from March 2013 indicate an attack which requires about 16 millions of connections to uncover a few secret bytes. That's rarely practical. The rest of the rumours is just that: rumours. E.g. I heard that Elvis Presley is still alive and works for the NSA. – Tom Leek Dec 20 '13 at 12:20

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.