> Hi, > > On Mon, Apr 05, 2021 at 10:16:07AM +0200, Simon Matter wrote: >> Then I misunderstood what is written here? >> >> https://community.openvpn.net/openvpn/wiki/DeprecatedOptions#Option:--compress >> >> "Compression is not recommended and is a feature users should avoid >> using. >> To signal this clearly, --comp-lzo and --compress are discouraged and >> considered deprecated features. Beginning with 2.5, these options will >> no >> longer enable compression, just enable the compression framing to be >> able >> to receive compressed packets." >> >> That made me feel compression support in 2.5 is only on a compatibility >> level. > > This is half-correct, and half-incomplete. Look at > > --allow-compression yes > > (new in 2.5). > > Yes, 2.5 will no longer send compressed packets unless explicitly > permitted > by "allow-compression yes" - but the infrastructure is still there, and > still tested, but moved from "this is something everybody will want" to > "if you know what you are doing and why, you can still have it". > > Regarding your other mail where you doubted that "there will be a > discussion" > - well, I can assure you that there are discussions about every feature we > take out of OpenVPN (and usually, mails to openvpn-devel and openvpn-users > to figure out who might still be using it). Many of these discussions do > not happen on the list but on the #openvpn-devel and #openvpn-meeting > IRC channels - but Samuli is sending the meeting minutes to the -devel > list (and they are on the trac web page), so we try to make transparent > what we discuss and why. > > > As always, code is a balance between features, maintenance effort, bugs, > and security... > > gert
Ok, thanks for explaining. Regards, Simon _______________________________________________ Openvpn-devel mailing list Openvpn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openvpn-devel
