# IrcMeetings ## Basic info - **Time:** Wednesday 27 November 2024 at 14:00 CEST (12:00 UTC) - **Place:** #openvpn-meeting channel on LiberaChat IRC network ## Topics ### Current topics - **New: swupdate.openvpn.net/org cleanup** - *Basically, this has become a dumping ground for just about everything. We're cleaning it up.* - *Need to discuss how to handle community files that are on there.* - *A priority is to ensure no interruptions to existing content/links.* - *The plan we want to propose to OpenVPN Inc. is to get all proprietary stuff moved off of swupdate.openvpn.net, which seems to already be ongoing anyhow.* - *And then keep swupdate.openvpn.net purely for community and move the s3 bucket to community AWS account and reduce the amount of caching layers to just one.* - *Will relay this plan to OpenVPN Inc. and see what they say.* - **Updated: DCO Linux upstreaming** - *Upstreaming DCO to Linux is proceeding, it is in review stage at the moment.* - *patchset v12 had 2 weeks delay, hoping to get it out this week now. Main reason is having to deal with someone with a lot of comments to make.* - **Updated: 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.* - **Updated: t_server_null improvements** - *The LWIP ping testing in t_server_null.sh is working and a PR is up.* - **Updated: 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: [RFC Pull Request](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.* - **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 an openvpn3-builds@ ML. djpig will look into that.* - **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 [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 a faster way to update community downloads and security advisories on the 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: [Static Key Mini Howto](https://openvpn.net/community-resources/static-key-mini-howto/)* - *company will send this to tech writer to redo based on [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* - **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 [Taskbar Icons Issue](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 the same cert type we use for driver signing, is also suitable for binary signing.* - *in the 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.*