On 08/06/2017 18:52, Peter Bowen wrote:
On Thu, Jun 8, 2017 at 9:38 AM, Jakob Bohm via dev-security-policy
wrote:
As the linked proposal was worded (I am not on Blink mailing lists), it
seemed obvious that the original timeline was:
Later: Once the new roots are generally accepted, Symante
On Thu, Jun 8, 2017 at 9:38 AM, Jakob Bohm via dev-security-policy
wrote:
>
> As the linked proposal was worded (I am not on Blink mailing lists), it
> seemed obvious that the original timeline was:
>
> Later: Once the new roots are generally accepted, Symantec can actually
> issue from the new
On 08/06/2017 11:09, Gervase Markham wrote:
On 07/06/17 22:30, Jakob Bohm wrote:
Potential clarification: By "New PKI", Mozilla apparently refers to the
"Managed CAs", "Transition to a New Symantec PKI" and related parts of
the plan, not to the "new roots" for the "modernized platform" / "new
in
On 07/06/17 22:30, Jakob Bohm wrote:
> Potential clarification: By "New PKI", Mozilla apparently refers to the
> "Managed CAs", "Transition to a New Symantec PKI" and related parts of
> the plan, not to the "new roots" for the "modernized platform" / "new
> infrastructure".
I expect those things t
Hi Gervase,
there seems to be a slight inconsistency between the terminology in the
plan posted at
https://groups.google.com/a/chromium.org/d/msg/blink-dev/eUAKwjihhBs/ovLalSBRBQAJ
And the official letter quoted below. I have added potential
clarifications to fix this, please indicate, for
5 matches
Mail list logo
