Re: V7R4 - Need to update Ciphers to use some outdated ones

I was going through Rob's old thread as it seems like a similar issue.
https://archive.midrange.com/midrange-l/201909/msg00227.html

Anyhow, I'm using my system as a proxy as a favor to a customer on V5R4.
This totally slipped my mind that the TLS 1.0 certificate on their site
would cause issues.

Anyhow, I was able to get around it using HTTP vs HTTPS for the callback to
their V5R4 system (I believe.. seems to be working now). This is just one
last customer on V5R4 that is updating in November and the only real place
that will have this issue (and it's frustrating...)

But of course now after mucking around with SST (which really needs
updating) and TLSCONFIG I probably want to get it back to what it was
before it causes other issues. Is there any "put it all back to stock"
commands for TLSCONFIG? lol Using that interface is a brain burner for
sure.

Bradley V. Stone
www.bvstools.com
GreenTools for G Suite/Google Apps <https://www.bvstools.com/g4g.html>:
Easy to use interfaces for GMail, Google Drive, Calendar, Contacts and
Cloud Print! <\body> <\html>

On Sun, Sep 29, 2019 at 12:09 PM B Stone <bvstone@xxxxxxxxx> wrote:

Well, one fun thing updating to V7R4 I found was that I need to use some
outdated ciphers.

The certificate in question has this information:

The connection to this site is encrypted and authenticated using TLS 1.0,
RSA, and AES_128_CBC with HMAC-SHA1.

Now, I updated QSSLPCL to use 1.3, 1.2, 1.1 and 1.0

I changed QSSLCSLCTL to *USRDFN

Now I just need to figure out what cipher(s) to add to QSSLCSL. Any ideas
there?

Bradley V. Stone
www.bvstools.com
MAILTOOL Benefit #15 <https://www.bvstools.com/mailtool.html>: The
ability to add a Footer to each email sent using an IFS stream file.