Commit d199ed
2025-10-15 11:53:15 novaflash: -/-| /dev/null .. Meetings/2025/2025-10-15.md | |
| @@ 0,0 1,70 @@ | |
| + | # Basic info |
| + | |
| + | * Time: Wednesday 15 October 2025 at 14:00 CEST (12:00 UTC) |
| + | * Place: #openvpn-meeting channel on !LiberaChat IRC network |
| + | |
| + | # Topics |
| + | |
| + | - **Updated: Release 2.7** |
| + | OpenVPN 2.7 beta3 was released 13 October. |
| + | It looks like next up will be beta4, after which a rc1 or stable release is expected, after the hackathon end of October. |
| + | Tentative date for a beta4 is ?. |
| + | |
| + | - **Updated: wolfSSL license changed from gplv2 to gplv3** |
| + | The release notes of wolfSSL indicate the license changed to GPLv3. This basically makes wolfSSL incompatible in regards to licensing with OpenVPN. |
| + | There is ongoing communication with wolfSSL regarding this issue, they suggested a meeting, we agreed. |
| + | Currently our position is still that if there is no resolution by 15th of October, then OpenVPN 2.7.0 goes out without wolfSSL support. |
| + | We will reevaluate at today's meeting. |
| + | |
| + | - **Updated: OpenVPN community meetup 2025** |
| + | https://community.openvpn.net/openvpn/wiki/CommunityMeetup2025 |
| + | When: 25 and 26 october (Saturday and Sunday), with travel days on the Friday before and Monday after. |
| + | Where: Naples, Italy. |
| + | Meeting room: https://www.hotelparadisonapoli.it/en/home-page.aspx |
| + | Hotel: Paradiso Napoli Hotel. |
| + | Beer: yes. |
| + | T-shirts: design being made ready. |
| + | The design was delivered, and we need to order. Idea is to have it sent directly to the hotel. |
| + | |
| + | - **t_server and t_client testing framework** |
| + | mattock reports that he's started publishing his work for t_server in this location: |
| + | https://github.com/mattock/openvpn-tests/tree/t_server_template/t_server |
| + | |
| + | - **forums situation** |
| + | minx from OpenVPN Inc. offered to set up a new forum and help us migrate old data to it. |
| + | Unfortunately minx left the company. He did hand over all his work though to other people. |
| + | OpenVPN Inc. website team has put this on their roadmap, to work on it further. So let's give them a chance. |
| + | |
| + | ## Backlog |
| + | |
| + | - **format code using clang formatting** |
| + | It seems prudent to do this before the real 2.7 release. |
| + | It was discussed and there's some additional work to be paid either on reviewer or submitter side. |
| + | Strategy will be; get all code into beta1, collect bugfixes, reformat everything, then beta2. |
| + | Collect more bugfixes and then do release 2.7.0 and branch it off into its own release branch. |
| + | |
| + | - **push_update / live route updates** |
| + | Client-side support for push_update is now merged. |
| + | For server-side support, company did QA on it with openvpn2 but found some missing features that are being added now. |
| + | Client-side support made it into alpha3. |
| + | |
| + | - **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. |
| + | |
| + | - **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. |
| + | |
| + | - **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. |