On Wednesday, March 2, 2016 at 5:11:43 PM UTC-8, Kathleen Wilson wrote:
> 
> To summarize this discussion:
> 
> 1) HARICA plans to update their CP/CPS in May-June of this year, and 
> incorporate the updates that they indicated in this discussion. I plan 
> to track that action item in parallel of the inclusion process.
> 
> 2) Dimitris provided further information about how HARICA performs 
> domain validation, but I do not expect them to modify the validation 
> rules in their CP/CPS until after the BRs are updated in this regards.
> 
> 3) There was a separate discussion regarding the output of the certlint 
> tests that found that these new root certificates have serial number 00. 
> That sparked discussion in the CAB Forum, which I think will address 
> this moving forward. I believe this is not a show stopper for this 
> particular root inclusion request.
> 
> Therefore, it is my intention to close this discussion and recommend 
> approval in the bug.
> 
> Please let me know if I missed anything that needs to be address before 
> moving forward with approval of this request.
> 
> Thanks,
> Kathleen

I sent the following earlier today, but it hasn't shown up yet, so trying 
again...

Thanks to all of you who reviewed and commented on this request from HARICA to 
include the "Hellenic Academic and Research Institutions RootCA 2015" and 
"Hellenic Academic and Research Institutions ECC RootCA 2015" root 
certificates, and enable the Websites and Email trust bits for both roots.

I am not aware of any issues that would prevent us from moving forward with 
this request. Therefore, I will recommend approval in the bug.

https://bugzilla.mozilla.org/show_bug.cgi?id=1201423

The action item to update the CP/CPS will be tracked in the bug, in parallel 
with the rest of the inclusion process.

Any further follow-up on this request should be added directly to the bug.

Thanks,
Kathleen


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

Reply via email to