From 69b206c3a0d07e9a8cb2edea022f050972b31c43 Mon Sep 17 00:00:00 2001 From: ID Bot Date: Sun, 5 Jan 2025 22:10:06 +0000 Subject: [PATCH] Script updating gh-pages from 1017f0d. [ci skip] --- proofreading/draft-irtf-cfrg-aegis-aead.html | 2 +- proofreading/draft-irtf-cfrg-aegis-aead.txt | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/proofreading/draft-irtf-cfrg-aegis-aead.html b/proofreading/draft-irtf-cfrg-aegis-aead.html index 9016000..e58db6b 100644 --- a/proofreading/draft-irtf-cfrg-aegis-aead.html +++ b/proofreading/draft-irtf-cfrg-aegis-aead.html @@ -3633,7 +3633,7 @@

10.2. Implementation Security

-

If tag verification fails, the unverified plaintext and computed authentication tag MUST NOT be released. As shown in [VV18], even a partial leak of the plaintext without verification would facilitate chosen ciphertext attacks.

+

If tag verification fails, the unverified plaintext and computed authentication tag MUST NOT be released. As shown in [VV18], even a partial leak of the plaintext without verification facilitates chosen ciphertext attacks.

The security of AEGIS against timing and physical attacks is limited by the implementation of the underlying AESRound function. Failure to implement AESRound in a fashion safe against timing and physical attacks, such as differential power analysis, timing analysis, or fault injection attacks, may lead to leakage of secret key material or state information. The exact mitigations required for timing and physical attacks depend on the threat model in question.

Regardless of the variant, the key and nonce are only required by the Init function; other functions only depend on the resulting state. Therefore, implementations can overwrite ephemeral keys with zeros right after the last Update call of the initialization function.

diff --git a/proofreading/draft-irtf-cfrg-aegis-aead.txt b/proofreading/draft-irtf-cfrg-aegis-aead.txt index edc7166..640af2c 100644 --- a/proofreading/draft-irtf-cfrg-aegis-aead.txt +++ b/proofreading/draft-irtf-cfrg-aegis-aead.txt @@ -1905,8 +1905,8 @@ return tag If tag verification fails, the unverified plaintext and computed authentication tag MUST NOT be released. As shown in [VV18], even a - partial leak of the plaintext without verification would facilitate - chosen ciphertext attacks. + partial leak of the plaintext without verification facilitates chosen + ciphertext attacks. The security of AEGIS against timing and physical attacks is limited by the implementation of the underlying AESRound function. Failure