|
Ok, I've verified there are at least 6 matching ciphers on the two systems,
but unless I add the obsolete one:
ECDHE_RSA_AES_256_CBC_SHA384
The SSL handshake errors out when communicating with their web service.
I'm even more confused now. I would hate the solution to be having to add
the obsolete cipher to our side. That could mess things up in the future
for other applications that may use newer ciphers added with OS
upgrades/PTFs.
On Tue, May 19, 2020 at 3:51 PM B Stone <bvstone@xxxxxxxxx> wrote:
Gotcha.. thanks! I need to review their cipher list more closely I thinkciphers,
to see why there wouldn't be any matching ciphers on my V7R4 system and
their system (which I assume is *nix).
Bradley V. Stone
www.bvstools.com
MAILTOOL Benefit #22 <https://www.bvstools.com/mailtool.html>: Low Total
Cost of Ownership!
On Tue, May 19, 2020 at 2:48 PM Jack Woehr <
jwoehr@xxxxxxxxxxxxxxxxxxxxxxxx> wrote:
On Tue, May 19, 2020 at 1:09 PM B Stone <bvstone@xxxxxxxxx> wrote:
Then here's another question. If the server has a huge list of
notand the client does as well (where 10 out of 20 match), why would the(resulting
server settle on using a cipher that the client doesn't support
in a failed handshake) while there are many others that can be used?I wasn't entirely paying attention when this conversation started, so
seesure what's happening and what order it's happening in.
It could be a configuration that is trying to avoid downgrade attacks,
viathe article I cited on "vulnerabilities".
Or both of you could be confused about what you're actually supporting.
You might try going to the IFS in PASE and exploring the TLS exchange
receivedthe openssl s_client command
--
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
delete/destroythis communication in error, please contact the sender and
relatedall 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
--questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com
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 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.