Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[ADSM\-L\]\s+TSM\s+V8\.1\.2\s+upgrade\s+and\s+not\s+use\s+SSL\/TLS12\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[ADSM\-L\]\s+TSM\s+V8\.1\.2\s+upgrade\s+and\s+not\s+use\s+SSL\/TLS12\s*$/: 2 ]

Total 2 documents matching your query.

1. [ADSM-L] TSM V8.1.2 upgrade and not use SSL/TLS12 (score: 1): Author: Bill Boyer <bjdboyer AT COMCAST DOT NET>; Date: Fri, 15 Sep 2017 15:10:31 -0400; I have a V6.3.5 TSM server (Linux) that I've "cloned" to another system for testing. I've upgraded it to V8.1.2 and now all my clients fail to connect with back-level client code or certification iss; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2017-09/msg00046.html (8,451 bytes)
2. Re: [ADSM-L] TSM V8.1.2 upgrade and not use SSL/TLS12 (score: 1): Author: Remco Post <r.post AT PLCS DOT NL>; Date: Sat, 16 Sep 2017 20:01:55 +0200; I believe the answer is: not. TLS is forced upon us with TSM 8.1.2. Despite other advantages, this is the one reason Im not rushing to implement 8.1.2. There are too many unknown factors and things; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2017-09/msg00048.html (9,273 bytes)

Current List: 1 - 2
Page: [1]