The updated CP/CPS are now under internal review and will be published
before end of February.
Thanks,
M.D.
On 2/8/2016 8:00 PM, Kathleen Wilson wrote:
On 2/7/16 2:53 AM, winpackja...@gmail.com wrote:
And how much more time is this going to take? Since no issues have
been highlighted...
W
On 2/7/16 2:53 AM, winpackja...@gmail.com wrote:
And how much more time is this going to take? Since no issues have been
highlighted...
We're waiting for SSC to update their CP/CPS to resolve the issues that
were raised here:
https://groups.google.com/d/msg/mozilla.dev.security.policy/W0st0
And how much more time is this going to take? Since no issues have been
highlighted...
___
dev-security-policy mailing list
dev-security-policy@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-security-policy
Thank you for your comments.
Let me start with your questions first.
RS-Q1:
"From interpreting Section 3.1.1, it would appear that a TLS server
certificate (e.g. DVCP, OVCP, EVCP, EVCP+) will never have a commonName
field appear within the subject, as the commonName is expressly
identified a
Dear Ryan,
thank you for your constructive criticism, suggestions and recommendations.
This is just a short confirmation that we are working on the feedback
which we expect to post in a couple of days.
All the best,
M.D.
On 8/29/2015 4:16 AM, Ryan Sleevi wrote:
On Wed, July 29, 2015 1:34 pm
On Wed, July 29, 2015 1:34 pm, Kathleen Wilson wrote:
> SSC has applied to include three root certificates as follows: enable
> the email trust bit for the âSSC GDL CA VS Rootâ certificate; enable
> the
> code signing and email trust bits for the âSSC GDL CA Root Aâ
> certificate; and
SSC has applied to include three root certificates as follows: enable
the email trust bit for the “SSC GDL CA VS Root” certificate; enable the
code signing and email trust bits for the “SSC GDL CA Root A”
certificate; and enable all three trust bits for the “SSC GDL CA Root B”
certificate. EV
7 matches
Mail list logo
