crypto/acme
Alex Vaghin bfa7d42eb5 acme: support custom crypto.Signer implementations
Currently, only rsa.PrivateKey and ecdsa.PrivateKey are supported
when creating JWS signatures. However, it is unnecessarily limiting
because any crypto.Signer implementation can sign a digest
in the appropriate format.

This change uses key.Public() instead of type-asserting the private
key which allows for a custom crypto.Signer implementation.
For instance, a key stored in a hardware module where the latter
does the actual signing without the key ever leaving its boundaries.

Change-Id: Ie7930ea2ba8c49dde7107ff074ae34abec05bdb9
Reviewed-on: https://go-review.googlesource.com/c/145137
Run-TryBot: Alex Vaghin <ddos@google.com>
TryBot-Result: Gobot Gobot <gobot@golang.org>
Reviewed-by: Filippo Valsorda <filippo@golang.org>
2018-11-06 15:23:44 +00:00
..
autocert acme/autocert: include rejected hostname in TLS handshake error when host not configured 2018-10-24 17:11:44 +00:00
acme.go acme: support custom crypto.Signer implementations 2018-11-06 15:23:44 +00:00
acme_test.go acme: fix encoding of the TLS-ALPN challenge extension 2018-06-13 20:22:54 +00:00
http.go acme: consistently return original errors from retries 2018-06-21 12:51:26 +00:00
http_test.go acme: consistently return original errors from retries 2018-06-21 12:51:26 +00:00
jws.go acme: support custom crypto.Signer implementations 2018-11-06 15:23:44 +00:00
jws_test.go acme: support custom crypto.Signer implementations 2018-11-06 15:23:44 +00:00
types.go acme: add support for TLS-ALPN 2018-06-08 09:28:29 +00:00
types_test.go acme: add function to check rate limits 2017-04-25 18:26:15 +00:00