The www-10.lotus.com environment uses a network manager that supports TLS 1.2, so that is why you're seeing it. The TLS support in IF1 for native Domino is currently TLS 1.0.
 

Hello,

Thanks for your response. Am I the only person severely frustrated/disappointed with the lack of transport security in Domino? TLS 1.2 was released in 2008 and IBM just scrambled to add TLS 1.0, the initial release from 1999, because of Google's <et al.> pressure tactics!?! Who's defining standards these days? I expect IBM to be at the forefront. This is incredibly disappointing. Have a great day.

***Why does the network manager support TLS 1.2 and not Domino? It sounds like a lack of support for the product line.

Regards,
Michael

...and I'm equally (or more) disappointed in the instructions to use the darn fix(es)! This is terrible!

http://www-10.lotus.com/ldd/dominowiki.nsf/dx/3rd_Party_SHA-2_with_OpenSSL_and_kyrtool

I know I must be spoiled that the old method was fairly easy, but (and I'm sure like many other admins), I only have to request certificates every couple years - this method is terrible! What about an actual workable solution? I don't have a linux box laying around to work with - Running thru this process I have know Idea what I'll end up with!

First of all, thanks for updating http://www-10.lotus.com/ldd/dominowiki.nsf/dx/3rd_Party_SHA-2_with_OpenSSL_and_kyrtool !

I understand that OpenSSL _IS_ available for Windows; my frustration lies in the fact the the only 'documented' procedure now for obtaining certificates is an example of using a linux tool, there are no examples of using the Windows version, which has its own idiosyncrasies.

I feel a little more confident after reading Michael's notes, and hope to submit my certificate requests today, and will report back..

Thanks!