Mozilla, Google, and Microsoft will disable RC4

[half-moon]

http://www.ghacks.net/2015/09/03/mozill ... arly-2016/

Read and smile!

[LimboSlam]

Will we do this, or is disabling it good enough?

[megaman]

The good: We might get sites that are en-par with us about not needing RC4.
The bad: Sites might still take time to get there.

[Moonchild]

It's about time they finally move forward with this!
I hope they enjoy the smoother ride with us paving part of the way with a number of higher-profile sites already having been forced to look at it due to Pale Moon users

Will we do this, or is disabling it good enough?

We've already disabled it early this year.
I don't see a reason to completely yank out the cipher. It's good for emergencies to be able to use it as a temporary fallback, and RC4 is far from as vulnerable as the other issues addressed recently (POODLE and Logjam); breaking the cipher isn't trivial or a (near-)real-time option.

How about now, VirginMedia? Will you respond this time?

[chreid]

Re VM: thanks for keeping an eye on that particular bugbear. I certainly am!

I warned them about this likelihood months ago: "As browsers finally implement current security protocols [by disabling RC4/implementing TLS1.2 and secure reneg etc] then no-one will be able to log in to VM without using insecure browsers. [If IE disabled RC4, which they should have done months ago, VM would act immediately]".

[Moonchild]

I warned them about this likelihood months ago:

I've said that this was going to happen - I just expected the "big players" to move a little faster than a year of latency; but it was inevitable. But apparently nobody of those sites took my word for it. I don't just pull this out of my... hat, you know?

[lyceus]

The good: We might get sites that are en-par with us about not needing RC4.
The bad: Sites might still take time to get there.

Correction:
The bad: Government sites might still take years to get there, as they rely in the lowest browser from Microsoft: MSIE 8. So is a long mile ahead.