Skip to content

Commit 47bc8a6

Browse files
Add session flow overview to architecture page
Adds the PostGuard session flow diagram and numbered steps to the architecture page, providing a high-level overview before the detailed encryption and decryption flow breakdowns. Requested in encryption4all/postguard#130 review feedback. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
1 parent e729573 commit 47bc8a6

2 files changed

Lines changed: 22 additions & 0 deletions

File tree

docs/guide/architecture.md

Lines changed: 22 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -58,6 +58,28 @@ IBS Master Key Pair (lives on the PKG server)
5858
Used to derive per-sender signing keys
5959
```
6060

61+
## Session Flow
62+
63+
A typical PostGuard session works as follows. Red actions require user interaction; all other actions are automatic.
64+
65+
<p align="center">
66+
<img src="/postguard-flow.png" alt="PostGuard session flow"/>
67+
</p>
68+
69+
0. The PKG generates a master key pair.
70+
1. Alice's client retrieves the public master key from the PKG.
71+
2. Alice uses the public master key and Bob's identity to encrypt a message.
72+
3. Alice's client sends the ciphertext to Bob via any channel.
73+
4. Bob's client asks for a key to decrypt the ciphertext.
74+
5. The PKG starts an authentication session at the Yivi server.
75+
6. Bob is asked to reveal his identity via a QR code.
76+
7. Bob reveals his identity.
77+
8. The Yivi server sends the authentication results to the PKG.
78+
9. The PKG issues a key for Bob's identity.
79+
10. Bob's client decrypts the ciphertext using his key.
80+
81+
The sections below break down the encryption and decryption steps in more detail.
82+
6183
## Encryption Flow
6284

6385
Here is what happens when a sender encrypts data:

docs/public/postguard-flow.png

101 KB
Loading

0 commit comments

Comments
 (0)