Re: P-521 Certificates

2019-01-08 Thread Jakob Bohm via dev-security-policy
Adding some data points for use by future readers of this thread.

On 08/01/2019 03:26, Corey Bonnell wrote:
> (Posting in a personal capacity as I am no longer employed by Trustwave)
> 
> Mozilla Root Store Policy section 5.1 
> (https://www.mozilla.org/en-US/about/governance/policies/security-group/certs/policy/)
>  prohibits the use of P-521 keys in root certificates included in the Mozilla 
> trust store, as well as in any certificates chaining to these roots. This 
> prohibition was made very clear in the discussion on this list in 2017 at 
> https://groups.google.com/forum/#!msg/mozilla.dev.security.policy/7O34-DmZeC8/fsKobHABAwAJ.
> 

This is Message-Id
   
Dated 2017-Jun-27 with Subject "P-521" and starts an approximately 2 
week long thread where arguments were made for and against reinstatating 
P-521.  Arguments were weak on both sides, but the "keep banning P-521" 
side was chosen at the end.

As noted by others, the ban was checked into draft policy on 2017-Feb-20 
and took effect upon publication on 2017-Feb-28 .  There was no explicit 
transition rule for existing certificates, thus certificates issued 
before 2017-Feb-28 are presumably exempt until their normal expiry.

> Below is a list of unexpired, unrevoked certificates which contain P-521 
> public keys (grouped by CA Owner and ordered by notBefore):
> 
> Sectigo
> crt.sh URL, notBefore, notAfter, issuer CN
> --
> https://crt.sh/?id=6371802, 2015-01-23, 2020-01-22, COMODO ECC Domain 
> Validation Secure Server CA
> https://crt.sh/?id=13764502, 2015-10-17, 2019-01-16, COMODO ECC Domain 
> Validation Secure Server CA
> https://crt.sh/?id=308269873, 2016-10-22, 2019-10-09, COMODO ECC Domain 
> Validation Secure Server CA
> https://crt.sh/?id=307896586, 2017-01-23, 2019-01-23, COMODO ECC Domain 
> Validation Secure Server CA
> https://crt.sh/?id=308306899, 2017-01-27, 2020-01-27, COMODO ECC Domain 
> Validation Secure Server CA
> https://crt.sh/?id=308113189, 2017-03-22, 2020-03-06, InCommon ECC Server CA
> https://crt.sh/?id=307650153, 2017-03-26, 2020-03-25, COMODO ECC Domain 
> Validation Secure Server CA
> https://crt.sh/?id=307656068, 2017-04-20, 2020-07-18, COMODO ECC Organization 
> Validation Secure Server CA
> https://crt.sh/?id=307534525, 2017-05-18, 2020-05-18, COMODO ECC Domain 
> Validation Secure Server CA
> https://crt.sh/?id=308201491, 2017-06-27, 2020-06-26, COMODO ECC Domain 
> Validation Secure Server CA
> https://crt.sh/?id=292253731, 2017-12-31, 2019-12-31, COMODO ECC Domain 
> Validation Secure Server CA
> https://crt.sh/?id=325088752, 2018-02-07, 2019-02-07, Gandi Standard SSL CA 2
> https://crt.sh/?id=495848274, 2018-02-25, 2019-02-25, COMODO ECC Domain 
> Validation Secure Server CA
> https://crt.sh/?id=363803336, 2018-03-23, 2020-05-23, COMODO ECC Domain 
> Validation Secure Server CA
> https://crt.sh/?id=369709685, 2018-03-29, 2019-04-28, COMODO ECC Domain 
> Validation Secure Server CA
> https://crt.sh/?id=369824505, 2018-03-29, 2020-03-25, COMODO ECC Domain 
> Validation Secure Server CA
> https://crt.sh/?id=377999330, 2018-04-05, 2020-04-04, COMODO ECC Domain 
> Validation Secure Server CA
> https://crt.sh/?id=395687551, 2018-04-14, 2019-04-29, COMODO ECC Domain 
> Validation Secure Server CA
> https://crt.sh/?id=441476932, 2018-04-14, 2019-04-29, COMODO ECC Domain 
> Validation Secure Server CA
> https://crt.sh/?id=419677583, 2018-04-25, 2020-04-24, COMODO ECC Domain 
> Validation Secure Server CA
> https://crt.sh/?id=419685986, 2018-04-25, 2020-04-24, COMODO ECC Domain 
> Validation Secure Server CA
> https://crt.sh/?id=441178023, 2018-05-05, 2019-05-05, COMODO ECC Domain 
> Validation Secure Server CA
> https://crt.sh/?id=441178000, 2018-05-05, 2019-05-05, COMODO ECC Domain 
> Validation Secure Server CA
> https://crt.sh/?id=447475737, 2018-05-07, 2020-05-06, COMODO ECC Domain 
> Validation Secure Server CA
> https://crt.sh/?id=447484644, 2018-05-07, 2020-05-06, COMODO ECC Domain 
> Validation Secure Server CA
> https://crt.sh/?id=453793669, 2018-05-10, 2019-05-10, COMODO ECC Domain 
> Validation Secure Server CA
> https://crt.sh/?id=453793685, 2018-05-10, 2019-05-10, COMODO ECC Domain 
> Validation Secure Server CA
> https://crt.sh/?id=455176361, 2018-05-11, 2019-05-11, COMODO ECC Domain 
> Validation Secure Server CA
> https://crt.sh/?id=455176321, 2018-05-11, 2019-05-11, COMODO ECC Domain 
> Validation Secure Server CA
> https://crt.sh/?id=463185238, 2018-05-15, 2019-05-15, USERTrust ECC Domain 
> Validation Secure Server CA
> https://crt.sh/?id=463092619, 2018-05-15, 2019-05-12, USERTrust ECC Domain 
> Validation Secure Server CA
> https://crt.sh/?id=463092603, 2018-05-15, 2019-05-12, USERTrust ECC Domain 
> Validation Secure Server CA
> https://crt.sh/?id=463185322, 2018-05-15, 2019-05-15, USERTrust ECC Domain 
> Validation Secure Server CA
> https://crt.sh/?id=499794005, 2018-06-01, 2020-02-29, COMODO ECC Domain 
> Validation Secure Server CA
> https://crt.sh/?i

Re: P-521 Certificates

2019-01-08 Thread Wayne Thayer via dev-security-policy
Thanks Corey, Ryan, and Jonathan.

In one of the bugs that Ryan created, the CA stated that it's not clear if
or when Mozilla requires revocation of these P-521 certificates. I believe
the answer is that we do not require revocation. Our policy (section 6)
explicitly requires CAs to abide by the BR revocation rules (section
4.9.1.1), but these certificates do not meet any of those requirements.

- Wayne

On Tue, Jan 8, 2019 at 11:30 AM Jonathan Rudenberg via dev-security-policy <
dev-security-policy@lists.mozilla.org> wrote:

> On Mon, Jan 7, 2019, at 21:26, Corey Bonnell via dev-security-policy wrote:
> > (Posting in a personal capacity as I am no longer employed by Trustwave)
> >
> > Mozilla Root Store Policy section 5.1
> > (
> https://www.mozilla.org/en-US/about/governance/policies/security-group/certs/policy/)
>
> > prohibits the use of P-521 keys in root certificates included in the
> > Mozilla trust store, as well as in any certificates chaining to these
> > roots. This prohibition was made very clear in the discussion on this
> > list in 2017 at
> >
> https://groups.google.com/forum/#!msg/mozilla.dev.security.policy/7O34-DmZeC8/fsKobHABAwAJ.
>
> >
> > Below is a list of unexpired, unrevoked certificates which contain P-521
> > public keys (grouped by CA Owner and ordered by notBefore):
>
> I've created https://misissued.com/batch/43/ to track these.
> ___
> dev-security-policy mailing list
> dev-security-policy@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-security-policy
>
___
dev-security-policy mailing list
dev-security-policy@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-security-policy


Re: P-521 Certificates

2019-01-08 Thread Jonathan Rudenberg via dev-security-policy
On Mon, Jan 7, 2019, at 21:26, Corey Bonnell via dev-security-policy wrote:
> (Posting in a personal capacity as I am no longer employed by Trustwave)
> 
> Mozilla Root Store Policy section 5.1 
> (https://www.mozilla.org/en-US/about/governance/policies/security-group/certs/policy/)
>  
> prohibits the use of P-521 keys in root certificates included in the 
> Mozilla trust store, as well as in any certificates chaining to these 
> roots. This prohibition was made very clear in the discussion on this 
> list in 2017 at 
> https://groups.google.com/forum/#!msg/mozilla.dev.security.policy/7O34-DmZeC8/fsKobHABAwAJ.
>  
> 
> Below is a list of unexpired, unrevoked certificates which contain P-521 
> public keys (grouped by CA Owner and ordered by notBefore):

I've created https://misissued.com/batch/43/ to track these.
___
dev-security-policy mailing list
dev-security-policy@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-security-policy


Re: P-521 Certificates

2019-01-08 Thread Ryan Sleevi via dev-security-policy
Thanks Corey for reporting these.

As you note, this policy came in to force with Policy 2.4, which as noted
in https://wiki.mozilla.org/CA/Root_Store_Policy_Archive , had a compliance
date of February 28, 2017. This was also part of a CA Communications item -
https://ccadb-public.secure.force.com/mozillacommunications/CACommResponsesOnlyReport?CommunicationId=a05o03WrzBC&QuestionId=Q00022,Q00029

I've opened the following bugs, based on the CAs listed:
Sectigo: https://bugzilla.mozilla.org/show_bug.cgi?id=1518553
DigiCert: https://bugzilla.mozilla.org/show_bug.cgi?id=1518555
Asseco DS / Certum: https://bugzilla.mozilla.org/show_bug.cgi?id=1518560

On Mon, Jan 7, 2019 at 9:55 PM Corey Bonnell via dev-security-policy <
dev-security-policy@lists.mozilla.org> wrote:

> (Posting in a personal capacity as I am no longer employed by Trustwave)
>
> Mozilla Root Store Policy section 5.1 (
> https://www.mozilla.org/en-US/about/governance/policies/security-group/certs/policy/)
> prohibits the use of P-521 keys in root certificates included in the
> Mozilla trust store, as well as in any certificates chaining to these
> roots. This prohibition was made very clear in the discussion on this list
> in 2017 at
> https://groups.google.com/forum/#!msg/mozilla.dev.security.policy/7O34-DmZeC8/fsKobHABAwAJ.
>
>
> Below is a list of unexpired, unrevoked certificates which contain P-521
> public keys (grouped by CA Owner and ordered by notBefore):
>
> Sectigo
> crt.sh URL, notBefore, notAfter, issuer CN
> --
> https://crt.sh/?id=6371802, 2015-01-23, 2020-01-22, COMODO ECC Domain
> Validation Secure Server CA
> https://crt.sh/?id=13764502, 2015-10-17, 2019-01-16, COMODO ECC Domain
> Validation Secure Server CA
> https://crt.sh/?id=308269873, 2016-10-22, 2019-10-09, COMODO ECC Domain
> Validation Secure Server CA
> https://crt.sh/?id=307896586, 2017-01-23, 2019-01-23, COMODO ECC Domain
> Validation Secure Server CA
> https://crt.sh/?id=308306899, 2017-01-27, 2020-01-27, COMODO ECC Domain
> Validation Secure Server CA
> https://crt.sh/?id=308113189, 2017-03-22, 2020-03-06, InCommon ECC Server
> CA
> https://crt.sh/?id=307650153, 2017-03-26, 2020-03-25, COMODO ECC Domain
> Validation Secure Server CA
> https://crt.sh/?id=307656068, 2017-04-20, 2020-07-18, COMODO ECC
> Organization Validation Secure Server CA
> https://crt.sh/?id=307534525, 2017-05-18, 2020-05-18, COMODO ECC Domain
> Validation Secure Server CA
> https://crt.sh/?id=308201491, 2017-06-27, 2020-06-26, COMODO ECC Domain
> Validation Secure Server CA
> https://crt.sh/?id=292253731, 2017-12-31, 2019-12-31, COMODO ECC Domain
> Validation Secure Server CA
> https://crt.sh/?id=325088752, 2018-02-07, 2019-02-07, Gandi Standard SSL
> CA 2
> https://crt.sh/?id=495848274, 2018-02-25, 2019-02-25, COMODO ECC Domain
> Validation Secure Server CA
> https://crt.sh/?id=363803336, 2018-03-23, 2020-05-23, COMODO ECC Domain
> Validation Secure Server CA
> https://crt.sh/?id=369709685, 2018-03-29, 2019-04-28, COMODO ECC Domain
> Validation Secure Server CA
> https://crt.sh/?id=369824505, 2018-03-29, 2020-03-25, COMODO ECC Domain
> Validation Secure Server CA
> https://crt.sh/?id=377999330, 2018-04-05, 2020-04-04, COMODO ECC Domain
> Validation Secure Server CA
> https://crt.sh/?id=395687551, 2018-04-14, 2019-04-29, COMODO ECC Domain
> Validation Secure Server CA
> https://crt.sh/?id=441476932, 2018-04-14, 2019-04-29, COMODO ECC Domain
> Validation Secure Server CA
> https://crt.sh/?id=419677583, 2018-04-25, 2020-04-24, COMODO ECC Domain
> Validation Secure Server CA
> https://crt.sh/?id=419685986, 2018-04-25, 2020-04-24, COMODO ECC Domain
> Validation Secure Server CA
> https://crt.sh/?id=441178023, 2018-05-05, 2019-05-05, COMODO ECC Domain
> Validation Secure Server CA
> https://crt.sh/?id=441178000, 2018-05-05, 2019-05-05, COMODO ECC Domain
> Validation Secure Server CA
> https://crt.sh/?id=447475737, 2018-05-07, 2020-05-06, COMODO ECC Domain
> Validation Secure Server CA
> https://crt.sh/?id=447484644, 2018-05-07, 2020-05-06, COMODO ECC Domain
> Validation Secure Server CA
> https://crt.sh/?id=453793669, 2018-05-10, 2019-05-10, COMODO ECC Domain
> Validation Secure Server CA
> https://crt.sh/?id=453793685, 2018-05-10, 2019-05-10, COMODO ECC Domain
> Validation Secure Server CA
> https://crt.sh/?id=455176361, 2018-05-11, 2019-05-11, COMODO ECC Domain
> Validation Secure Server CA
> https://crt.sh/?id=455176321, 2018-05-11, 2019-05-11, COMODO ECC Domain
> Validation Secure Server CA
> https://crt.sh/?id=463185238, 2018-05-15, 2019-05-15, USERTrust ECC
> Domain Validation Secure Server CA
> https://crt.sh/?id=463092619, 2018-05-15, 2019-05-12, USERTrust ECC
> Domain Validation Secure Server CA
> https://crt.sh/?id=463092603, 2018-05-15, 2019-05-12, USERTrust ECC
> Domain Validation Secure Server CA
> https://crt.sh/?id=463185322, 2018-05-15, 2019-05-15, USERTrust ECC
> Domain Validation Secure Server CA
> https://crt.sh/?id=499794005, 2018-06-0