Notes on TLS/SSL 3.0 Intolerant Servers
A number of Netscape 6.x/7.x and Mozilla users have reported that some secure sites -- typically sites featuring online transactions or online banking over the https protocol -- do not display any content at all. The connection seems terminated and a blank page is displayed. This is the main symptom of the problem when Mozilla based browsers encounter TLS/SSL 3.0 intolerant servers.
There are some number of web servers in production today which incorrectly implement the SSL 3.0 specification. This incorrect implementation causes them to reject connection attempts from clients that are compliant with the SSL 3.0 and TLS (aka SSL 3.1) specifications.
Netscape 6.x/7.x and Mozilla browsers (0.9.1 and later versions) correctly implement the TLS specification, and the users cannot utilize sites which have this problem.
The SSL 3.0 and TLS (aka SSL 3.1) specs both contain a provision -- the same provision -- for
detecting "version rollback attacks". It is designed to permit a server to detect a man-in-the-middle that is
altering the SSL client hello (connection) requests as they pass from the client to the server, altering them by
changing the protocol version number to a lower version number. This feature was kind of meaningless until TLS
(SSL 3.1) came along because there was no version higher than 3.0 from which to be rolled back. TLS is now
available and used, and products that have implemented the roll-back detection incorrectly are not interoperable
with TLS/SSL spec-compliant clients. Normally the servers which have this problem are not equipped to deal with the
TLS protocol, but instead of rolling back to SSL 3.0 as the rollback provision provides, they terminate/drop the
connection, thus resulting in most cases a blank page display.
For up-to-date information, you can read a Bugzilla bug report which keeps track of this problem with Mozilla-based browsers. See Bug 59321.
How can users avoid this problem?:
- If you're using a version earlier than Netscape Preview Release 1, or Mozilla Release 0.9.1, these versions shipped with the TLS option turned ON as the default but with no way to deal with the problem servers. If you are using these old versions, please update to the latest Netscape or Mozilla versions. You can also avoid such a problem by editing an existing profile -- check the preference option setting at: Edit | Preferences | Privacy and Security | SSL | Enable TLS, and turn it OFF if it is ON for these earlier browsers.
- Netscape 6.1 (and later) (Mozilla 0.9.2 or later) shipped with the TLS option ON but also included a graceful rollback mechanism on the client side when they encounter known TLS/SSL 3.0 intolerant servers.
What servers are currently known to exhibit TLS/SSL 3.0 intolerant behavior?:
As of this writing, this problem has been reported for the following servers: (Wherever there is an upgraded version which fixes the problem, it is indicated by an asterisked remark in the parentheses. )
- Domino-Go-Webserver/220.127.116.11 (and perhaps some later versions.)
- IBM_HTTP_Server/18.104.22.168 or earlier (* Upgrade to 22.214.171.124 )
- IBM_HTTP_Server/126.96.36.199 or earlier (*Upgrade to 188.8.131.52 )
- Java Web Server 2
- OSU/3.2 - DECthreads HTTP server for OpenVM
- Webmail v. 3.6.1 by Infinite Technologies (Upgrade available )
N.B. There might be servers other than those listed above which exhibit this problem. If you find such a server, please let us know through a feedback address you find on this page. We will include it in an update to this document. For up-to-date information, you can read this Bugzilla bug which keeps a list of TLS/SSL 3.0 intolerant servers.
If you're the administrator of a web site running TLS/SSL 3.0 intolerant server(s), what should you do?:
- Upgrade to a newer version if available, which corrects this problem. ( See the above list for the info.) There will be other network clients which implement TLS/SSL 3.0 specification correctly and have a problem with your site. Let's not perpetuate the problem servers.
- Contact the manufacturer and inquire if there is a new version available which fixes this problem,.
- Post a note on your site instructing users of old versions of browsers like Netscape 6.0/6.01/6.1 Preview Release 1 and Mozilla 0.9.1 and earlier to turn OFF the TLS option at: Edit | Preferences | Privacy and Security | SSL | Enable TLS. However, this is a temporary workaround at best. We recommend strongly that you urge users to upgrade to the latest Netscape version (or at least Netscape 6.1 or later) since the newer versions have the graceful rollback implemented in the code.
- If you have questions concerning Netscape browsers and problem servers, please contact us using the
feedback address at the top of this page.
How do you know you are experiencing TLS/SSL 3.0 intolerant servers?:
Because newer versions of Netscape and Mozilla have built-in workaround for the problem servers, it is now unlikely that you will experience this problem. But if you're running Netscape 6.0/6.01/6.1 PR 1or Mozilla build (prior to 6/11/2001), you should look out for the symptom described below. You may also run this test with versions later than the older versions of Netscape 6.x or Mozilla -- just in case code changes in Netscape 6.1/Mozilla 0.9.2 or later may not catch all problem servers.
- When you find a secure site which simply does not display any page content or drops the connection, check to see if the preference option,
- Edit | Preferences | Privacy and Security | SSL | Enable TLS
is turned ON. If so, turn it OFF.
- Now re-visit the problem site. If the content displays this time, you are most likely witnessing a TLS/SSL 3.0 intolerant server.
- (Optional: Go visit http://www.netcraft.com/sslwhats/ and paste in the HTTPS URL and find out what SSL server the site is running.)
- Report such a problem --> see the next section.
What should you do if you find a server which has this problem on Netscape 6.0/6.01/6.1 PR 1 & Mozilla (prior to 6/11/2001) browsers or later versions of the same browsers ?:
- Add the information on such a server to this bug report at Bugzilla. (Note: You will be asked to provide your email address before you can file a bug at Bugzilla.)
- Or send your finding to the feedback address you find on this page.