commit | f9e2070545dcd4128a854a97ddf10fbfc3c4b6e4 | [log] [tgz] |
---|---|---|
author | Alex Vaghin <alex@cloudware.io> | Wed Sep 11 10:47:38 2019 -0400 |
committer | Alex Vaghin <ddos@google.com> | Tue Oct 01 17:07:39 2019 +0000 |
tree | 4939e889b9121c2a5b60ddfd79a0fcc45e2ee394 | |
parent | 4663e185863a1aee50d0486b326769f0bd22eb30 [diff] |
acme/internal: add a prober program While working on the RFC 8555 implementation for golang/go#21081, I've been also manually verifying the functionality against various CAs both draft-02 and RFC versions. This does not of course replace automated tests yet it might be useful to others. It is not a _test.go file because the program may require interactive user input for dns-01 challenge types and needs to flush logs to stderr during its run. Change-Id: Ia324b08b30308441cc0705648e30c0112b0fa0c8 Reviewed-on: https://go-review.googlesource.com/c/crypto/+/194681 Reviewed-by: Brad Fitzpatrick <bradfitz@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.