This forum is closed to new posts and responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:

HCL Software Customer Support Portal for U.S. Federal Government clients
HCL Software Customer Support Portal


Oct 21, 2014, 3:35 PM
90 Posts

IBM Technotes with plans on addressing POODLE and SHA 2 support

  • Category: Domino Server
  • Platform: All Platforms
  • Release: 9.0.1,9.0
  • Role:
  • Tags:
  • Replies: 10
Oct 21, 2014, 7:08 PM
10 Posts
Do I understand correctly

I believe this is is saying that  TLS support will be in native Domino shortly - after a fix pack or 2. Can somebody please confirm my understanding.

For those of us mandated to get away from SSL 3.0 ASAP we can get new TLS certifcates and they will work with Domino with no need for proxy (IHS etc..)

This is great news if I am understanding correctly. Timeframe is still very important which is unclear.

TBear

 

 

Oct 21, 2014, 9:13 PM
43 Posts
You understand correctly.
You understand correctly. But the part about "TLS certificates" in your post is a little unclear. As per the technote, TLS 1.0 is the protocol we are adding natively to Domino for the latest fixpacks of 8.5.1 through 9.0.1. That will allow browsers configured with SSLv3 disabled and TLS 1.0 enabled to communicate with Domino.

The certs are a separate story. You can use existing SHA-1 certs with TLS 1.0.

Separately we plan on are releasing tools to allow SHA-2 importing. SHA-2 is restricted to 9.0 and above since it relies on cryptographic infrastructure introduce in 9.0. TLS supports SHA-2 as well.

Timeframe
We are keeping the time-frame somewhat vague as we go through the dev/test cycle. The technote states "Domino server Interim Fixes over the next several weeks". But we will keep the Design Partners up to speed.
Oct 22, 2014, 2:27 PM
10 Posts
Cetificates Clarification

Thank you Scott. Perhaps to clarify my certificate question I will just give the concrete example - as I am sure it will help others understand also.

Current status. Domino 9.01 server with SHA-1 certificate using SSL 3.0

Goal: Domino 9.x server with SHA-2 certificate using TLS

My guess at what to do:

1 - wait for announcemnt form IBM that fx pack is ready

2 - upgrade Domino

3 - TLS 1.0 is now supported

4 - Generate a new CSR for an SHA-2 certificate (using Dominio Server Certificate Admin?)

5 - Use CSR to request new certificate (SHA-2) from certificate authority and implement  

6 - SHA-2 now supported

How close am I?

 

TBear

 

Oct 22, 2014, 4:45 PM
90 Posts
TLS 1.0 is supported now
It just that it falls back to SSL 3.0 and there is no way to disable that fallback. That is what IBM is fixing in the POODLE hotfix.

This is what Firefox shows for our Domino site.



Howard
Oct 22, 2014, 7:34 PM
94 Posts
That's the cipherspec, not the protocol version.
The TLS_RSA_WITH_RC4_128_SHA cipherspec can be used with any version of the SSL/TLS protocol from SSLv3.0 to TLS v1.2.
Oct 22, 2014, 7:17 PM
94 Posts
Almost...
Current status. Domino 9.01 server with SHA-1 certificate using SSL 3.0

Goal: Domino 9.x server with SHA-2 certificate using TLS

My guess at what to do:

1 - wait for announcemnt form IBM that fx pack is ready

2 - upgrade Domino

3 - TLS 1.0 is now supported

Correct. No configuration changes will be necessary to enable TLS 1.0 beyond upgrading Domino.

4 - Generate a new CSR for an SHA-2 certificate (using Dominio Server Certificate Admin?)

We will provide directions on how to use OpenSSL to generate a new keypair and a new CSR.  Other techniques to generate a CSR may work, but will not be explicitly supported with SHA-2.  

You will also be able to use certreq.nsf and the Domino CA process to generate a keyring file with SHA-2 using your own Internet CA.

5 - Use CSR to request new certificate (SHA-2) from certificate authority and implement  

... and then use a new tool to create a new keyring file, import the keypair generated in #4, and import the certificate chain received from your CA.

6 - SHA-2 now supported

Correct.

Oct 31, 2014, 1:49 PM
5 Posts
The question is: WHEN

The only problem is item 1: How long will it take till the fix pack is ready?

IBM says "in the next several weeks". Several weeks can also be half a year.

TLS 1.0 is standard since 1999. IBM, did you sleep the last 15 years? Why wasn't it implemented much earlier?

We need a solution NOW, as SSL 3.0 will be shut down in webbrowsers soon.

And NO, IHS is NOT a solution. It has too many limitations that are unacceptable.

WAKE UP IBM AND FIX THIS!!!!! NOW!!!!!!

Nov 4, 2014, 6:10 PM
94 Posts
Went live on FixCentral yesterday for 40+ platforms and releases
The technotes at the top of this thread have been updated.

There are also links to the download site from the documentation in the Notes/Domino wiki:

IBM Domino Interim Fixes to support TLS 1.0 which can be used to prevent the POODLE attack
http://www-10.lotus.com/ldd/dominowiki.nsf/dx/IBM_Domino_TLS_1.0

Generating a SHA-2 Keyring file
http://www-10.lotus.com/ldd/dominowiki.nsf/dx/Domino_keyring

And more articles under the SHA-2 and TLS categories:

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

This forum is closed to new posts and responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:

HCL Software Customer Support Portal for U.S. Federal Government clients
HCL Software Customer Support Portal