# IrcMeetings ## Basic info - **Time:** Wednesday 4 December 2024 at 14:00 CEST (12:00 UTC) - **Place:** #openvpn-meeting channel on LiberaChat IRC network ## Topics ### Current topics - **New: no meetings on 25th of December, 1st of January** *For obvious reasons.* - **Updated: swupdate.openvpn.net/org cleanup** *Basic idea is agreed; set up a new S3 bucket in AWS community account, keep only community stuff there, move swupdate.openvpn.net/org domains there, have only 1 caching layer (not 2 like now).* *There will be some redirects for some of the company stuff that go to packages.openvpn.net.* - **Updated: DCO Linux upstreaming** *Upstreaming DCO to Linux is proceeding, it is in review stage at the moment.* *Patchset v12 has gone out and is under review.* *ordex reports that some of the test framework has been merged so it looks like there is some movement.* - **Updated: t_server_null improvements** *ovpnlwip seems to work fine on all linux platforms, based on buildbot tests.* *Waiting review.* - **Updated: buildbot improvements** *cron2 requests that we pretty please have a mingw build in gerrit. this has in the meantime materialized.* *mattock is looking into adding ubu24.04 clang+asan build.* - **Updated: multi-socket support** *Now in review. Patchset v8 should be going out this week.* - **Updated: new --dns option support** *Now in review. d12fk sent in patchset for new --dns option support.* - **community.openvpn.net wiki** *A more suitable production deployment schema for otterwiki has been submitted upstream. That does not block us however.* *uddr35 has arranged a node for mattock to use and the DNS record for it should be ready today.* *That means mattock will have access to a node to set things up on in the next few hours or so.* - **OpenVPN community meetup 2025** *When: september/october ish, a poll will be made soonish to gather people's availabilities.* *Where: Napoli, Italy.* *Meeting room: tbd.* *Hotel: tbd.* *Beer: yes.* *T-shirts: yes.* - **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.* - **DCO windows multi-peer** *Preparing patchset for the userspace implementation.* - **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.* - **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.* - **Release 2.7** *../../Development/StatusOfOpenvpn27 was updated with the results from Karlsruhe meetup.* *compare wiki:CommunityMeetup2024.* *Note: automatic enabling of --compression migrate was dropped from feature list since djpig discovered it is too complicated to get right.* ### Backlog - **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** *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.*