This article discusses changes that affect security in Firefox 2.
Firefox 2 disables SSLv2 and the weak "export" cipher suites (those with key lengths less than 64 bits) by default, in favor of SSLv3. This provides improved security.
The preferred encryption methods are
TLS_RSA_WITH_3DES_EDE_CBC_SHA. Some servers refer to these as
If SSLv2 support must be enabled, it can be by setting the appropriate
security.ssl2.* user preferences to
- Firefox 2 supports Elliptic Curve Cryptography in TLS. Support is presently limited to curves of 256, 384, and 521 (yes, 521) bits.
- Firefox 2 supports the TLS server name indication extension to facilitate secure connections to servers hosting multiple virtual servers on a single underlying network address, as per RFC 3546.
- When Firefox 2 makes an OCSP request to validate a web server's certificate, it now uses the proxy that has been configured for normal HTTP traffic.
As always, you can find out what ciphers are supported — and which are enabled or disabled — by going to about:config and searching on "ssl" or "tls".
In order to correct a potential security problem when using the
jar: protocol, it's now necessary to serve JAR files with the MIME type
application/java-archive. See Security and the jar protocol for further details.