Re: Telia CA - incorrect OID value

2018-08-05 Thread Lewis Resmond via dev-security-policy
Am Freitag, 3. August 2018 10:51:34 UTC+2 schrieb pekka.la...@teliasonera.com: > Steps to fix: > 1. fix the DV profile; DONE 25-Jun-2018, no errors occurred after that > 2. reproduce all incorrect certificates any provide those to Customer; > ONGOING, planned to finnish 30-Sep-2018 > 3. revoke all

Re: localhost.megasyncloopback.mega.nz private key in client

2018-08-05 Thread Alex Cohn via dev-security-policy
The certificate [1] in the GitHub link you posted was issued by Comodo, not by GeoTrust. The two share a private key, though, so both the Comodo and GeoTrust certs should be considered compromised at this point. I've added the Comodo-issued cert to several CT logs for tracking, and I'm CCing ssl_ab

Re: Telia CA - problem in E validation

2018-08-05 Thread Ryan Sleevi via dev-security-policy
On Fri, Aug 3, 2018 at 3:53 AM pekka.lahtiharju--- via dev-security-policy < dev-security-policy@lists.mozilla.org> wrote: > Incident report: > > PROBLEM IN SUBJECT E (email) VALUE VALIDATION (deviation 5) > Telia got a preliminary CA audit report on 25th June 2018. One of its BR > deviations was

Re: Telia CA - incorrect OID value

2018-08-05 Thread Ryan Sleevi via dev-security-policy
On Fri, Aug 3, 2018 at 3:51 AM pekka.lahtiharju--- via dev-security-policy < dev-security-policy@lists.mozilla.org> wrote: > Indident reports: > > ERROR IN DV OID VALUE (deviation 4) > > How Telia became aware: > Telia got preliminary CA audit report on 25th June 2018. One of its BR > deviations w