Home A - Z
Page Index

An Otter Wiki

Blame

6f02e7 Samuli Seppänen 2025-01-29 06:40:08 1 
# IrcMeetings
2
3
## Basic info
4
5
- Time: Wednesday 30 October 2024 at 14:00 CEST (12:00 UTC)
6
- Place: #openvpn-meeting channel on LiberaChat IRC network
7
8
## Topics
9
10
### Current topics
11
12
- **Updated: DCO and Linux upstreaming, API change**
13
_Upstreaming DCO to Linux is proceeding, it is in review stage at the moment._
14
_ordex sent in **patchset version 11**. Awaiting feedback._
15
16
- **Updated: DCO windows multi-peer**
17
_Kernel-side stuff looks to be mostly done. Currently look into user-space stuff and some proper locking and memory management (refcounters etc)._
18
19
- **Updated: multi-socket patch series**
20
_4 preparation work patches were merged. Now it's on to the real patch series._
21
22
- **Updated: data format v3 / epoch data keys**
23
_plaisthos has written a new draft for new key handling for the data channel based on discussions in Karlsruhe._
24
_See <https://github.com/OpenVPN/openvpn-rfc/pull/5>._
25
_The current state is that the work for it is done but not yet sent in - plaisthos indicates he wants to test and implement it with openvpn3 before submitting it to openvpn2._
26
27
- **buildbot improvements**
28
_cron2 requests that we pretty please have a mingw build in gerrit. djpig indicates next week should be possible._
29
_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._
30
_Instead we could create a openvpn3-builds@ ML. djpig will look into that._
31
32
- **push_update / live route updates**
33
_There were some clarification questions which resulted in the decision we should add a few clarifying words to the RFC._
34
_Implementation for OpenVPN v2 will be looked at by ordex and his team._
35
36
- **where next community meeting**
37
_Italy or Spain have been mentioned._
38
_Beer: yes._
39
_T-shirts: yes._
40
41
- **t_server_null improvements**
42
_The tests against latest git master server against older openvpn client versions are almost done._
43
44
- **Release 2.7**
c9d9c9 Samuli Seppänen 2025-01-29 12:06:32 45
_../../Development/StatusOfOpenvpn27 was updated with the results from Karlsruhe meetup._
6f02e7 Samuli Seppänen 2025-01-29 06:40:08 46
_compare wiki:CommunityMeetup2024._
47
_Note: automatic enabling of --compression migrate was dropped from feature list since djpig discovered it is too complicated to get right._
48
49
- **2.7 security audit**
50
_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._
51
52
### Backlog
53
54
- **--dns patch review upcoming**
55
_DNS patches were discussed during Meetup. d12fk will provide them for review real soon._
56
57
- **community.openvpn.net trac wiki**
58
_Seems mattock managed to get it into a reasonable shape ready for production._
59
_Some required changes to otterwiki have been submitted upstream._
60
_Next step is looking at migrating data from old to new._
61
_Also djpig needs to provide an EC2 instance in the community account for hosting production._
62
63
- **forums topics**
64
_novaflash has access and is working on a PoC setup combining old and new on an ubuntu server._
65
66
- **Tunnelcrack progress**
67
_Status update on TunnelCrack mitigations:_
68
_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._
69
_Windows, openvpn2: merged to master, not to 2.6.x. openvpn3: in code review._
70
_Linux, openvpn2: in progress. openvpn3: in progress._
71
_macOS: to be determined._
72
_iOS: to be determined._
73
_Android: not vulnerable._
74
75
- **run tests of 2.x against openvpn3? how?**
76
_There is a 'null client' variant of ovpncli that allows to make VPN connections but not fully, for testing purposes._
77
_This is in the openvpn3 repository._
78
79
- **donation collection**
80
_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._
81
_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._
82
_There are some options to consider. There may be existing solutions that we want to consider._
83
_PayPal seems overly expensive with all their fees._
84
_Stripe could be worth considering for credit card processing._
85
_GitHub Sponsors was mentioned as a possible solution, this is worth investigating._
86
_Open Collective was also mentioned, that needs some investigating how that exactly would work for us._
87
88
- **Community AWS account governance**
89
_Currently the Community AWS account is part of the OpenVPN, Inc. AWS organization_
90
_With the OTF founding there would be opportunity to move to a separate AWS account that is not under the corporate umbrella._
91
_Requires further discussion whether that is something we want._
92
93
- **website release process**
94
_Waiting for faster way to update community downloads and security advisories on main site._
95
_Again postponed due to issues. Now planned for this week. We'll see._
96
97
- **Status of SBOM**
98
_There was a discussion between MaxF and djpig and others._
99
_For OpenVPN2 / OpenVPN-NL, there is not much overlap, as OpenVPN2 doesn't ship much in terms of libraries, but OpenVPN-NL does._
100
_The interesting use-case for an SBOM is really the OpenVPN Windows GUI client._
101
102
- **Static-key mini how-to is outdated.**
103
_This page is outdated badly: <https://openvpn.net/community-resources/static-key-mini-howto/>_
104
_company will send this to tech writer to redo based on <https://github.com/OpenVPN/openvpn/blob/master/doc/man-sections/example-fingerprint.rst> info and also retain a link to that github doc._
105
_having a simple guide online will help adoption_
106
107
- **OpenVPN 2.6 performance results.**
108
_tests should cover: gre, ipsec, userland, dco_
109
_linux, freebsd, windows_
110
_requires time to be dedicated to doing this, when time available will do it_
111
112
- **What's going on with new taskbar icons?**
113
_matt provided icons in <https://github.com/OpenVPN/openvpn-gui/issues/595>_
114
_last update: will be picked up by selva when he has time_
115
116
- **software code signing topic**
117
_company switched EV code signing to cloudhsm, this is same cert type we use for driver signing, is also suitable for binary signing._
118
_in future we could possibly switch community to that same key. saves having to maintain 2 different keys._
119
_depends on how hard/easy it is to access company key signing thingee from community infrastructure._
120
_also no high priority at the moment, we have a working solution now._