× 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.



Then here's another question. If the server has a huge list of ciphers,
and the client does as well (where 10 out of 20 match), why would the
server settle on using a cipher that the client doesn't support (resulting
in a failed handshake) while there are many others that can be used?

I hope I'm getting this across correctly.

In this case it would require me to change my IBM i SSL settings to user
defined and adding obsolete ciphers to my SSL list... why is it asking to
use this cipher and not another that we both support?


On Tue, May 19, 2020 at 2:04 PM B Stone <bvstone@xxxxxxxxx> wrote:

So you're saying the ciphers used by the SSL certificate have no bearing
in the negotiation?

On Tue, May 19, 2020 at 1:46 PM Jack Woehr <
jwoehr@xxxxxxxxxxxxxxxxxxxxxxxx> wrote:

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.


--
Jack Woehr
Absolute Performance, Inc.
12303 Airport Way, Suite 100
Broomfield, CO 80021

NON-DISCLOSURE NOTICE: This communication including any and all
attachments is for the intended recipient(s) only and may contain
confidential and privileged information. If you are not the intended
recipient of this communication, any disclosure, copying further
distribution or use of this communication is prohibited. If you received
this communication in error, please contact the sender and delete/destroy
all copies of this communication immediately.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com



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-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.