Just as an update - it appears that there was a vhost config that went unnoticed - this from the guy who found it: Looking against the config being included in the Apache when started we found a vhost file which had shared the same IP listener. This was a site migrated from the platform under a different domain (yyy.xxx.xxx.domain), so the SSL attached to this vhost was expired (possibly the SHA1) but getting considered as part of the TLS negotiation alongside the existing certificate for xxx.xxx.xxx.domain (which was SHA2)." From: Pedro Coelho Silva <coelhop24@xxxxxxxxx>
Sent: Friday, October 13, 2023 5:42 AM To: users@xxxxxxxxxxxxxxxx <users@xxxxxxxxxxxxxxxx> Subject: Re: Peer digest using sha1 on TLS connection - Chrome fails
Is the CA cert signed with SHA-1? If so, you can try to check if the CA has a cross-signed CA cert with SHA2 you can use for the customer's current certificate chain or just tell your customer to reissue the cert with a full SHA2 chain.
Best Regards
/P
--
--
On Thu, 12 Oct 2023 at 04:27, Craig H Silva (Cenitex) <Craig.Silva@xxxxxxxxxxxxxxxxxx.invalid> wrote:
Notice: This email and any attachments may contain information that is personal, confidential, legally privileged and/or copyright. No part of it should be reproduced, adapted or communicated without the prior written consent of the copyright owner. It is the responsibility of the recipient to check for and remove viruses. If you have received this email in error, please notify the sender by return email, delete it from your system and destroy any copies. You are not authorised to use, communicate or rely on the information contained in this email. Please consider the environment before printing this email. |