W3C home > Mailing lists > Public > public-rww@w3.org > January 2015

Re: Domains, Subdomains, Etc.

From: Anders Rundgren <anders.rundgren.net@gmail.com>
Date: Mon, 05 Jan 2015 09:14:29 +0100
Message-ID: <54AA47E5.7020108@gmail.com>
To: Timothy Holborn <timothy.holborn@gmail.com>, cdr <mail@whats-your.name>
CC: public-rww <public-rww@w3.org>, "public-webid@w3.org" <public-webid@w3.org>, Henry Story <henry.story@bblfish.net>
On 2015-01-05 04:41, Timothy Holborn wrote:
> Further research [2][3] appears to show the structure of using wildcard certs not currently supported?

Sub-domains costs nothing and TLS certs for sub-domains can be fully automated
with letsencrypt/ACME so if you are hosted on a reasonable provider everything
you need to get going should be available in the end of this year.

Anders

>
> The RWW (and LDP?) use-cases might be worth bringing up with the group managing the project i'd imagine?
>
> I've posted a question - I think to the right area [4].  If you've got any improvements to make, please do so. ;)
>
> [2] https://letsencrypt.github.io/acme-spec/
> [3] https://github.com/letsencrypt/lets-encrypt-preview/issues/66
> [4] https://groups.google.com/a/letsencrypt.org/d/topic/ca-dev/CTaExow1WrI/discussion
>
> On 5 January 2015 at 02:21, Timothy Holborn <timothy.holborn@gmail.com <mailto:timothy.holborn@gmail.com>> wrote:
>
>     Interesting. I found more info [1]
>
>     Does it support WebID-TLS?
>
>     [1] https://letsencrypt.org/howitworks/
>
>     On 4 January 2015 at 22:01, cdr <mail@whats-your.name <mailto:mail@whats-your.name>> wrote:
>
>         > a financial issue, being the cost of a
>         > domain and wildcard SSL certificate.
>
>         Let's Encrypt is attempting to address this
>
>         seth@EFF giving a talk on how it works:
>         https://www.youtube.com/watch?v=OZyXx8Ie4pA&t=17m
>
>
>
>
Received on Monday, 5 January 2015 08:15:02 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:10:50 UTC