Ryan,

GlobalSign certificate issuance has been referenced in several different 
threads recently and I think most of them are closed; however, if you feel 
otherwise, let me know.

Suspicious Test certificate
https://groups.google.com/forum/#!topic/mozilla.dev.security.policy/-gaS1p3vrXc
I provided a formal response in that thread that I believe closes this issue.

Incapusla certifciates with SANs for domains that don't currently exist
https://groups.google.com/forum/#!topic/mozilla.dev.security.policy/l1mDdCL8LlU
This is not an issue as all SANs were validated in accordance with the BRs when 
the domain was verified, thus no formal response is needed.

And lastly this ticket.  The Domain name was validated in accordance with the 
BRs, but there was a bug that allowed a user entered space to be included in 
some of the SAN values.  While the value is not compliant with RFC 5280 or the 
BRs, there was no security issue with the certificate that was issued (it was 
likely not able to secure the intended subdomains).  We'll provide an incident 
report for this.

If this isn't sufficient for some reason, I'm sure you will let us know.

Doug

On Tuesday, February 28, 2017 at 1:06:57 PM UTC-5, Ryan Sleevi wrote:
> On Tue, Feb 28, 2017 at 8:53 AM, douglas.beattie--- via dev-security-policy
> <[email protected]> wrote:
> 
> >
> > Yes, we're working to do just this now.
> 
> 
> While that's good and well, I do hope GlobalSign will produce an incident
> report regarding this matter, as to how the situation in
> https://groups.google.com/d/msg/mozilla.dev.security.policy/luxlU5TL2ew/qkL1ZdThAQAJ
> came to be in the first place.
> 
> I think GoDaddy's recent explanation -
> https://groups.google.com/d/msg/mozilla.dev.security.policy/Htujoyq-pO8/uRBcS2TmBQAJ
> - may provide a model for GlobalSign here.
> 
> The intent is that we don't just deal with the symptom, but that we work to
> understand the root cause, the scope of impact, and the opportunities for
> improvement.
> 
> I look forward to reading GlobalSign's analysis of both this and other
> recent issues.

_______________________________________________
dev-security-policy mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-security-policy

Reply via email to