Google Git
Sign in
go / crypto / 76eec36fa14229c4b25bb894c2d0e591527af429
commit76eec36fa14229c4b25bb894c2d0e591527af429[log] [tgz]
authorRuss Cox <rsc@golang.org>Wed Sep 27 13:19:09 2017 -0400
committerRuss Cox <rsc@golang.org>Thu Sep 28 14:24:50 2017 +0000
treed99c77c1cc4e09abd41797ad8e143745ffb91173
parentc84b36c635ad003a10f0c755dff5685ceef18c71 [diff]
acme/autocert: add Cache to Manager example

If you don't use a cache you're just begging for Let's Encrypt
to ban you for a week due to duplicate certificate requests.
Don't encourage users to get banned.

Change-Id: Icf999c7f28817990bb45931d30692d4040c0ed71
Reviewed-on: https://go-review.googlesource.com/66550
Run-TryBot: Russ Cox <rsc@golang.org>
TryBot-Result: Gobot Gobot <gobot@golang.org>
Reviewed-by: Alex Vaghin <ddos@google.com>
2 files changed
tree: d99c77c1cc4e09abd41797ad8e143745ffb91173
  1. acme/
  2. bcrypt/
  3. blake2b/
  4. blake2s/
  5. blowfish/
  6. bn256/
  7. cast5/
  8. chacha20poly1305/
  9. cryptobyte/
  10. curve25519/
  11. ed25519/
  12. hkdf/
  13. md4/
  14. nacl/
  15. ocsp/
  16. openpgp/
  17. otr/
  18. pbkdf2/
  19. pkcs12/
  20. poly1305/
  21. ripemd160/
  22. salsa20/
  23. scrypt/
  24. sha3/
  25. ssh/
  26. tea/
  27. twofish/
  28. xtea/
  29. xts/
  30. .gitattributes
  31. .gitignore
  32. AUTHORS
  33. codereview.cfg
  34. CONTRIBUTING.md
  35. CONTRIBUTORS
  36. LICENSE
  37. PATENTS
  38. README.md
README.md

Go Cryptography

This repository holds supplementary Go cryptography libraries.

Download/Install

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.

Report Issues / Send Patches

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.