Domino on Linux/Unix, Troubleshooting, Best Practices, Tips and more ...

Domino TLS 1.0 SHA-2 Support to prevent POODLE has been shipped today

Daniel Nashed  4 November 2014 01:14:16


As blogged before IBM was already working on addressing the POODLE attack by finally implementing TLS 1.0 for all internet protocols.


Today IBM shipped an Interims Fix to introduce TLS 1.0 which is very important because many browsers and other software vendors are about to drop SSL 3.0 support.

So you need those fixes to continue to use secure protocols like HTTS, secure SMTP, LDAP, IMAP, POP3, DIIOP..


There are a couple of changes which are described in the following Wiki documents. And there are a couple of additional Wiki documents providing additional information.


Basically this fix will allow TLS 1.0 and also allows you to use SHA-2 based certificates with a new introduced command-line key-ring tool called "kyrtool".

The tool is a command line application that can manage your keyring files with SHA-2 support and you don't need the old ikeyman tool that many of us used before with all those limitations.

I have been testing the tool on Windows and Linux and it is working like a charm. The Wiki contains step by step instructions how to use it in combination with openssl to generate a private key, signing requests and import trusted roots and certficates.


You find very detailed step by step documentation in the referenced links.


And you can start downloading the fix and the kyrtool today!
I have it already running on my production Traveler server on Linux 64.


Here are the details including download links and detailed descriptions.


For TLS 1.0 support you just need to install the hotfix and all the defaults should just work fine. You need no additional settings.

Note: IBM did not disable SSL 3.0 for compatibility reasons in this fist step. The first IF is intended to introduce TLS 1.0 to allow all applications to continue to work with Domino.


Domino with this fix prevents a downgrade attacks if the client requested TLS 1.0. Some applications will still report that your server is vulnerable to POODLE because Domino still supports SSL 3.0 but this is not completely true. That's just a basic check for SSL 3.0.


IMHO introducing TLS 1.0 in combination with preventing downgrade protocol attacks is the right first move.

The fixes are available for  all supported platforms and releases (9.0.1 FP2, 9.0, 8.5.3 FP6, 8.5.2 FP4, 8.5.1 FP5).


But you should be aware that SHA-2 is only available in Domino 9.0.x because 8.5.x releases "lack the cryptographic infrastructure for SHA-2. "



Thanks to IBM and specially the security team who did a great job in a very short time!

They have been already working on TLS and SHA-2 support before but had to change their plans because of the short term move to diable SSL 3.0 in browsers and other software.


Here is the official quite detailed IBM documentation for TLS, SHA-2, the new key-ring tool "kyrtool" and information about how IBM addressed the "POODLE attack" with this fix.


-- Daniel



IBM Domino Interim Fixes to support TLS 1.0 which can be used to prevent the POODLE attack

http://www.lotus.com/ldd/dominowiki.nsf/dx/IBM_Domino_TLS_1.0

Generating a SHA-2 Keyring file

http://www.lotus.com/ldd/dominowiki.nsf/dx/Domino_keyring

IBM will add more articles in these categories around troubleshooting, tracing, and so on.


http://www.lotus.com/ldd/dominowiki.nsf/xpViewTags.xsp?categoryFilter=SHA-2
http://www.lotus.com/ldd/dominowiki.nsf/xpViewTags.xsp?categoryFilter=TLS
Comments

1Christian Henseler  04.11.2014 9:37:20  Domino TLS 1.0 SHA-2 Support to prevent POODLE has been shipped today

Big thank you to IBM :-)

2Andrew Pollack  05.11.2014 3:21:51  Domino TLS 1.0 SHA-2 Support to prevent POODLE has been shipped today

Careful though. If you connect to the server using scripting or shell tools like Python or wget or curl, the TLS 1.0 patch will break those connections over ssl.

3ISMAIL KHAN   05.11.2014 8:40:20  Domino TLS 1.0 SHA-2 Support to prevent POODLE has been shipped today

Hi Daniel,

I hope this hotfix can be applied to IBM Notes Traveler too. There should not be any impact on the device SYNC level issue right after SSL to TLS update.

Thanks & Regards

Ismail khan

4Daniel Nashed  05.11.2014 10:31:12  Domino TLS 1.0 SHA-2 Support to prevent POODLE has been shipped today

Yes absolutely the fix should be also applied to Traveler servers -- specially if they are directly connected to the internet without a secure proxy in front of it.

I am running it on my production Traveler server but only test iOS devices yet.

5Daniel Nashed  05.11.2014 10:32:27  Domino TLS 1.0 SHA-2 Support to prevent POODLE has been shipped today

@Andrew, I saw your post already and I have reproduced it on my server and sent it along with SSL debug output from my server to IBM.

For me it is hard to say where the problem is. Browsers can connect just fine and they should also try TLS 1.2 first.

-- Daniel

6SABARISH KUMARAN  05.11.2014 12:30:01  Domino TLS 1.0 SHA-2 Support to prevent POODLE has been shipped today

Hi Daniel,

We have not enforced http to https in the server document. Will there be any issue on the android client device after applying this interim fix for IBM Notes Traveler.

How about for Traveler HA pool on applying this Interim fix

Thanks

7Daniel Nashed  05.11.2014 14:18:25  Domino TLS 1.0 SHA-2 Support to prevent POODLE has been shipped today

On Traveler the same rules apply as usual. Just update all servers one after another.

But you could also wait until Traveler 9.0.1 IF7 is available and patch Domino and Traveler at the same time!

I would always use a HTTPS only configuration. On Android there are issues downloading the client software over not trusted certs depending on the browser -- but that is nothing new.

For Android I cannot say if all versions will continue to work without issues. I assume all current Android versions do at least support TLS 1.0 but I have not tested that.

I have personally tested Android 4.0.4 which continued to work with TLS 1.0 only

8Martin Garrels  06.11.2014 8:54:55  Domino TLS 1.0 SHA-2 Support to prevent POODLE has been shipped today

@Daniel:

Google starts the TLS 1.0 support with Android 2.3.7

9Daniel Nashed  06.11.2014 10:28:34  Domino TLS 1.0 SHA-2 Support to prevent POODLE has been shipped today

@Martin, thanks!

Did you test connecting to Traveler against a server that only supports TLS 1.0 and higher (proxy)?

The devil could be in the details in those cases. Even if code supports TLS 1.0 depending on protocol negotiation and the ciphers supported could cause issues.

-- Daniel

10Devendra  07.11.2014 6:36:45  Domino TLS 1.0 SHA-2 Support to prevent POODLE has been shipped today

Hi Daniel,

Any changes in the latest IF1 for poodle attack?Can

u provide expected timelines for the release of Traveler 9.0.1 IF7 .

11Panu Haaramo  12.11.2014 17:36:23  Domino TLS 1.0 SHA-2 Support to prevent POODLE has been shipped today

I installed the IF on 9.0.1FP2 and Chrome still uses SSLv3 and says TLS is not supported on that server.

How do I disable SSLv3 on Domino server to force TLS always?

12Daniel Nashed  12.11.2014 19:46:15  Domino TLS 1.0 SHA-2 Support to prevent POODLE has been shipped today

it's currently not support to disable SSL3.0 with IF1.

does it work for other browsers?

-- Daniel

13Panu Haaramo  12.11.2014 20:08:27  Domino TLS 1.0 SHA-2 Support to prevent POODLE has been shipped today

We were able to verify with a tool that TLS 1.0 is now enabled. I have know idea why Chrome prefers SSLv3.

Have I missed something because this is my understanding: If SSLv3 is enabled on server then the server is vulnerable. There is no point to enable TLS if you do not shut down SSL.

14Daniel Nashed  12.11.2014 21:05:39  Domino TLS 1.0 SHA-2 Support to prevent POODLE has been shipped today

The first step is to support TLS 1.0 and to prevent downgrade attacks if a client requests TLS 1.0.

The main goal of this first fix is to ensure that all browsers and applications continue to work when SSL 3.0 is disabled.

IMHO we need a step by step approach. First ensure that everytone does support TLS 1.0 at least before shutting down SSL 3.0 support completely.

I agree that the next step is to disable SSL 3.0 to avoid the risk for the POODLE attack completely.

So it is important right now that a client/browser requests TLS 1.0

-- Daniel

Archives


  • [IBM Lotus Domino]
  • [Domino on Linux]
  • [Nash!Com]
  • [Daniel Nashed]