Obsolete Cipher Suite Message
-
@tonyshowoff said
In this case there really is no difference as confusing as that is, but I don't see SHA-1 there, instead SHA-2 (256)
This is what I am seeing...
-
@BRRABill said in Obsolete Cipher Suite Message:
@tonyshowoff said
In this case there really is no difference as confusing as that is, but I don't see SHA-1 there, instead SHA-2 (256)
This is what I am seeing...
That's SHA-2 (TLS 1.2 uses this), message authentication is a different aspect of it, in the simplest terms, it's to avoid corrupt messages.
-
So in my original post, what is Chrome having an issue with?
-
@BRRABill said in Obsolete Cipher Suite Message:
So in my original post, what is Chrome having an issue with?
In TLS 1.2 if it's not using the ECDHE with GCM it is obsolete according to Chrome. If the signature, however, uses SHA-1, Chrome I don't even think will just accept it without going red or whatever. I think that's where some confusion comes from, the cipher of the protocol itself versus the signature of the certificate.
-
So the net net here is that it is probably OK, but should be upgraded if possible?
-
@BRRABill Yes
-
Now THIS is the kind of chatter this thread deserved, LOL.
