there's quite an interesting patchset https://patchwork.openvpn.net/project/openvpn2/list/?series=230 is it scheduled for 2.5 release ?
or I've missed something and all patches are scheduled for 2.5 ? ср, 24 июн. 2020 г. в 16:11, Samuli Seppänen <sam...@openvpn.net>: > Hi, > > Here's the summary of the IRC meeting. > > --- > > COMMUNITY MEETING > > Place: #openvpn-meeting on irc.freenode.net > Date: Wed 24th June 2020 > Time: 11:30 CEST (9:30 UTC) > > Planned meeting topics for this meeting were here: > > <https://community.openvpn.net/openvpn/wiki/Topics-2020-06-24> > > Your local meeting time is easy to check from services such as > > <http://www.timeanddate.com/worldclock> > > SUMMARY > > cron2, dazo, lev, mattock, plaisthos and uip participated in this meeting. > > --- > > Talked about the status of OpenVPN 2.5: > > <https://community.openvpn.net/openvpn/wiki/StatusOfOpenvpn25> > > Ordex promised to have a look at the async-cc patches this week. > Plaisthos, dazo and cron2 will follow-up on the review comments to get > them resolved quickly. > > OpenVPN 2.5 MSI looks surprisingly good. Mattock was able to produce > tap-windows6 MSM ("merge module") which he then used to produce OpenVPN > 2.5-based MSI installer. The only significant challenge is adding > code-signing support to openvpn-build/generic. > > Automating MSI builds also seems easier than expected, given that the > existing openvpn-build buildslave can perform the actual build and push > the artifacts to the Windows packager, which can then build and push the > results to build.openvpn.net. > > Code-vise 2.5-alpha1 is in a good shape, mainly missing > > - compression > - async cc > - VRF (which is quite trivial) > > The auth-token fixes are corner-cases and it was agreed that that can be > resolved between 2.5-alpha1 and 2.5-beta1. > > --- > > Talked about moving 2.3 into "oldstable" support mode. Previously we had > agreed to do that when 2.3.19 was released. However, 2.3.18 was released > a long while ago and there's nothing queued for 2.3.19. So it was > decided to move 2.3 to "oldstable" now instead of later. > > --- > > Talked about starting the deprecation of "--ncp-disable". The idea is > that --ncp-disable has been mostly a debug feature and as we move > forward and want to be able to manage VPN security more from server > side, we want to abandon the possibility to ignore NCP. > > This is tied with deprecation of --cipher for everything except p2p: > > > https://www.mail-archive.com/openvpn-devel@lists.sourceforge.net/msg20062.html > > Uip will bring these topics up with syzzer a.s.a.p. > > --- > > Talked about OpenVPN 2.6. There are several things that are 2.6 material: > > - Kernel acceleration module (client-side only beta ~next week) > - Work related to "making DNS handling nice" > > It is possible that we'd also need to postpone the --ncp-disable and > --cipher changes. > > However, it was agreed that doing a "quick" 2.6 release in, say, early > 2021 is doable. It was also agreed that supporting both 2.5 and 2.6 as > "stable" for a while would be acceptable, as the changes would be mostly > in OpenVPN and the same release and automation tooling could be used for > both. > > --- > > Talked about our use of IV_*. Agreed that rather than having tons of > IV_FOO=1 options IV_PROTO should be considered a wire-protocol-only > 64-bit mask field and IV_FEAT would be a new 64-bit mask field > indicating which features the local side supports. > > OpenVPN will need to handle a remote side not providing IV_FEAT. > Default behaviour when this field is missing must be documented. > IV_FEAT should be sent by OpenVPN 2.6 and newer. This approach allows > easier deprecation of features as well. > > -- > > Full chatlog attached > _______________________________________________ > Openvpn-devel mailing list > Openvpn-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/openvpn-devel >
_______________________________________________ Openvpn-devel mailing list Openvpn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openvpn-devel
