mirror of
https://github.com/amnezia-vpn/amneziawg-linux-kernel-module.git
synced 2026-10-13 21:34:34 +00:00
[PR #238] fix: use RejectAfterTime for failed-handshake cleanup #251
Labels
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
amnezia-vpn/amneziawg-linux-kernel-module#251
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
📋 Pull Request Information
Original PR: https://github.com/amnezia-vpn/amneziawg-linux-kernel-module/pull/238
Author: @HeisLuka
Created: 9/14/2026
Status: 🔄 Open
Base:
master← Head:fix/zero-key-cleanup-reject-after-time📝 Commits (1)
54de74bfix: use RejectAfterTime for failed-handshake cleanup📊 Changes
1 file changed (+2 additions, -2 deletions)
View changed files
📝
src/timers.c(+2 -2)📄 Description
Summary
Use
RejectAfterTimerather thanRekeyAfterTimewhen schedulingzero-key-material cleanup after handshake retries are exhausted.
The zero-key timer is documented and otherwise scheduled from
RejectAfterTime. This path was the outlier: it selected a value fromrekey_after_timebut fell back to the fixedREJECT_AFTER_TIMEconstant,so configurations with different rekey and reject ranges could clear residual
key material far earlier or later than intended.
The change keeps the existing kernel range-selection behavior and only corrects
which configured timer range is used.
Scope
This PR addresses only problem 2 from #227.
The data-path key expiration checks and receive-side negative refresh timeout
are intentionally left for separate changes.
Related to #227
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.