- **Time:** Wednesday 29 May 2024 at 14:00 CEST (12:00 UTC)

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

- There was a responsible disclosure report made regarding DCO windows driver.

- This was fixed and released in the I003 Windows installer release for 2.6.10.

- There was some downtime here and after looking into it, the conclusion is that the software is out-of-date and needs love.

- We were already planning to migrate to another wiki solution, so this has provided an impetus to accelerate this.

- mattock will look into putting a PoC of wiki.js and outline after debian/ubuntu snapshot task is done.

- Waiting to complete review/merge process of Windows tunnelcrack mitigations.

- For the proposed Linux tunnelcrack mitigations, going for policy routing and such, it may need to go to 2.7 and it's quite a big change.

- There's an item reported by reynir that we'll likely want to get into this release as well.

- There's a wiki page up now where we can coordinate: [CommunityMeetup2024](https://community.openvpn.net/openvpn/wiki/CommunityMeetup2024)

- We're basically at the point where we can prepare a mailing and send out invites to people.

- Where: Karlsruhe, Germany. Exact details of meeting room to be determined.

- When: Set to 20-22 September 2024.

- Shirts: novaflash will talk to matt about this.

- There is code waiting for review/merging but one of the reviewers is on vacation.

- Will in the meantime tackle the community.openvpn.net / wiki topic.

- Wrapping up debian/ubuntu snapshot building. It already works but wants to clean things up and make a PR.

- rob0 and novaflash will work to get access and then find some time to look at solving the cloudflare related issue.

- Unfortunately the past weeks were difficult to find time - holidays and travel and such. Will find time and push this forward.

- Plan is to soon switch URLs so new forum is on forums.openvpn.net and old forums is on archive address.

- - email confirmation on registration was suggested.

- - mod permissions, guide, hard or soft delete (chuck board?), what to do with GDPR, etc. (write it down and actually make it available to mods, maybe a hidden topic)

- - access for mods to logs so one can see what others did

- Status update on TunnelCrack mitigations:

- Windows, openvpn2: ready to merge. openvpn3: in code review.

- Linux, openvpn2: in progress. openvpn3: in progress.

- macOS: to be determined.

- iOS: to be determined.

- Android: not vulnerable.

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

- ordex will send a patchset v3 based on feedback received today.

- There will be an API change that makes it incompatible with the current implementation.

- A graceful solution to that was already discussed and in motion. giaan will be working on this.

- (in a nutshell, make OpenVPN understand old and new API, DKMS and kernel versions both will then use new API, then we drop old API)

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

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

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

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

- company will send this to tech writer to redo based on [Github example-fingerprint](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

- tests should cover: gre, ipsec, userland, dco

- linux, freebsd, windows

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

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

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

- 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 this moment, we have a working solution now.

- **Management interface documentation on main website will be updated with info from doc/management-notes.txt**

- novaflash will pick this up at some point

Latest status in [ServerSideTestingImprovementPlan](https://github.com/mattock/openvpn/blob/dev_null/doc/dev-null-test-suite.rst). Additional details in [dev-null-test-suite](https://github.com/mattock/openvpn/blob/dev_null/doc/dev-null-test-suite.rst). Current PoC code is available in mattock's "dev_null" branch. A good starting point is [t_server_null.sh](https://github.com/mattock/openvpn/blob/dev_null/tests/t_server_null.sh).

Potential next steps:

- Expand the test suite

- Integrate into Buildbot (i.e. get to production)

- Support multiple client versions (depends on Buildbot integration)

Git commit history needs to be cleaned up and there may be other small fixes / improvements here and there to be done:

- Enable disabling the test suite (requires root so we can't run it by default)

- In a previous meeting we agreed to publish snapshot Debian/Ubuntu packages on *build.openvpn.net*

- The tool to use to publish is [aptly](https://www.aptly.info/)

- aptly does not have direct support for running commands (e.g. rsync, scp) after publishing packages, e.g. to a local filesystem on the buildmaster

- **Option 1 (hacky):** use `inotifywait` with `rsync` or `scp` to copy the published repo to build.openvpn.net

- **Option 2 (less hacky):** use `NFS` to publish "directly" to build.openvpn.net

- Both options require a fair amount of tinkering

- Mattock moved this forward a bit at the buildbot end (get the files out from workers)