[tor-bugs] #18655 [Obfuscation/meek]: Make meek-server easy to use with Let's Encrypt

[Tor Bug Tracker & Wiki]

#18655: Make meek-server easy to use with Let's Encrypt
------------------------------+------------------------------
 Reporter:  dcf               |          Owner:  dcf
     Type:  enhancement       |         Status:  needs_review
 Priority:  Medium            |      Milestone:
Component:  Obfuscation/meek  |        Version:
 Severity:  Normal            |     Resolution:
 Keywords:                    |  Actual Points:
Parent ID:                    |         Points:
 Reviewer:                    |        Sponsor:
------------------------------+------------------------------
Changes (by dcf):

 * status:  new => needs_review


Comment:

 Here is a branch for review.
   https://gitweb.torproject.org/pluggable-
 transports/meek.git/log/?h=bug18655
   https://gitweb.torproject.org/pluggable-
 transports/meek.git/diff/?h=bug18655&id=1fcae3cad2&id2=93dd339f7

 Let's Encrypt support is activated by the `--acme-hostnames` option, which
 specifies the set of hostnames for which the server will ask for
 certificates. For example,
 {{{
 ServerTransportPlugin meek exec /usr/local/bin/meek-server --acme-
 hostnames meek.bamsoftware.com --acme-email david at bamsoftware.com
 }}}

 I have this running right now on https://meek.bamsoftware.com/ (which is
 the bridge
 [https://atlas.torproject.org/#details/C20658946DD706A7A2181159A1A04CD838570D04
 maenad]).

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/18655#comment:11>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online