Basic info

• Time: Wednesday 1 October 2025 at 14:00 CEST (12:00 UTC)
• Place: #openvpn-meeting channel on !LiberaChat IRC network

Topics

• Updated: Release 2.7
  OpenVPN 2.7 beta2 was released 25 September.
  It looks like next up will be a beta3, after which a stable release is expected.

• New, closed: verify signature page
  During the revamp of the community pages on the main openvpn.net website the instructions on how to verify the GPG signature was lost.
  We brought it back under the community.openvpn.net wiki's downloads page here; https://community.openvpn.net/Downloads/Verify%20signature

• New, closed: gerrit updated
  Gerrit review system was updated. If there are any issues please let uddr35 know on IRC.

• Updated: wolfSSL license changed from gplv2 to gplv3
  The release notes of wolfSSL indicate the license changed to GPLv3. This basically makes wolfSSL incompatible in regards to licensing with OpenVPN.
  We reached out to WolfSSL and we got back a response indicating that other parties have also expressed similar concerns and an exception may be considered.
  We are still waiting for a resolution, it has been several weeks now. We reached out again to wolfSSL.
  If there is no resolution by 15th of October, then we will proceed with our OpenVPN 2.7 release plans without wolfSSL support.

• OpenVPN community meetup 2025
  https://community.openvpn.net/openvpn/wiki/CommunityMeetup2025
  When: 25 and 26 october (Saturday and Sunday), with travel days on the Friday before and Monday after.
  Where: Naples, Italy.
  Meeting room: https://www.hotelparadisonapoli.it/en/home-page.aspx
  Hotel: Paradiso Napoli Hotel.
  Beer: yes.
  T-shirts: yes.
  Invites were sent to openvpn-devel and some selected individuals. If we missed anyone please reach out.
  Current status is we have asked Matt the designer to come up with a t-shirt design.

• forums situation
  minx offered to set up a new forum and help us migrate old data to it.
  We have a new setup with flarum at a hidden location and we're trying to get the old forums data in there.
  The tool for that called nitroporter had some difficulty, partially because the database is just so huge, but there is some progress.
  Sad news; minx left openvpn inc. however, he does still want to try to get this working and is helping us still.
  Once the migration is done, we can run some tests, and see if it meets our standards. Then we can plan a cutover date.
  To the question where the instance should be hosted, community indicates it should be under the community AWS infrastructure.
  To the question what authentication system should be used, community indicates it should just be the built-in system from the forum solution itself.

Backlog

• format code using clang formatting
  It seems prudent to do this before the real 2.7 release.
  It was discussed and there's some additional work to be paid either on reviewer or submitter side.
  Strategy will be; get all code into beta1, collect bugfixes, reformat everything, then beta2.
  Collect more bugfixes and then do release 2.7.0 and branch it off into its own release branch.

• t_server and t_client testing framework
  mattock reports progress on building automated testing environment for really old OpenVPN versions.
  This covers tests for versions going back to 2.2.

• push_update / live route updates
  Client-side support for push_update is now merged.
  For server-side support, company did QA on it with openvpn2 but found some missing features that are being added now.
  Client-side support made it into alpha3.

• 2.7 security audit
  ordex mentioned that OTF offers the possibility to get a 3rd-party security audit for supported projects. So we will apply for that around or after the 2.7 release to review the latest code.

• Tunnelcrack progress (see TunnelCrack community wiki article)
  Status update on TunnelCrack mitigations:
  The tunnelcrack mitigation for Windows has gone in master, which will go to 2.7 release. There is the possibility for it to go to 2.6.x if we can find testers for this.
  Windows, openvpn2: block-local merged to master, not to 2.6.x. openvpn3: in code review.
  Linux, openvpn2: in progress. openvpn3: in progress.
  macOS: to be determined.
  iOS: to be determined.
  Android: not vulnerable.

• donation collection
  From earlier exploration it is clear that setting up a legal entity is not worth the expense at this point. We're just starting out with donations.
  What we can do is start out with an existing company that can collect the money and puts it to good community use. ordex volunteers to take this on.
  There are some options to consider. There may be existing solutions that we want to consider.
  PayPal seems overly expensive with all their fees.
  Stripe could be worth considering for credit card processing.
  GitHub Sponsors was mentioned as a possible solution, this is worth investigating.
  Open Collective was also mentioned, that needs some investigating how that exactly would work for us.