在 2016年10月21日星期五 UTC+8上午12:15:00，Han Yuwei写道：
> 在 2016年10月20日星期四 UTC+8上午5:27:42，Andrew R. Whalley写道：
> > Hello,
> >
> > Thank you for the links. I note, however, that there's at least one
> > difference between the native language version and the English translation:
> >
> >
在 2016年10月21日星期五 UTC+8上午10:52:42，Percy写道：
> Thanks for bringing the discrepancy into our attention.
> Even the cover page of the English and Chinese version of CPS are dated
> differently.
>
> English
> Global Digital Cybersecurity Authority
> CO., LTD.
> Certification Practice Statement (CPS)
Thanks for bringing the discrepancy into our attention.
Even the cover page of the English and Chinese version of CPS are dated
differently.
English
Global Digital Cybersecurity Authority
CO., LTD.
Certification Practice Statement (CPS) Version: V4.3
Effective Date: July 1, 2016
Chinese
On Thursday, October 20, 2016 at 6:59:08 PM UTC-7, Percy wrote:
> Kathleen,
> As most users affected by this decision are Chinese, will you be able to make
> the blog post available in Chinese on the security blog as well? You can ask
> the Chinese firefox community or me to translate.
>
> As
Kathleen,
As most users affected by this decision are Chinese, will you be able to make
the blog post available in Chinese on the security blog as well? You can ask
the Chinese firefox community or me to translate.
As I stated earlier, there are almost no news of the distrust of
On 20/10/16 15:05, Kathleen Wilson wrote:
> You are receiving this email because our records indicate that there
> are non-technically-constrained intermediate certificates that chain
> up to your root certificates that are included in Mozilla’s program
> that have not been entered into the CA
On Thursday, October 20, 2016 at 2:24:19 PM UTC-7, Florian Weimer wrote:
>
> Does this requirement apply transitively sub-CAs of sub-CAs?
>
> It may make sense to stress explicitly that the “technically
> constrained” refers to properties visible in the certificates
> themselves, not technical
* Kathleen Wilson:
> The following was stated in Mozilla’s March 2016 CA Communication
> (https://wiki.mozilla.org/CA:Communications#March_2016):
> Beginning with Version 2.1 of Mozilla's CA Certificate Policy, for any
> certificate which directly or transitively chains to the root
> certificates
All,
I have filed the following two bugs.
WoSign Action Items:
https://bugzilla.mozilla.org/show_bug.cgi?id=1311824
StartCom Action Items:
https://bugzilla.mozilla.org/show_bug.cgi?id=1311832
I will work on a security blog that will probably get posted early next week.
It will point to these
All,
Next week I expect to have a better capability for sending notification emails
to CAs. The first email I would like to try this new tool on is regarding the
CAs who have not disclosed all of their non-technically-constrained
intermediate certificates in the CA Community in Salesforce (aka
On 19/10/16 15:13, okaphone.elektron...@gmail.com wrote:
> Perhaps "haste" is not what you want here. How about "urgency"?
I was using it in the sense of the English phrase "more haste, less speed":
http://dictionary.cambridge.org/dictionary/english/more-haste-less-speed
But yes, urgency is
在 2016年10月20日星期四 UTC+8上午5:27:42，Andrew R. Whalley写道：
> Hello,
>
> Thank you for the links. I note, however, that there's at least one
> difference between the native language version and the English translation:
>
> http://www.gdca.com.cn/cps/cps version 4.3 has a section 4.2.4 covering
> CAA.
12 matches
Mail list logo
