Matthew Holt 6f78cc49d1 tls: Initial transition to ACMEv2 and support automatic wildcard certs ... - Using xenolf/lego's likely-temporary acmev2 branch - Cleaned up vendor folder a little bit (probably more to do) - Temporarily set default CA URL to v2 staging endpoint - Refactored user management a bit; updated tests (biggest change is how we get the email address, which now requires being able to make an ACME client with a User with a private key so that we can get the current ToS URL) - Automatic HTTPS now allows specific wildcard pattern hostnames - Commented out (but kept) the TLS-SNI code, as the challenge type may return in the future in a similar form		2018-03-14 21:44:08 -06:00
..
cloud.google.com/go/compute/metadata	Vendor all dependencies (Warning: Huge changeset.)	2017-05-27 13:30:11 -06:00
github.com	tls: Initial transition to ACMEv2 and support automatic wildcard certs	2018-03-14 21:44:08 -06:00
go4.org/syncutil/singleflight	Vendor all dependencies (Warning: Huge changeset.)	2017-05-27 13:30:11 -06:00
golang.org/x	tls: Initial transition to ACMEv2 and support automatic wildcard certs	2018-03-14 21:44:08 -06:00
google.golang.org	vendor: Update dependencies	2017-07-27 16:11:56 -06:00
gopkg.in	tls: Initial transition to ACMEv2 and support automatic wildcard certs	2018-03-14 21:44:08 -06:00
manifest	tls: Initial transition to ACMEv2 and support automatic wildcard certs	2018-03-14 21:44:08 -06:00