forked from TrueCloudLab/certificates
acme/challenge: Fix error return type on KeyAuthorization
In golang, one should always return error types rather than interfaces that conform to an error protocol. Why? Because of this: https://play.golang.org/p/MVa5vowuNRo Feels ~~like JavaScript~~ bad, man.
This commit is contained in:
parent
9f18882973
commit
089e3aea4f
1 changed files with 1 additions and 1 deletions
|
@ -621,7 +621,7 @@ func (dc *dns01Challenge) validate(jwk *jose.JSONWebKey, vo validateOptions) (ch
|
|||
|
||||
// KeyAuthorization creates the ACME key authorization value from a token
|
||||
// and a jwk.
|
||||
func KeyAuthorization(token string, jwk *jose.JSONWebKey) (string, *Error) {
|
||||
func KeyAuthorization(token string, jwk *jose.JSONWebKey) (string, error) {
|
||||
thumbprint, err := jwk.Thumbprint(crypto.SHA256)
|
||||
if err != nil {
|
||||
return "", ServerInternalErr(errors.Wrap(err, "error generating JWK thumbprint"))
|
||||
|
|
Loading…
Reference in a new issue