On 20/11/14 07:27, Peter Gutmann wrote:
> That was my immediate reaction as well. CACert has been given the runaround
> for more than just four years, it's been more than a decade, and yet as soon
> as a Mozilla-sponsored CA turns up it's in.
>
> Perhaps someone from Mozilla would be able to expl
On Thu, Nov 20, 2014 at 6:22 AM, Richard Barnes wrote:
> I am from Mozilla, and the replies here are exactly right. From the
> perspective of the Mozilla root CA program, Let's Encrypt will be treated as
> any other applicant, should they choose to apply. No "immediate acceptance",
> no "less
I am from Mozilla, and the replies here are exactly right. From the
perspective of the Mozilla root CA program, Let's Encrypt will be treated as
any other applicant, should they choose to apply. No "immediate acceptance",
no "less audited" -- same audit requirements and application process as
On Thu, Nov 20, 2014 at 08:27:37PM +1300, Peter Gutmann wrote:
> Mark Atwood writes:
> >On Tue, Nov 18, 2014, at 11:25, Salz, Rich wrote:
> >> Initial drop of code and specs available here:
> >> https://github.com/letsencrypt
> >>
> >> From https://letsencrypt.org/2014/11/18/announcing-lets-encryp
On Wed, Nov 19, 2014 at 11:27 PM, Peter Gutmann
wrote:
> Mark Atwood writes:
>>So Mozilla et al have been giving CAcert the runaround for over 4 years now,
>>and then suddenly they create a more centralized less audited "Let's Encrypt"
>>shows up, and it's welcomed into the root?
>
> That was my
Mark Atwood writes:
>On Tue, Nov 18, 2014, at 11:25, Salz, Rich wrote:
>> Initial drop of code and specs available here:
>> https://github.com/letsencrypt
>>
>> From https://letsencrypt.org/2014/11/18/announcing-lets-encrypt.html :
>
>So Mozilla et al have been giving CAcert the runaround for over
6 matches
Mail list logo
