Re: GSKit SSL Handshake error 406 errno 3406 -- MIDRANGE-L

Subject: Re: GSKit SSL Handshake error 406 errno 3406
From: Jack Woehr <jwoehr@xxxxxxxxxxxxxxxxxxxxxxxx>
Date: Tue, 19 May 2020 12:46:19 -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 Tue, May 19, 2020 at 12:42 PM B Stone <bvstone@xxxxxxxxx> wrote:

I know this, Rob. Not really my question.

For some reason the admin of a site seems to think the ciphers used by
their SSL certificate are the ciphers set up on their system (similar to
QSSLCSL system value), not the ciphers used in the actual SSL certificate.

I was asking if I was misunderstanding something about the SSL handshake,
or they were. :)

Yes, you are misunderstanding.

The server and the client negotiate cyphers.

This is separate from the encryption and digest of the cert itself.

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: GSKit SSL Handshake error 406 errno 3406 , B Stone

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