diff options
| author | Gab <24553253+gabrix73@users.noreply.github.com> | 2025-06-06 13:53:39 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-06-06 13:53:39 +0200 |
| commit | 1f0531879edd88c304db3bbd14937f89ee3087ca (patch) | |
| tree | c4754ce32f6c99c642e76cab667ce60868d473b6 | |
| parent | 7887624068a9f5307d2efc8c33fa7dca4205b0aa (diff) | |
| download | nofuture-go-memguard-1f0531879edd88c304db3bbd14937f89ee3087ca.tar.gz nofuture-go-memguard-1f0531879edd88c304db3bbd14937f89ee3087ca.tar.xz nofuture-go-memguard-1f0531879edd88c304db3bbd14937f89ee3087ca.zip | |
Update README.md
| -rw-r--r-- | README.md | 22 |
1 files changed, 22 insertions, 0 deletions
@@ -100,6 +100,28 @@ Encrypted communication is based on shared **Session IDs**, which encapsulate th - Once both sides are synchronized, they can start exchanging encrypted text. --- +## π What Is the Session ID? + +The `Session ID` is not a simple string or UUID β it's a **cryptographic descriptor** of the secure session. +It contains all the necessary public information to allow the other party to **synchronize**, encrypt, and verify the session context. + +### π Composition of a Session ID + +- π The **public key** of the sender (Kyber1024-90s) +- 𧬠A **nonce** β a unique 24-byte random seed +- π§ Optionally, a digital signature (Dilithium5-AES) for verifying the identity +- π A hashed session fingerprint using BLAKE2b + +> Think of it like a βtemporary public keyβ for a one-time encrypted channel. + +### π§© Why it matters + +Sharing this `Session ID` allows another user to: +- Derive a **shared secret** via post-quantum KEM +- Bind their session securely to yours +- Encrypt data you alone can decrypt (and vice versa) + +---- ## π₯ End Session = Total Key Destruction |
