|author||Jason Baker <email@example.com>||Mon Feb 10 19:01:28 2020 +0000|
|committer||Filippo Valsorda <firstname.lastname@example.org>||Mon Feb 10 19:18:31 2020 +0000|
acme: update TLS-ALPN identifier to the latest IANA assignment It looks like the source code has fallen out of date with the draft spec. The latest version https://tools.ietf.org/html/draft-ietf-acme-tls-alpn-05 has a different OID 18.104.22.168.22.214.171.124.31 assigned. You can test that you're using the correct OID by performing a TLS-ALPN-01 challenge against a Pebble (https://github.com/letsencrypt/pebble) ACME server running with the -strict argument. This implementation will reject the obsolete OID. Change-Id: I58c52eaed487949e9071d3b9772f7acfdcc91201 GitHub-Last-Rev: 4cacc0723c431a29aec77d4fb3320d91c66c1ff5 GitHub-Pull-Request: golang/crypto#91 Reviewed-on: https://go-review.googlesource.com/c/crypto/+/204177 Run-TryBot: Filippo Valsorda <email@example.com> Reviewed-by: Alex Vaghin <firstname.lastname@example.org> Reviewed-by: Filippo Valsorda <email@example.com>
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
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.