Google Git
Sign in
go / crypto / 5f87f3452ae96c4850ab9af7783f2517b643061b
commit5f87f3452ae96c4850ab9af7783f2517b643061b[log] [tgz]
authorJulie Qiu <julie@golang.org>Mon Dec 07 11:24:29 2020 -0500
committerJulie Qiu <julie@golang.org>Tue Dec 08 17:14:46 2020 +0000
treefcef8433556e85cc3645a921977d62d710938bdb
parentbe400aefbc4c83e9aab51e82b8d4b12760653b47 [diff]
README.md: add badge to pkg.go.dev

A badge linking to https://pkg.go.dev/golang.org/x/crypto is added.

Change-Id: Ifa07c0c04e3dd30503f196179f6883cc569e7908
Reviewed-on: https://go-review.googlesource.com/c/crypto/+/275873
Trust: Julie Qiu <julie@golang.org>
Run-TryBot: Julie Qiu <julie@golang.org>
TryBot-Result: Go Bot <gobot@golang.org>
Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
Reviewed-by: Filippo Valsorda <filippo@golang.org>
1 file changed
tree: fcef8433556e85cc3645a921977d62d710938bdb
  1. acme/
  2. argon2/
  3. bcrypt/
  4. blake2b/
  5. blake2s/
  6. blowfish/
  7. bn256/
  8. cast5/
  9. chacha20/
  10. chacha20poly1305/
  11. cryptobyte/
  12. curve25519/
  13. ed25519/
  14. hkdf/
  15. internal/
  16. md4/
  17. nacl/
  18. ocsp/
  19. openpgp/
  20. otr/
  21. pbkdf2/
  22. pkcs12/
  23. poly1305/
  24. ripemd160/
  25. salsa20/
  26. scrypt/
  27. sha3/
  28. ssh/
  29. tea/
  30. twofish/
  31. xtea/
  32. xts/
  33. .gitattributes
  34. .gitignore
  35. AUTHORS
  36. codereview.cfg
  37. CONTRIBUTING.md
  38. CONTRIBUTORS
  39. go.mod
  40. go.sum
  41. LICENSE
  42. PATENTS
  43. README.md
README.md

Go Cryptography

Go Reference

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.