Commit d47f6a
2026-04-15 11:48:40 novaflash: -/-| /dev/null .. Meetings/2026/2026-04-15.md | |
| @@ 0,0 1,55 @@ | |
| + | # Basic info |
| + | |
| + | * Time: Wednesday 15 April 2026 at 14:00 CEST (12:00 UTC) |
| + | * Place: #openvpn-meeting channel on !LiberaChat IRC network |
| + | |
| + | # Topics |
| + | |
| + | - **OpenSSL 4.0 support** |
| + | A few patches are needed in OpenVPN so it can all compile without warnings. |
| + | Patches are already up for review in Gerrit, but need review and merging. |
| + | |
| + | - **driver signing** |
| + | The current driver signing uses an EV key that expires April 15. We have a new one so we can do signing manually. |
| + | But we will discuss possible new automation for driver signing. Not a critical topic as we can do it manually, but should not forget. |
| + | |
| + | - **Tunnelblick security fix** |
| + | The following is information provided as a courtesy to people using Tunnelblick. The advice is to update to latest version to solve a security issue. |
| + | The details are unfortunately not known at the moment to OpenVPN Community itself, but there is an updated Tunnelblick release that fixes a particular CVE. |
| + | This is the currently available information from Tunnelblick website: https://tunnelblick.net/CVE-2026-31893.html |
| + | Questions regarding this should be directed to Tunnelblick. |
| + | |
| + | - **OpenVPN 2.7.1 release** |
| + | OpenVPN 2.7.1 was released on 31st of March. The main website will get the update soon, but on community.openvpn.net it can be found already now. |
| + | This is mostly a bugfix release. There are a few more DCO event handling fixes coming. |
| + | We intend to do a 2.6.20 release to bring some of these fixes done in 2.7 to 2.6 as well. Tentatively in 2 weeks from now. |
| + | |
| + | - **forums situation** |
| + | The header and footer were adjusted a while back to be more community focused. It's not entirely perfect yet but further improvements will be made. |
| + | Syzzer pointed out we have a 'responsible disclosure procedure' on our main website but it's not linked from the website footer anymore. |
| + | This will be fixed and also be added into the forum footer. |
| + | A policy document was made up for the forums, just a beginning; https://community.openvpn.net/Community%20Forum |
| + | |
| + | - **community meetup 2026** |
| + | Coordination is currently taking place here: https://community.openvpn.net/Meetups/2026-Paderborn |
| + | The date is around 17 and 18 October, location in Paderborn, Germany. |
| + | |
| + | - **2.7 security audit** |
| + | There are still things ongoing in regards to the security audit but no new major findings so far. |
| + | Still have items to review and go through, but this is ongoing. |
| + | |
| + | ## Backlog |
| + | |
| + | - **t_server and t_client testing framework** |
| + | mattock asked where to put the t_server stack as it is currently on ordex's open source fund funded AWS account but funds might dry up there. |
| + | Discussed option to move it to OpenVPN Inc. funded AWS community account. Will explore this option. |
| + | Needs to be picked up by either djpig or uddr. |
| + | |
| + | - **Tunnelcrack progress (see 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: block-local 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. |