noise: re-decide SSH check follow-up after verdict consumed

Closed verdict channel yields zero AuthVerdict, which Accept() treats as
success; a replayed follow-up was accepted even after Reject.
This commit is contained in:
Kristoffer Dalby authored and Kristoffer Dalby committed 2026-10-07 12:50:32 +02:00
1 parent 2dcd5c876e
commit 133f8142c6
3 files changed
+355 -10

No files matched your search

+1
View File
@@ -128,6 +128,7 @@ clients, and how to run the same setup without Nix.
- Fix packet filters under `autogroup:self` not updating after a user is added or renamed [#3501](https://github.com/juanfont/headscale/pull/3501)
- Fix a rejected policy leaving its packet filter active [#3501](https://github.com/juanfont/headscale/pull/3501)
- A registration request from a client below the minimum supported version is now rejected before it can log a node out, use a pre-auth key or start a login [#3519](https://github.com/juanfont/headscale/pull/3519)
- Fix a repeated SSH check follow-up for an already-decided session being accepted, even after the check was rejected; a repeat now asks the user to authenticate again
## 0.29.5 (202x-xx-xx)