On 24/01/17 14:53, Gervase Markham wrote:
> It is proposed that we dealing with this from a policy perspective by
> doing the following:
Resolution: branch merged as drafted.
> 5) We will need to update the CCADB-related pages on the Mozilla wiki to
> disentangle and remove policy bits from the
On 27/01/2017 10:06, Gervase Markham wrote:
On 26/01/17 14:12, Jakob Bohm wrote:
Given that Mozilla has been reducing the scope and generality of their
root store over the past few years, I would suggest reaching out to
those organizations that base their public root stores on the Mozilla
On 26/01/2017 10:23, Gervase Markham wrote:
On 25/01/17 18:38, Ryan Sleevi wrote:
I'm a little wary of introducing #1 until you know what #2 contains,
because to introduce #1, you want to have some way of building
consensus/agreement with different consumers, and that remains unspecified.
It
On 25/01/17 18:38, Ryan Sleevi wrote:
> I'm a little wary of introducing #1 until you know what #2 contains,
> because to introduce #1, you want to have some way of building
> consensus/agreement with different consumers, and that remains unspecified.
It does remain unspecified... However, while
On 25/01/17 18:38, Ryan Sleevi wrote:
> I'm a little wary of introducing #1 until you know what #2 contains,
> because to introduce #1, you want to have some way of building
> consensus/agreement with different consumers, and that remains unspecified.
> Further, because of the existence of #2, it
Mozilla has started using the Common CA Database to track root
certificates in its root program, and the intermediate certificates
which chain up to those roots. This has led to substantial changes to
the practical processes that CAs must follow. In addition, it is hoped
and anticipated that other
6 matches
Mail list logo
