Re: Namecheap refused to revoke certificate despite domain owner changed

2018-06-04 Thread Jakob Bohm via dev-security-policy
On 01/06/2018 21:01, Wayne Thayer wrote: On Fri, Jun 1, 2018 at 5:06 PM Jakob Bohm via dev-security-policy < dev-security-policy@lists.mozilla.org> wrote: Please contact the CA again, and inform them that BR 4.9.1.1 #6 requires the CA (not some reseller) to revoke the certificate within 24

Re: Namecheap refused to revoke certificate despite domain owner changed

2018-06-04 Thread Jakob Bohm via dev-security-policy
On 01/06/2018 22:39, Joanna Fox wrote: In light of the limited visibility of WHOIS, Wayne's suggestion of "... allow anyone to revoke by proving that they control the domain name using one of the BR 3.2.2.4 methods" is preferable as it is a bit more encompassing rather than restricting to to

Re: Plan to update CCADB PEM extraction tool

2018-06-04 Thread Kathleen Wilson via dev-security-policy
I would like to replace the old "Certificate ID" field with the following two fields, because they are useful in different situations, and the new field names are clear about what the values are. SPKI SHA256 Subject + SPKI SHA256 Also, I am seeing differences in the following fields for a

Re: OISTE WISeKey Global Root GC CA Root Inclusion Request

2018-06-04 Thread Pedro Fuentes via dev-security-policy
Kind reminder. Thanks! ___ dev-security-policy mailing list dev-security-policy@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-security-policy

Re: Disallowed company name

2018-06-04 Thread James Burton via dev-security-policy
This company only cost £10. £6 for the incorporation. £4 for sending in NE01 form to Companies House. On Mon, 4 Jun 2018 at 08:58, Jeremy Rowley via dev-security-policy < dev-security-policy@lists.mozilla.org> wrote: > Punctuation differences are not enough to register a name in the us, or at >

Re: Disallowed company name

2018-06-04 Thread Jeremy Rowley via dev-security-policy
Punctuation differences are not enough to register a name in the us, or at least in the jurisdictions here I’m aware of. > On Jun 4, 2018, at 1:04 AM, Ryan Hurst via dev-security-policy > wrote: > > I apologize, I originally wrote in haste and did not clearly state what I > was suggesting.

Re: Disallowed company name

2018-06-04 Thread Ryan Hurst via dev-security-policy
I apologize, I originally wrote in haste and did not clearly state what I was suggesting. Specifically, while it is typical for a given jurisdiction (state, etc) to require a name to be unique, it is typically not a requirement for it to not be so unique that it can not be confused for another