From e9f942ad012160bb8995dc14ae03333efa012dbc Mon Sep 17 00:00:00 2001 From: miro Date: Tue, 24 Dec 2024 16:00:21 +0000 Subject: [PATCH] format --- docs/19_crypto.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/19_crypto.md b/docs/19_crypto.md index b54046a..3a8d138 100644 --- a/docs/19_crypto.md +++ b/docs/19_crypto.md @@ -92,9 +92,9 @@ This approach ensures that both devices independently derive the same encryption Once the secret key is derived, it is used to encrypt and decrypt all messages exchanged between devices. The process is as follows: 1. **Encryption**: - - The sending device uses the secret key to encrypt the plaintext message using AES-GCM. - - The resulting ciphertext, along with the `nonce` and `tag`, is packaged into a message and sent over the network. + - The sending device uses the secret key to encrypt the plaintext message using AES-GCM. + - The resulting ciphertext, along with the `nonce` and `tag`, is packaged into a message and sent over the network. 2. **Decryption**: - - The receiving device extracts the `ciphertext`, `nonce`, and `tag` from the message. - - Using the same secret key, it decrypts the `ciphertext` and verifies the message integrity using the `tag`. + - The receiving device extracts the `ciphertext`, `nonce`, and `tag` from the message. + - Using the same secret key, it decrypts the `ciphertext` and verifies the message integrity using the `tag`.