Firefox 36: "No longer accept insecure RC4 ciphers whenever possible” https://www.mozilla.org/en-US/firefox/36.0/releasenotes/ …
-
-
Replying to @ivanristic
@ivanristic Better: "Tries to handshake w/ RC4 cipher suites disabled and falls back to handshaking w/ RC4 cipher suites enabled, like IE."1 reply 5 retweets 0 likes -
Replying to @BRIAN_____
@BRIAN_____@ivanristic We’re not going to get things like https://identity.virginmedia.com/ fixed until there’s an interstitial or it breaks.1 reply 0 retweets 0 likes -
Replying to @Nick_Lowe
@BRIAN_____@ivanristic https://www.ssllabs.com/ssltest/analyze.html?d=identity.virginmedia.com … I’ve tried contacting the company but they’re dysfunctional/incompetent. Hand needs forcing.2 replies 0 retweets 0 likes -
Replying to @Nick_Lowe
@Nick_Lowe@ivanristic I think you need@vyv03354.1 reply 0 retweets 0 likes -
Replying to @BRIAN_____
@BRIAN_____@ivanristic Point I wanted to make: Isn’t it about time to get an interstitial in Firefox and Chrome before fallback occurs?1 reply 0 retweets 0 likes
@Nick_Lowe @ivanristic emk is working on further limiting RC4 fallback in Fx38. Stopping non-secure fallback is needed first, in Fx37.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.