IrcMeetings
Basic info
- Time: Wednesday 2nd October 2024 at 14:00 CEST (12:00 UTC)
- Place: #openvpn-meeting channel on LiberaChat IRC network
Topics
Current topics
Release 2.7
StatusOfOpenvpn27 was updated with the results from Karlsruhe meetup.
Compare CommunityMeetup2024.
Note: automatic enabling of --compression migrate was dropped from feature list since djpig discovered it is too complicated to get right.Updated: multi-socket patch series
New version of the patch series is posted. Reviews welcome :)Updated: DATA_V3 patch
plaisthos has written a new draft for new key handling for the data channel based on discussions in Karlsruhe.
See DATA_V3 patch PR. Feedback welcome :)Updated: buildbot improvements
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.Updated: t_server_null improvements
mattock plans to work on improving stability of the test first. At the moment, if the test fails to clean up it can easily leave the worker in a state where all future tests fail.
Next feature plans are to add more cross-version tests. E.g. have a test for release/2.6 <-> master in buildbot.New: 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.
Backlog
--dns patch review upcoming
DNS patches were discussed during Meetup. d12fk will provide them for review real soon.DCO and Linux upstreaming, API change
Upstreaming DCO to Linux is proceeding, it is in review stage at the moment.
ordex is collecting feedback on patchset version 7. Plan is to send v8 by end of month.
During meetup it was discussed that if the patchset does not make it into the kernel before 2.7 we should update the out-of-tree module to match the new API anyway. So that 2.7 supports the new API and we need no or minimal further changes to work with the eventual in-tree version.live route updates
PR to RFC was merged. Live route updates PR
Now we need to complete the actual implementations.
Implementation for OpenVPN v2 will be looked at by ordex and his team.
lev is working on (client-side) implementation in OpenVPN 3.community.openvpn.net trac wiki
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.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
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.Security mailing list
Static-key mini how-to is outdated.
This page is outdated badly: Static Key Mini How-To
The company will send this to a tech writer to redo based on Example Fingerprint 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
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 two 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.