Extend `--static-challenge` to support concat mode like OpenVPN
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 55/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- cpp
- Domain
- networking, security
Research direction
Start by locating the OpenVPN3 entry point that parses and handles --static-challenge, then compare its current two-argument behavior with the linked OpenVPN 2.x changes. Support the documented scrv1 default and concat form while preserving existing usage; done means the three-argument example works with the expected password and response format.
Written by the indexing model from the issue text.
Description
OpenVPN 2.x recently added support for extending the --static-challenge option with a third argument (scrv1 or concat) to specify whether the password and response should be concatenated or use the SCRV1 protocol (default: scrv1).
This allows simpler handling of password+response in some server-side scripts/plugins that expect plain concatenation instead of the SCRV1-formatted string.
OpenVPN3 currently supports --static-challenge with only two arguments (challenge text and echo flag), but lacks this third argument for format selection.
https://github.com/OpenVPN/openvpn/commit/6f6a0f362f845f042a965f797b731f8931310372
https://gerrit.openvpn.net/c/openvpn/+/665
https://patchwork.openvpn.net/project/openvpn2/patch/[email protected]/#6530
https://github.com/OpenVPN/openvpn-gui/issues/663
Example Usage
--static-challenge "Enter OTP:" 0 concat
This would prompt for the challenge response without echo and concatenate it directly with the password.
Why Needed
- Compatibility with servers expecting concatenation behavior.
- Parity with upstream OpenVPN features for easier migration.
- Dominant language
- C++
- Stars
- 1.2k
- Forks
- 473
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No 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/openvpn3
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 30/100
-
Difficulty 3/5 1-2 days Newbie friendliness 53/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
All issues in OpenVPN/openvpn3
Similar issues
-
bug needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
microsoft/DirectXShaderCompiler#9155 ·
Maintainers usually reply within 2 days
-
Errors in 1.20 proseOpenCampaign DiD Campaign EI Campaign HttT Campaign TDG Campaign TSG Campaign WoF Enhancement Help Prose Stable 1.20
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
wesnoth/wesnoth#11749 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
trabucayre/openFPGALoader#767 ·
Maintainers usually reply within 1 day
-
agent:Windows bug in progress pri:medium sev:low testing windows
Difficulty 1/5 Under an hour Newbie friendliness 91/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
protocolbuffers/protobuf#31768 ·
Maintainers usually reply within 1 day