Send `RESTART,[P]:` instead of bare `RESTART` on server-initiated restart/exit
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- c
- Domain
- authentication, networking
Research direction
Start by tracing the server-initiated restart and exit signal emission and the control-message handling for bare RESTART. Compare the existing restart behavior with the proposed RESTART,[P]: and RESTART,[PN]: forms, then identify the relevant tests or add coverage showing that authentication tokens persist across a server restart without forcing reauthentication.
Written by the indexing model from the issue text.
Description
Environment
- Debian Trixie
- OpenVPN server version: 2.7.5-1~bpo13+1
- Clients: OpenVPN 2 community (
2.7.2) and OpenVPN Connect 3 (3.11.3) - Plugin: OpenVPN auth oAuth2 plugin version
2.0.1 - Use authentication tokens and persistent HHAC keys (directives
auth-gen-token 86400andauth-gen-token-secret [keyfile]
Description / Problem Statement:
When an OpenVPN server initiates a restart/reset (e.g., via SIGUSR1 or explicit management signals), it currently transmits a bare RESTART control message.
This causes inconsistent behavior across client implementations:
- OpenVPN 2.x (Community): Reuses the active
auth-tokenstored in memory and reconnects transparently. - OpenVPN Connect 3 (OpenVPN 3 Core): Interprets bare
RESTARTas a full session reset, purging ephemeral session tokens. Since the oauth2 plugin is in use, this forces users to re-enter credentials/OTP manually with the SSO server (unless the SSO session is already active) rather than completing a seamless background reconnection.
Proposed Solution / Feature Request:
- Update server restart signal emission to send
RESTART,[P]:by default to preserve pushed authentication tokens across restarts. - Alternatively, provide a configurable server directive to toggle between
RESTARTandRESTART,[P]:/RESTART,[PN]:behavior.
Impact:
Aligns session persistence across both OpenVPN 2.x and OpenVPN 3 core engines, preventing unnecessary authentication during graceful server restarts or maintenance.
- Dominant language
- C
- Stars
- 14.8k
- Forks
- 3.4k
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from OpenVPN/openvpn
-
Difficulty 2/5 1-3 hours Newbie friendliness 71/100
-
CVE-2026-11604 vs OpenVPN 2.7.x DocumentationMay be free again @lstipakov claimed this 35 days ago, and no pull request is open. OpenDCO website Windows
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Document Real Address format change in management/status output (OpenVPN 2.7)Possibly taken A pull request linked to this issue is open or already merged. Opendocumentation enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Since 2.7.9 "route-method exe" can't set routePossibly taken @d12fk claimed this 1 day ago. Openoutdated code Windows
-
enhancement feature
Difficulty 4/5 3-5 days Newbie friendliness 48/100
Similar issues
-
issue: bug report
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 2 days
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
documentation
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Stellarium/stellarium#5197 · 1 comment ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
ChupathingyCE/chupathingyce#1550 ·
Maintainers usually reply within 1 day
-
[BUG] SWAPDB sends no invalidation to CLIENT TRACKING clientsPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
redis/redis#16302 · 1 comment ·
Maintainers usually reply within 1 day