Google Git
Sign in
go / crypto / 2b4b18b6aaeb2c9f7c1cc0145eccaabb3d96cf62
commit2b4b18b6aaeb2c9f7c1cc0145eccaabb3d96cf62[log] [tgz]
authorAndreas Auernhammer <aead@mail.de>Wed Dec 20 22:48:45 2017 +0100
committerAdam Langley <agl@golang.org>Sun Dec 31 21:46:28 2017 +0000
tree4c0ce4b361e44baeaa3502140b354e0f89f748d0
parent95a4943f35d008beabde8c11e5075a1b714e6419 [diff]
argon2: fix incorrect key derivation if parallelism > 1

This change fixes an incorrect key derivation if the
degree of parallelism is greater than 1.

This change adds additional test vectors generated by the
https://github.com/P-H-C/phc-winner-argon2 CLI.

Fixes golang/go#23200

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