Google Git
Sign in
go / crypto / a48ac81e47fd6f9ed1258f3b60ae9e75f93cb7ed
commita48ac81e47fd6f9ed1258f3b60ae9e75f93cb7ed[log] [tgz]
authorHan-Wen Nienhuys <hanwen@google.com>Thu Jul 06 14:31:36 2017 +0200
committerHan-Wen Nienhuys <hanwen@google.com>Thu Jul 06 15:27:25 2017 +0000
treeb7be75458c9a91301f24110eea1de9db3186d377
parentd625dfd80595a76324dea1452ceb9cfbcaee8e3e [diff]
ssh: allow up to 255 bytes of padding in AES-GCM

The writing side would generate a maximum of 19 bytes of padding, so
the reading side erroneously checked this. However, RFC 5647 specifies
255 as the maximum amount of padding for AES-GCM.

Fixes golang/go#18953.

Change-Id: I416b0023c6e4cbd91a6a1b4214a03f1663b77248
Reviewed-on: https://go-review.googlesource.com/47590
Reviewed-by: Adam Langley <agl@golang.org>
Run-TryBot: Adam Langley <agl@golang.org>
TryBot-Result: Gobot Gobot <gobot@golang.org>
1 file changed
tree: b7be75458c9a91301f24110eea1de9db3186d377
  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