Re: Preparing to Publish HTTPS Finding

On 19 December 2014 at 11:28, Daniel Appelquist <appelquist@gmail.com>
wrote:
>
> As discussed on yesterday’s call, we have come to consensus to publish
> Mark’s draft[1] as a TAG finding, pending feedback on this mailing list (or
> via the Github issues tracker[2]), but before the end of the year. For all,
> but especially for those TAG members who were not on yesterday’s call, if
> you have any objections to this or would like to register further feedback,
> this is your chance.
>

+0

I welcome a more secure web.

However the cost of a wildcard HTTPS certificate is still prohibitive, if
you consider the budget of world population, or the long tail of
development, both of which tend to be under represented in TAG discussions.

I would welcome publication if consensus was reached that such a switch was
affordable, but I am unsure I've seen that bit covered yet, other that
discussion of the CPU overhead.

Perhaps next year, systems such as lets encrypt [1] will solve that issue.
Since TLS/SSL is a tactical solution to tackle security, why not back
similar tactics to make it affordable?

[1] https://letsencrypt.org/


> Thanks,
> Dan Appelquist
> TAG Co-Chair
>
> 1. https://w3ctag.github.io/web-https/
> 2. https://github.com/w3ctag/web-https/issues
>
>