| commit | bfa7d42eb568d3c454e1853744768cc80718040d | [log] [tgz] |
|---|---|---|
| author | Alex Vaghin <ddos@google.com> | Fri Oct 26 11:44:37 2018 -0700 |
| committer | Filippo Valsorda <filippo@golang.org> | Tue Nov 06 15:23:44 2018 +0000 |
| tree | c39e76f0be0b038528fa55c6b8c7010445e575e5 | |
| parent | 4d3f4d9ffa16a13f451c3b2999e9c49e9750bf06 [diff] |
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>
This repository holds supplementary Go cryptography libraries.
The easiest way to install is to run go get -u golang.org/x/crypto/.... You can also manually git clone the repository to $GOPATH/src/golang.org/x/crypto.
This repository uses Gerrit for code changes. To learn how to submit changes to this repository, see https://golang.org/doc/contribute.html.
The main issue tracker for the crypto repository is located at https://github.com/golang/go/issues. Prefix your issue with “x/crypto:” in the subject line, so it is easy to find.
Note that contributions to the cryptography package receive additional scrutiny due to their sensitive nature. Patches may take longer than normal to receive feedback.