From 0e7e403c64fd17508a2f8931538727a7cf72a573 Mon Sep 17 00:00:00 2001 From: kaldonia Date: Fri, 7 Jun 2024 11:01:27 +0200 Subject: [PATCH] Fix typo in aes-cipher-concepts.md --- symmetric-key-ciphers/aes-cipher-concepts.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/symmetric-key-ciphers/aes-cipher-concepts.md b/symmetric-key-ciphers/aes-cipher-concepts.md index 80f309e..0a2d896 100644 --- a/symmetric-key-ciphers/aes-cipher-concepts.md +++ b/symmetric-key-ciphers/aes-cipher-concepts.md @@ -59,7 +59,7 @@ The entire **AES encryption** process (password-based authenticated encryption) * In case of **authenticated encryption** (e.g. AES-GCM), the MAC is already calculated automatically during the AES encryption process. - * If the encryption scheme is **not authenticated encryption** (e.g. AER-CTR), the MAC code is not calculated automatically by the AES encryption process and should be calculated additionally. The **MAC code** can be calculated from the **input msg**, using the encryption **key** (or some transformation of it) and some **MAC function** (like HMAC-SHA-256): + * If the encryption scheme is **not authenticated encryption** (e.g. AES-CTR), the MAC code is not calculated automatically by the AES encryption process and should be calculated additionally. The **MAC code** can be calculated from the **input msg**, using the encryption **key** (or some transformation of it) and some **MAC function** (like HMAC-SHA-256): * The **ciphertext** is calculated through the **AES encryption algorithm**. It first **generates a random salt** (**IV**) and uses it to transform the **input msg** using the **encryption key**, through the AES cipher encryption logic: