Missing <connection> parity with OpenVPN 2.x

Open
#447 0 comments 0 reactions 0 assignees View on GitHub

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

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

enhancement

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:

  • bind
  • connect-retry
  • connect-retry-max
  • connect-timeout
  • explicit-exit-notify
  • float
  • fragment
  • http-proxy
  • http-proxy-option
  • key-direction
  • link-mtu
  • local
  • lport
  • mssfix
  • mtu-disc
  • nobind
  • port
  • proto
  • remote
  • rport
  • socks-proxy
  • tls-auth
  • tls-crypt
  • tls-crypt-v2
  • tun-mtu
  • tun-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

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from OpenVPN/openvpn3

All issues in OpenVPN/openvpn3

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.