Meeting summary for 2 October 2024: * *Release 2.7* https://community.openvpn.net/openvpn/wiki/StatusOfOpenvpn27 was updated with the results from Karlsruhe meetup. Compare also https://community.openvpn.net/openvpn/wiki/CommunityMeetup2024 Note: automatic enabling of --compression migrate was dropped from feature list since the meeting 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 https://github.com/OpenVPN/openvpn-rfc/pull/5. 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. Regards, -- Frank Lichtenheld _______________________________________________ Openvpn-devel mailing list Openvpn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openvpn-devel
