1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
//! Noise handshake patterns.
//!
//! A pattern defines the pre-message knowledge and the sequence of
//! handshake messages. Each message is a type-level list of tokens
//! wrapped in a [`Message`] with a direction.
use *;
use assert_well_formed;
/// A Noise handshake pattern.
///
/// Implementors encode the full message flow as associated types
/// built from [`Cons`]/[`Nil`] lists of [`Message`]s, making the
/// handshake structure available to the compiler at monomorphisation
/// time.
// ── N ───────────────────────────────────────────────────────────
/// `N` — one-way pattern. The sender knows the recipient's static
/// key. No sender authentication.
///
/// Used for encrypting data at rest to a known public key (e.g.
/// sealing per-pair PSKs to the device's own Secure Enclave key).
/// Each seal operation uses a fresh ephemeral key, providing
/// forward secrecy per write.
///
/// ```text
/// N:
/// <- s
/// ...
/// -> e, es
/// ```
;
assert_well_formed!;
// ── K ───────────────────────────────────────────────────────────
/// `K` — one-way authenticated pattern. Both static keys are known
/// before the handshake. The sender is authenticated via `ss`.
///
/// Used for sealed envelopes between two peers who have already
/// completed a trust ceremony — the message is confidential,
/// sender-authenticated, and forward-secret.
///
/// ```text
/// K:
/// -> s
/// <- s
/// ...
/// -> e, es, ss
/// ```
;
assert_well_formed!;
// ── Kpsk0 ────────────────────────────────────────────────────────
/// `Kpsk0` — one-way authenticated pattern with PSK at position 0.
/// Both static keys are known; the PSK is mixed before the ephemeral
/// key, binding the entire message to the ceremony-established trust.
///
/// ```text
/// Kpsk0:
/// -> s
/// <- s
/// ...
/// -> psk, e, es, ss
/// ```
;
assert_well_formed!;
// ── IKpsk1 ──────────────────────────────────────────────────────
/// `IKpsk1` — the initiator knows the responder's static key and
/// transmits their own static key encrypted in msg1. A PSK is
/// mixed at the end of msg1.
///
/// The initiator's identity is revealed to the responder during
/// msg1 processing (after `es` DH), enabling per-pair PSK lookup
/// before the `psk` token.
///
/// ```text
/// IKpsk1:
/// <- s
/// ...
/// -> e, es, s, ss, psk
/// <- e, ee, se
/// ```
;
assert_well_formed!;
// ── IK ──────────────────────────────────────────────────────────
/// `IK` — interactive mutual authentication. The initiator knows the
/// responder's static key up front and transmits its own static key,
/// encrypted, in msg1; the responder authenticates in msg2.
///
/// Identical to [`IKpsk1`] without the pre-shared key — full mutual
/// authentication from raw static-key DH alone.
///
/// ```text
/// IK:
/// <- s
/// ...
/// -> e, es, s, ss
/// <- e, ee, se
/// ```
;
assert_well_formed!;
// ── NK ──────────────────────────────────────────────────────────
/// `NK` — interactive, responder-authenticated handshake. The
/// initiator knows the responder's static key up front and is
/// **anonymous** (it has no static key of its own); only the
/// responder is authenticated, via the `es` DH that binds its static
/// key.
///
/// Like [`IK`] minus the initiator's static key — confidentiality to
/// a known recipient plus a fresh responder ephemeral, without
/// initiator authentication.
///
/// ```text
/// NK:
/// <- s
/// ...
/// -> e, es
/// <- e, ee
/// ```
;
assert_well_formed!;
// ── IX ──────────────────────────────────────────────────────────
/// `IX` — interactive mutual authentication with **no pre-messages**:
/// neither party knows the other's static key up front. Both transmit
/// their static keys *during* the handshake (as `s` tokens).
///
/// Because the initiator's static is sent in msg1 **before any DH**, it
/// travels **in the clear** — exposed to a passive eavesdropper. The
/// responder's static is sent in msg2 *after* `ee` keys the cipher, so
/// it is encrypted. Authentication is mutual: the initiator is
/// authenticated to the responder via `se`, the responder to the
/// initiator via `es`.
///
/// Unlike [`IK`], there is no pre-known static on either side — IX
/// trades the initiator's identity privacy for not needing the
/// responder's static key in advance.
///
/// ```text
/// IX:
/// -> e, s
/// <- e, ee, se, s, es
/// ```
;
assert_well_formed!;
// ── XK ──────────────────────────────────────────────────────────
/// `XK` — interactive mutual authentication over **three messages**
/// with strong **initiator-identity privacy**. The initiator knows the
/// responder's static key up front (pre-message `<- s`) and
/// authenticates the responder early via `es`. The initiator's own
/// static key is transmitted **encrypted in msg3** (after `ee` has
/// keyed the cipher), so it is hidden from a passive eavesdropper, and
/// is authenticated via `se`.
///
/// Unlike [`IK`] (where the initiator's static rides in msg1), XK defers
/// the initiator's static to a third flight, after both ephemerals are
/// mixed — giving the initiator's identity full forward-secret
/// confidentiality at the cost of an extra round trip.
///
/// ```text
/// XK:
/// <- s
/// ...
/// -> e, es
/// <- e, ee
/// -> s, se
/// ```
;
assert_well_formed!;
// ── NN ──────────────────────────────────────────────────────────
/// `NN` — interactive handshake with **no static keys** and **no
/// pre-messages**: both parties are anonymous. The only key material
/// exchanged is a fresh ephemeral from each side.
///
/// `NN` provides **no authentication** of either party — it is
/// vulnerable to an active man-in-the-middle. Confidentiality holds
/// only against a *passive* eavesdropper. Once `ee` mixes both
/// ephemerals, the session has **full forward secrecy**.
///
/// msg1 (`-> e`) is the first pattern to drive the single-`e` send
/// finalizer: the cipher is never keyed in msg1, so the message is
/// just the bare ephemeral (no payload tag).
///
/// ```text
/// NN:
/// -> e
/// <- e, ee
/// ```
;
assert_well_formed!;
// ── XX ──────────────────────────────────────────────────────────
/// `XX` — the canonical interactive, mutually-authenticated handshake
/// over **three messages** with **no pre-messages**. Both parties
/// transmit their static keys *during* the handshake, and both do so
/// **encrypted** (after `ee` keys the cipher), so **both identities are
/// hidden from a passive eavesdropper**.
///
/// The initiator is authenticated to the responder via `se`; the
/// responder is authenticated to the initiator via `es`. Neither side
/// needs to pre-know the other's static key — unlike [`XK`] (which
/// pre-knows the responder's static via a pre-message), XX learns both
/// statics on the wire. Once `ee` mixes both ephemerals, the session
/// has **full forward secrecy**.
///
/// msg1 (`-> e`) drives the single-`e` send finalizer (the cipher is
/// never keyed in msg1, so the message is the bare ephemeral with no
/// payload tag); msg3 (`-> s, se`) drives the `s`-first send entry,
/// sending the initiator's static encrypted.
///
/// ```text
/// XX:
/// -> e
/// <- e, ee, s, es
/// -> s, se
/// ```
;
assert_well_formed!;
// ── X ───────────────────────────────────────────────────────────
/// `X` — one-way authenticated pattern with sender-identity hiding. The
/// sender knows the recipient's static key up front (pre-message `<- s`)
/// and transmits its **own** static key, encrypted, within the single
/// message; the sender is authenticated via `ss`.
///
/// Like [`K`] it is a one-shot seal to a known recipient, but where `K`
/// pre-shares *both* statics, `X` pre-shares only the recipient's and
/// carries the sender's static **encrypted in-band** (after `es` keys the
/// cipher), so the sender's identity is hidden from a passive eavesdropper.
/// Its single message is the same token sequence as [`IK`]'s msg1, without
/// the responder's reply — confidential, sender-authenticated, and
/// forward-secret per write.
///
/// ```text
/// X:
/// <- s
/// ...
/// -> e, es, s, ss
/// ```
;
assert_well_formed!;