Skip to content

Update crypto/aead to libsodium 1.0.15 - #36

Open
silkeh wants to merge 2 commits into
GoKillers:masterfrom
silkeh:crypto_aead
Open

Update crypto/aead to libsodium 1.0.15#36
silkeh wants to merge 2 commits into
GoKillers:masterfrom
silkeh:crypto_aead

Conversation

@silkeh

@silkeh silkeh commented Oct 23, 2017

Copy link
Copy Markdown
Contributor

For performing the size checks from libsodium 1.0.14 the support.CheckSizeMax function is added.

libsodium also added a warning to crypto_aead_aes256gcm (below), should we include it as well?

/*
 * WARNING: Despite being the most popular AEAD construction due to its
 * use in TLS, safely using AES-GCM in a different context is tricky.
 *
 * No more than ~ 350 GB of input data should be encrypted with a given key.
 * This is for ~ 16 KB messages -- Actual figures vary according to
 * message sizes.
 *
 * In addition, nonces are short and repeated nonces would totally destroy
 * the security of this scheme.
 *
 * Nonces should thus come from atomic counters, which can be difficult to
 * set up in a distributed environment.
 *
 * Unless you absolutely need AES-GCM, use crypto_aead_xchacha20poly1305_ietf_*()
 * instead. It doesn't have any of these limitations.
 * Or, if you don't need to authenticate additional data, just stick to
 * crypto_secretbox().
 */

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant