RE: SSL ciphers

Pete,

Now you have me wondering.
So are all the pieces related, Cert, SSL ver, cipher, etc.
I wish I could find a better link that explains the cipher selection, or someone explain how this whole process works.
This was the best link I found thus far.

http://www-01.ibm.com/support/knowledgecenter/SSFKSJ_7.1.0/com.ibm.mq.doc/sy10660_.htm?lang=en

Paul



-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Pete Helgren
Sent: Wednesday, April 22, 2015 3:51 PM
To: Midrange Systems Technical Discussion
Subject: Re: SSL ciphers

"The certificate and the cipher have nothing to do with one another. "

Hmmm. News to me then. My understanding was that we needed to request a new Certificate from Comodo. Current certificate shows that it supports Signature algorithm SHA1RSA with a Signature hash algorithm of SHA1. Which is why Chrome flags our website with the red slash on our SSL connection. My understanding was that that the SHA1 cert would only negotiate a SHA1 cipher request (so the cipher and cert WERE related) so I guess I need to do more reading.....

Pete Helgren
www.petesworkshop.com
GIAC Secure Software Programmer-Java


On 4/22/2015 12:20 PM, Tim Bronski wrote:

The certificate and the cipher have nothing to do with one another.

On 4/22/2015 7:12 PM, Steinmetz, Paul wrote:

Could/would the iSeries WC cert affect the cipher negotiation?
I still have a SHA 1 WC cert, the new SHA 256 WC cert not yet enabled.

Pa

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.