- **Time:** Wednesday 23 October 2024 at 14:00 CEST (12:00 UTC)

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

- plaisthos has written a new draft for new key handling for the data channel based on discussions in Karlsruhe.

- See [GitHub PR](https://github.com/OpenVPN/openvpn-rfc/pull/5).

- Requesting feedback from community to review.

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

- ordex sent in **patchset version 9**. Got some small feedback, a v10 will be sent in this week.

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

- Getting closer - kernel side stuff seems to be getting near to completion. Will look at user-space part next.

- There were some issues building on Windows and some buildbot failures pointed out by djpig when merging the preparation work patches.

- These will be addressed in follow-up patches that are underway now.

- And then we'll move on to the real patch series.

- There were some clarification questions which resulted in the decision we should add a few clarifying words to the RFC.

- Implementation for OpenVPN v2 will be looked at by ordex and his team.

- Italy or Spain have been mentioned.

- Beer: yes.

- T-shirts: yes.

- The tests against latest git master server against older openvpn client versions are almost done.

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

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

- DNS patches were discussed during Meetup. d12fk will provide them for review real soon.

- Seems mattock managed to get it into a reasonable shape ready for production.

- Some required changes to otterwiki have been submitted upstream.

- Next step is looking at migrating data from old to new.

- Also djpig needs to provide an EC2 instance in the community account for hosting production.

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

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

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

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

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

- 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-howto](https://openvpn.net/community-resources/static-key-mini-howto/)

- company will send this to tech writer to redo based on [GitHub doc](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 [GitHub Issue](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 the moment, we have a working solution now.