riccardom cc2d43ee09 [client] pqkem: document the real responder callback timing ...

OnNewPSKReady's doc claimed the responder fires it "on receiving the confirm",
but there is no confirm round: the responder fires it right after deriving the
PSK from the offer and before sending the answer. Say so, so a host does not
assume the peer has already confirmed the key.

Found in cubic review on #7098 (client/internal/pqkem/callbacks.go:11).

2026-10-07 13:23:22 +02:00

..

bench_test.go

Addresses CI fixes

2026-09-11 14:48:54 +02:00

callbacks.go

[client] pqkem: document the real responder callback timing

2026-10-07 13:23:22 +02:00

capability_test.go

Addresses CI fixes

2026-09-11 14:48:54 +02:00

concurrency_test.go

Addresses CI fixes

2026-09-11 14:48:54 +02:00

convergence_test.go

[client] pqkem: enforce exchange roles and re-bootstrap stale signal offers

2026-09-11 15:03:47 +02:00

convergence.go

[client] pqkem: address review findings on convergence, strict parsing and status

2026-10-05 16:02:33 +02:00

env.go

[client] pqkem: address review findings on convergence, strict parsing and status

2026-10-05 16:02:33 +02:00

kem_framing_test.go

Adds test to validate compromised keys are not accepted

2026-09-11 14:48:54 +02:00

kem_test.go

Addresses CI fixes

2026-09-11 14:48:54 +02:00

kem.go

Addresses CI fixes

2026-09-11 14:48:54 +02:00

manager_test.go

[client] pqkem: enforce exchange roles and re-bootstrap stale signal offers

2026-09-11 15:03:47 +02:00

manager.go

[client] pqkem: correct the convergence-deadline comment

2026-10-07 13:22:59 +02:00

message_test.go

Removes confirm. Uses next offer to deliver confirmation/ack of previous round

2026-09-11 14:48:54 +02:00

message.go

Addresses CI fixes

2026-09-11 14:48:54 +02:00