> Hi, > > On 03/04/2021 10:32, Simon Matter wrote: >> I'm not asking to enable it by default or even compile it by default. >> I'm >> only asking to keep the code in so those who know what they are doing >> can >> enable it as a compile time option or expert mode option or something >> like >> that. > > If you ask everybody, they always knew what they were doing, even when > something went wrong. > > If there is no real usecase for a feature, and this feature is known to > be a potential risk, it is our duty to make sure people will not shoot > themselves in the foot. > > If you have a use case that you think can benefit big time by having > compression, please feel free to describe it in details. Therefore might > be saner ways to address it. > > > If somebody feels being expert enough and knows what he is doing more > than the others, he can still re-add the feature (i.e. by reverting any > patch that might be removing the code) and recompile OpenVPN. The beauty > of Open Source :-)
I knew such answers will come :-) But, back to security, why do you still allow OpenVPN being built on M$ Windows then? That's the real place where people are comforted with snake oil and may be tempted to feel safe when using an OpenVPN tunnel but in reality are vulnerable. Isn't this much worse than leaving compression in as a compile time option? Simon _______________________________________________ Openvpn-devel mailing list Openvpn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openvpn-devel
