Maybe: add key exchange plugin interface (allows easily doing. Route monitoring (enable clients to react to network changes) Unlikely to happen, keeping the list inner VRF support? Test framework improvements (local "make check" crypto tests) Maybe: fix radius-plugin - plugin is useful but not maintained very well Update OpenVPN PRF (move away from SHA1/MD5) Test server that does -auth-user-pass and/or challenge stuff Nice to have / wild ideas Task descriptionĭNS option rework (split DNS) - windows backendĪUTH_TEMP_FAIL ("I can not handle you *now*, but please come back later") Polish auth-token / auth-gen-token corner cases (not sending token after explicit-exit-notify from server, etc.)ĭDoS reflection hardening (rate-limiting) Now I fallback my OpenVPN Client to 2.5.8 (OpenVPN-2.5.8-I604-amd64.msi), the OpenVPN connection between my Win 10 PC and remote Netgear Router can be established again and resume normal. nobind for -pull by default ("random client port by default")ĭNS option rework (split DNS) - new option parsingĭo not push route-ipv6 entries that are also in the iroute-ipv6 list OpenSSL Config file handling ("where does an OpenVPN binary read OpenSSL config from, and why?") - windows build / private vcpkg? - unix builds - OpenVPN vs. Must have - completed/done Task description TLS handshake replay protection (up for discussion) Merged, fine tuning (/24-on-/24 iroute, peer stats, exit notification with stats) Merged, ironing out bugs (-windows-driver, -disable-dco quirks) Merged, now ironing out bugs (p2p reconnection) all "must have" code in and all major (crash) bugs fixed: Jan 11, 2023įeatures/fixes to include must have Task description.If you want all the details, see the Active Tickets by Milestone report. This page shows the high-level status of OpenVPN 2.6 release.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |