- **Time:** Wednesday 20 November 2024 at 14:00 CEST (12:00 UTC)

- **Place:** #openvpn-meeting channel on LiberaChat IRC network

- **Updated: DCO Linux upstreaming**

Upstreaming DCO to Linux is proceeding, it is in review stage at the moment.

ordex intended to send out patchset v12 but was delayed due to illness. Now expected this week.

- **Updated: data format v3 / epoch data keys**

RFC is here: [https://github.com/OpenVPN/openvpn-rfc/pull/5](https://github.com/OpenVPN/openvpn-rfc/pull/5).

plaisthos is working to implement it in openvpn3 first.

MaxF reviewed the RFC and commented that it looks good.

- **Updated: DCO windows multi-peer**

Preparing patchset for the userspace implementation.

- **Updated: t_server_null improvements**

The LWIP ping testing in t_server_null.sh is somewhat working.

It is a bit tricky to get it right but then it seems to be working.

mattock will prepare a patch.

- **Updated: community.openvpn.net wiki**

A more suitable production deployment schema for otterwiki has been submitted upstream. That does not block us however.

mattock is ready to proceed and needs an EC2 instance in the community account for hosting production.

This instance can have some new address so we can start setting it up and migrating content.

After migrating data we can then remove the old wiki and put the new wiki on the address of the old one.

djpig or uddr35 can help to provide the instance and give mattock full access to it so he can then deploy the necessary otterwiki deployment on it.

- **New: snapshot releases via Chocolatey software**

mattock contacted the Chocolate package maintainer for OpenVPN and asked if he would be okay with publishing Windows MSI snapshots as well.

Seems like the maintainer is amenable to helping us achieve that goal.

- **Updated: --dns patch review upcoming**

d12fk patches are being made ready for gerrit review now - should arrive before next meeting.

- **multi-socket patch series**

Now in review.

- **push_update / live route updates**

There have been some initial tests on a server implementation in PG.

There is a server-side bug that will be fixed in PG, and a request to support a few more options (keepalive options).

lev__ will add keepalive to OpenVPN3 code.

mrbff and ordex will implement the openvpn2 server and client support for push_update.

- **TLS-exporter in mbedtls**

Needed for TLS 1.3 support with openvpn and mbedtls - TLS-exporter currently missing in mbedtls.

maxf reports he's making some progress on implementing this - currently working to ensure all unit tests in all million billions of configurations work.

- **buildbot improvements**

cron2 requests that we pretty please have a mingw build in gerrit. djpig indicates next week should be possible.

mattock has a patch to split the mails for different project to different mail addresses. The idea is to split openvpn3 and openvpn3-linux out so it doesn't go to openvpn-builds@ ML anymore.

Instead we could create a openvpn3-builds@ ML. djpig will look into that.

- **where next community meeting**

Italy or Spain have been mentioned.

Beer: yes.

T-shirts: yes.

- **Release 2.7**

Note: automatic enabling of --compression migrate was dropped from feature list since djpig discovered it is too complicated to get right.

---

- **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.

- **forums topics**

novaflash has access and is working on a PoC setup combining old and new on an ubuntu server.

- **Tunnelcrack progress [TunnelCrack community wiki article](https://openvpn.net/community-resources/tunnelcrack)**

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: 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.

- **run tests of 2.x against openvpn3? how?**

There is a 'null client' variant of ovpncli that allows to make VPN connections but not fully, for testing purposes.

This is in the openvpn3 repository.

- **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.

- **Community AWS account governance**

Currently the Community AWS account is part of the OpenVPN, Inc. AWS organization.

With the OTF founding there would be opportunity to move to a separate AWS account that is not under the corporate umbrella.

Requires further discussion whether that is something we want.

- **website release process**

Waiting for faster way to update community downloads and security advisories on main site.

Again postponed due to issues. Now planned for this week. We'll see.

- **Status of SBOM**

There was a discussion between MaxF and djpig and others.

For OpenVPN2 / OpenVPN-NL, there is not much overlap, as OpenVPN2 doesn't ship much in terms of libraries, but OpenVPN-NL does.

The interesting use-case for an SBOM is really the OpenVPN Windows GUI client.

- **Static-key mini how-to is outdated.**

This page is outdated badly: [https://openvpn.net/community-resources/static-key-mini-howto/](https://openvpn.net/community-resources/static-key-mini-howto/)

company will send this to tech writer to redo based on [https://github.com/OpenVPN/openvpn/blob/master/doc/man-sections/example-fingerprint.rst](https://github.com/OpenVPN/openvpn/blob/master/doc/man-sections/example-fingerprint.rst) info and also retain a link to that github doc.

having a simple guide online will help adoption

- **OpenVPN 2.6 performance results.**

tests should cover: gre, ipsec, userland, dco

linux, freebsd, windows

requires time to be dedicated to doing this, when time available will do it

- **What's going on with new taskbar icons?**

matt provided icons in [https://github.com/OpenVPN/openvpn-gui/issues/595](https://github.com/OpenVPN/openvpn-gui/issues/595)

last update: will be picked up by selva when he has time

- **software code signing topic**

company switched EV code signing to cloudhsm, this is same cert type we use for driver signing, is also suitable for binary signing.

in future we could possibly switch community to that same key. saves having to maintain 2 different keys.

depends on how hard/easy it is to access company key signing thingee from community infrastructure.

also no high priority at the moment, we have a working solution now.