riccardom 6e0c150fc9 [client] pqkem: drop the unused exchangeCtl.pendingPSK field ...

The responder wrote pendingPSK but nothing ever read it: the derived key is
consumed via m.psks (set at the same time) and the cached answer via lastSent.
Remove the field and its write to avoid a misleading store.

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

2026-10-09 09:49:59 +02:00

..

bench_test.go

Addresses CI fixes

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

callbacks.go

[client] pqkem: carry a generation on PSK callbacks to drop stale applies

2026-10-07 13:30:52 +02:00

capability_test.go

[client] pqkem: signal a responder failure distinctly from "no KEM"

2026-10-07 13:38:42 +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: drop the unused exchangeCtl.pendingPSK field

2026-10-09 09:49:59 +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: carry a generation on PSK callbacks to drop stale applies

2026-10-07 13:30:52 +02:00

manager.go

[client] pqkem: drop the unused exchangeCtl.pendingPSK field

2026-10-09 09:49:59 +02:00

message_test.go

[client] pqkem: signal a responder failure distinctly from "no KEM"

2026-10-07 13:38:42 +02:00

message.go

[client] pqkem: signal a responder failure distinctly from "no KEM"

2026-10-07 13:38:42 +02:00