Missing <connection> parity with OpenVPN 2.x
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 30/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- cpp
- Domain
- networking, security
Research direction
The payload names no source files. Start by finding where the C++ profile parser handles the <connection> block and its remote directive, then check how the per-connection options are applied. Done means key-direction, tls-auth, tls-crypt and tls-crypt-v2 are accepted inside <connection> and applied per remote. Agree the scope with maintainers before coding, since the issue lists about two dozen options.
Written by the indexing model from the issue text.
Description
It would seem that in OpenVPN 3.x, only remote directives are considered.
This means it is impossible to tailor network flexibility and, more importantly, cryptography/PKI for multiple remote servers in a cluster for HA without requiring a completely separate configuration per-server - which is a terrible UX for end-users, as they must now be instructed to explicitly choose a different fallback (and defeats the purpose of multiple <connection>s).
OpenVPN 2.7.8, for instance, lists the following as supported inside a <connection> block:
bindconnect-retryconnect-retry-maxconnect-timeoutexplicit-exit-notifyfloatfragmenthttp-proxyhttp-proxy-optionkey-directionlink-mtulocallportmssfixmtu-discnobindportprotoremoterportsocks-proxytls-authtls-crypttls-crypt-v2tun-mtutun-mtu-extra
Now, some may of course not be relevant (e.g. fragment, given #24 ).
But others -- most notably the key-direction, tls-auth, tls-crypt, and tls-crypt-v2 directives -- are a significant disparity if one maintains separate TLS auth/crypt keys per-server (as, IMHO, one should per various compliance recommendations/requirements).
I am requesting that support for the missing options, especially the key-direction and tls-* directives, be added to <connection> block parsing/application in OpenVPN 3.
- 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
-
Difficulty 3/5 1-2 days Newbie friendliness 53/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 55/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