×

Good News Everybody!

A new search engine is coming soon.

As a stop gap measure, we are using Google's custom search engine service.



  1.  Home
  2. WEB400
  3. August 2019

Re: Protocol tls v 1.1

Raul,


Issue WRKSYSVAL QSSL*


Notice QSSLCSLCTL -- change that from *OPSYS to *USRDFN to tell the system you are taking responsibility for setting and maintaining the list of approved ciphers.


Once you no longer need TLS 1.1, you can then change it back to *OPSYS.


Hope that helps.


Mark S. Waterbury



On Monday, August 26, 2019, 10:54:30 AM EDT, Raul Jager <raul@xxxxxxxxxx> wrote:


In v7.4 the only protocols enabled are 1.2 and 1.3

Some clients are behind and as a temporary solution I plan to enable v
1.1, I added v 1.1 in QSSLPCL
and in the DCM, but the validator only sees 1.2 and 1.3

I have restarted the server, but no difference.

My server is at https://i5.abc.com.py

Any ideas?




As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow-Ups:
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2026 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.