What version of FF shipped with 128-bit encryption?
And which versions can suport it but didn't ship with it? We want to stop allowing weak-encryption for our SSL sites. Thanks.
Additional System Details
- User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; MS-RTC LM 8)
Mozilla Suite, Firefox, and Thunderbird support up to 256-bit encryption, read here for more informations:
and here, cor-el, the-edmeister and James replies:
Thanks, I saw both of those links but I don't think they answer my question. I'm looking for backwards compatability so that I can tell my Manager which versions support 128-bit and with which version did it start coming already enabled.
Do all versions support it?
Firefox supported 256-bit encryption in versions further back than anyone should be using these days. I can't recall exactly when it started, but Firefox 2.0 had it.
256 bit AES support started with Mozilla Suite 1.3 (Mar 12, 2003) and Firebird 0.6 (May 17, 2003), so 128 bit support shouldn't be a problem with any Firefox version.
Modified by cor-el
cor-el, Thanks for the help. That's exactly what I needed. Dave
For some weird reason, Home Depot thinks not. At some point -- I don't remember what I had requested -- it popped up this:
Minimum System Requirements
Your privacy and security are important to us. That’s why we require you to use a browser with 128-bit security encryption to proceed with your application. This protection helps to ensures that the information you send and receive will remain confidential.
Check your browser to verify it meets minimum system requirements.
Clicking "Check your browser" gives me this:
According to our test, your browser is not equipped to support 128-bit encryption. We suggest you upgrade your browser to ensure you can access secure sites.
I have Ffox 8.0, WinXPPro v5.1, SP3. ... Hmm, Ffox is offering an update. Let's see what happens.
If websites complain about 128 bit encryption not available then that can be caused by the "U;" that is no longer present in the user agent of Firefox 4+ versions.
- bug 572668 - Remove the crypto strength token from the UA string
Firefox supports 256 bit encryption ciphers since Firefox 2 was released in 2002.