Re: Protocol tls v 1.1

[Raul Jager <raul@xxxxxxxxxx>]

I already did.  I added some old ciphers in QSSLCSL seems that it
worked, next I changed QSSLPCL, but the old PC still can not access my
server, and in one of the SSL diagnostics it shows as disabled.

My favorite is
https://www.ssllabs.com/ssltest/analyze.html?d=i5.abc.com.py before
changes it reported A, but after changes reload just shows the cached page.

On 8/26/19 11:06 AM, Mark Waterbury wrote:
> 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?

-- Este e-mail fue enviado desde el Mail Server del diario ABC Color -- 
            -- Verificado por Anti-Virus Corporativo Symantec --