Blame
| 6f02e7 | Samuli Seppänen | 2025-01-29 06:40:08 | 1 | # IrcMeetings |
| 2 | ||||
| 3 | ## Basic info |
|||
| 4 | ||||
| 5 | - **Time:** Wednesday 5 June 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 | - **New, closed: no community meeting on 12 June 2024** |
|||
| 13 | Due to an event that a large amount of people will attend, this particular day will be inconvenient to do a meeting. |
|||
| 14 | Meetings will resume the week after on 19 June 2024. |
|||
| 15 | ||||
| 16 | - **Updated: Buildbot and t_server null** |
|||
| 17 | Builds were failing because worker containers have not been rebuilt. |
|||
| 18 | This issue was resolved between mattock and djpig. |
|||
| 19 | ||||
| 20 | - **Updated: community.openvpn.net trac wiki** |
|||
| 21 | It turned out that outline is not really open source, it has BSL 1.1 license. Not suitable for us. |
|||
| 22 | Wiki.js still seems at the moment the direction we want to go. To be sure leoossa will present some workflows to test. |
|||
| 23 | Based on the results of those tests we can then see where the limitations of wiki.js are, and then we can see if those are dealbreakers or not. |
|||
| 24 | ||||
| 25 | - **Updated: release openvpn 2.6.11** |
|||
| 26 | Waiting to complete review/merge process of Windows tunnelcrack mitigations. |
|||
| 27 | Waiting to complete review/merge process of item reported by reynir. |
|||
| 28 | Once those items are in we'll prepare for a release, tentatively in 2 weeks from now. |
|||
| 29 | ||||
| 30 | - **Updated: DCO and Linux upstreaming, API change** |
|||
| 31 | Upstreaming DCO to Linux is proceeding, it is in review stage at the moment. |
|||
| 32 | ordex will send a **patchset v4** based on feedback received over the past days. |
|||
| 33 | There will be an API change that makes it incompatible with the current implementation. |
|||
| 34 | A graceful solution to that was already discussed and in motion. giaan will be working on this. |
|||
| 35 | (in a nutshell, make OpenVPN understand old and new API, DKMS and kernel versions both will then use new API, then we drop old API) |
|||
| 36 | ||||
| 37 | - **OpenVPN community meetup 2024** |
|||
| 38 | There's a wiki page up now where we can coordinate: [CommunityMeetup2024](https://community.openvpn.net/openvpn/wiki/CommunityMeetup2024) |
|||
| 39 | We're basically at the point where we can prepare a mailing and send out invites to people. |
|||
| 40 | Where: Karlsruhe, Germany. Exact details of meeting room to be determined. |
|||
| 41 | When: Set to 20-22 September 2024. |
|||
| 42 | Shirts: novaflash will talk to matt about this. |
|||
| 43 | ||||
| 44 | - **forums topics** |
|||
| 45 | rob0 and novaflash will work to get access and then find some time to look at solving the cloudflare related issue. |
|||
| 46 | Unfortunately the past weeks were difficult to find time - holidays and travel and such. Will find time and push this forward. |
|||
| 47 | Plan is to soon switch URLs so new forum is on forums.openvpn.net and old forums is on archive address. |
|||
| 48 | - email confirmation on registration was suggested. |
|||
| 49 | - mod permissions, guide, hard or soft delete (chuck board?), what to do with GDPR, etc. (write it down and actually make it available to mods, maybe a hidden topic) |
|||
| 50 | - access for mods to logs so one can see what others did |
|||
| 51 | ||||
| 52 | - **Tunnelcrack progress** |
|||
| 53 | Status update on TunnelCrack mitigations: |
|||
| 54 | Windows, openvpn2: ready to merge. openvpn3: in code review. |
|||
| 55 | Linux, openvpn2: in progress. openvpn3: in progress. |
|||
| 56 | macOS: to be determined. |
|||
| 57 | iOS: to be determined. |
|||
| 58 | Android: not vulnerable. |
|||
| 59 | ||||
| 60 | - **donation collection** |
|||
| 61 | 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. |
|||
| 62 | 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. |
|||
| 63 | There are some options to consider. There may be existing solutions that we want to consider. |
|||
| 64 | PayPal seems overly expensive with all their fees. |
|||
| 65 | Stripe could be worth considering for credit card processing. |
|||
| 66 | GitHub Sponsors was mentioned as a possible solution, this is worth investigating. |
|||
| 67 | Open Collective was also mentioned, that needs some investigating how that exactly would work for us. |
|||
| 68 | ||||
| 69 | - **website release process** |
|||
| 70 | Waiting for faster way to update community downloads and security advisories on main site. |
|||
| 71 | Again postponed due to issues. Now planned for this week. We'll see. |
|||
| 72 | ||||
| 73 | - **Status of SBOM** |
|||
| 74 | There was a discussion between MaxF and djpig and others. |
|||
| 75 | For OpenVPN2 / OpenVPN-NL, there is not much overlap, as OpenVPN2 doesn't ship much in terms of libraries, but OpenVPN-NL does. |
|||
| 76 | The interesting use-case for an SBOM is really the OpenVPN Windows GUI client. |
|||
| 77 | ||||
| 78 | - **Security mailing list** |
|||
| 79 | ||||
| 80 | - **Static-key mini how-to is outdated.** |
|||
| 81 | This page is outdated badly: [Static Key Mini How-to](https://openvpn.net/community-resources/static-key-mini-howto/) |
|||
| 82 | 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. |
|||
| 83 | having a simple guide online will help adoption |
|||
| 84 | ||||
| 85 | - **OpenVPN 2.6 performance results.** |
|||
| 86 | tests should cover: gre, ipsec, userland, dco |
|||
| 87 | linux, freebsd, windows |
|||
| 88 | requires time to be dedicated to doing this, when time available will do it |
|||
| 89 | ||||
| 90 | - **What's going on with new taskbar icons?** |
|||
| 91 | matt provided icons in [GitHub Issue #595](https://github.com/OpenVPN/openvpn-gui/issues/595) |
|||
| 92 | last update: will be picked up by selva when he has time |
|||
| 93 | ||||
| 94 | - **software code signing topic** |
|||
| 95 | company switched EV code signing to cloudhsm, this is same cert type we use for driver signing, is also suitable for binary signing. |
|||
| 96 | in future we could possibly switch community to that same key. saves having to maintain 2 different keys. |
|||
| 97 | depends on how hard/easy it is to access company key signing thingee from community infrastructure. |
|||
| 98 | also no high priority at the moment, we have a working solution now. |
