Same with DigiCert. This is a sub CA issued by Verizon. We've reached out to the customer to investigate why they had the issue and what they are doing to remediate. We will provide details once we receive them.
-----Original Message----- From: dev-security-policy [mailto:dev-security-policy-bounces+jeremy.rowley=digicert.com@lists.mozilla .org] On Behalf Of Rick Andrews Sent: Monday, February 1, 2016 11:34 AM To: mozilla-dev-security-pol...@lists.mozilla.org Subject: Re: More SHA-1 certs On Sunday, January 31, 2016 at 9:47:53 AM UTC-8, Peter Bowen wrote: > These are all in the last week > > Sub-CA under SHECA (which has applied to be in the Mozilla program) > https://crt.sh/?id=12367776&opt=cablint > > Sub-CA under DigiCert > https://crt.sh/?id=12460684&opt=cablint > > Sub-CA under Symantec > https://crt.sh/?id=12456194&opt=cablint > https://crt.sh/?id=12434313&opt=cablint The Sub-CA under Symantec is managed by one of our customers. We've reached out to them and we're investigating. More detail to follow. _______________________________________________ dev-security-policy mailing list dev-security-policy@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-security-policy
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ dev-security-policy mailing list dev-security-policy@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-security-policy
