W3C home > Mailing lists > Public > public-webid@w3.org > November 2014

Re: https://letsencrypt.org

From: Melvin Carvalho <melvincarvalho@gmail.com>
Date: Mon, 24 Nov 2014 22:07:56 +0100
Message-ID: <CAKaEYhJQwuH8g4u=+BWAHQjuCJ5Q3DE1QkzGWsF3==3uat_WHw@mail.gmail.com>
To: Nick Jennings <nick@silverbucket.net>
Cc: "henry.story@bblfish.net" <henry.story@bblfish.net>, public-webid <public-webid@w3.org>
Me too, I joined both dev lists ...

Client Software

Let’s Encrypt Preview <https://github.com/letsencrypt/lets-encrypt-preview>
is a Python-based utility that works alongside Apache to automatically
obtain a certificate and convert a website to HTTPS.

Client software development can be discussed on this mailing list
<https://groups.google.com/a/letsencrypt.org/forum/#%21forum/client-dev>.
To subscribe without a Google account, send mail to
client-dev+subscribe@letsencrypt.org.
CA Software

We’ve created demo ACME library in node.js
<https://github.com/letsencrypt/node-acme> that let you see how the
protocol works. We also have example pre-built node.js modules
<https://github.com/letsencrypt/heroku-acme> based on the ACME library that
can be installed in a Heroku instance to create a test ACME server or
retrieve a test certificate.

CA software development can be discussed on this mailing list
<https://groups.google.com/a/letsencrypt.org/forum/#%21forum/ca-dev>. To
subscribe without a Google account, send mail to
ca-dev+subscribe@letsencrypt.org.


On 24 November 2014 at 21:24, Nick Jennings <nick@silverbucket.net> wrote:

> Yeah, I saw this as well, looks absolutely fantastic, definitely looking
> forward to the launch!
>
>
> On Mon Nov 24 2014 at 8:36:14 PM henry.story@bblfish.net <
> henry.story@bblfish.net> wrote:
>
>> "Let’s Encrypt is a new Certificate Authority:
>> It’s free, automated, and open.
>> Arriving Summer 2015"
>>
>> Don't have time to look into this in detail, but if
>> this allows me to add to my server a bit of code
>> that makes it close to a couple of click operations
>> for the server admino to create a certificate, then
>> this could massively increase deployment of https
>> servers. Currently creating a server certificate
>> is hugely and wastefully complex.
>>
>> This would then allow of course more servers to
>> deploy secure webids.
>>
>> Henry
>>
>>
>> Social Web Architect
>> http://bblfish.net/
>>
>>
>>
Received on Monday, 24 November 2014 21:08:25 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:54:50 UTC