Re: 7.4 ssl issue -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Subject: Re: 7.4 ssl issue
From: Jack Woehr <jwoehr@xxxxxxxxxxxxxxxxxxxxxxxx>
Date: Mon, 16 Sep 2019 17:16:17 -0600
List-archive: <https://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@lists.midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.lists.midrange.com>
List-post: <mailto:midrange-l@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=unsubscribe>

On Mon, Sep 16, 2019 at 5:13 PM Rob Berendt <rob@xxxxxxxxx> wrote:

Since this person is running an old 3-year certificate which expires next
month, and to them, tls 1.3 is a head scratcher, I have these system values:

QSSLCSLCTL*USRDFN

This one's interesting. It's the cipher control. Usually people leave it
*OPSYS ... is that all set up right?

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: 7.4 ssl issue , Jack Woehr
RE: 7.4 ssl issue , Rob Berendt

This mailing list archive is Copyright 1997-2024 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.