From 7cf55414b5801f342817a239afe88a596335bb23 Mon Sep 17 00:00:00 2001 From: Leonetienne Date: Sun, 22 May 2022 23:22:54 +0200 Subject: [PATCH] Wording readme --- readme.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/readme.md b/readme.md index f7ed17f..eda2ff9 100644 --- a/readme.md +++ b/readme.md @@ -136,7 +136,7 @@ future output. ![Ciphertext 1](https://gitea.leonetienne.de/leonetienne/GCrypt/raw/branch/feature/relaunch/GCryptLib/visualizations/output.bmp.png) -Now, let's flip than a single bit in the input: +Now, let's flip a single bit in the input: One bit flipped, and again the corresponding ciphertext: ![One bit flipped](https://gitea.leonetienne.de/leonetienne/GCrypt/raw/branch/feature/relaunch/GCryptLib/visualizations/input-flip.bmp.png) @@ -148,15 +148,16 @@ Let's gif them together, to better see the difference:     ![Ciphertext](https://gitea.leonetienne.de/leonetienne/GCrypt/raw/branch/feature/relaunch/GCryptLib/visualizations/output.gif) +As shown, flipping even a single bit, affects the entire ciphertext. -#### What about input longer a single block? +#### What about input longer than a single block? Input, and ciphertext: ![Input](https://gitea.leonetienne.de/leonetienne/GCrypt/raw/branch/feature/relaunch/GCryptLib/visualizations/input-big.gif)     ![Ciphertext](https://gitea.leonetienne.de/leonetienne/GCrypt/raw/branch/feature/relaunch/GCryptLib/visualizations/output-big.gif) -Notice how the ciphertext doesn't change until the block containing the bitflip is reached. This is a limitation of cipher block chaining. +Notice how the ciphertext doesn't change until the block containing the bitflip is reached? This is a limitation of cipher block chaining. ### What about extreme inputs? How non-transparent is the cipher with extreme inputs? Even with a super problematic key?: