Opened 4 years ago
Closed 3 years ago
#1393 closed FRP - Feature Removal Process (Only for OpenVPN developers) (wontfix)
Deprecation notice: Compression --comp-lzo --compress
Reported by: | tct | Owned by: | |
---|---|---|---|
Priority: | minor | Milestone: | release 2.6 |
Component: | Generic / unclassified | Version: | OpenVPN 2.5.0 (Community Ed) |
Severity: | FRP - Phase 1 | Keywords: | compress comp-lzo |
Cc: |
Description
At the time of creating this ticket, Openvpn has not decided if supporting built-in compression should remain a feature.
Deprecation warnings:
https://community.openvpn.net/openvpn/wiki/DeprecatedOptions#Option:--comp-lzo
https://community.openvpn.net/openvpn/wiki/DeprecatedOptions#Option:--compress
- Note: This ticket is preliminary and under review.
Suggestion: Because trac gets more eyes, this is a better place to keep trac of important issues.
Change History (3)
comment:2 Changed 3 years ago by
Not sure what the point of this ticket is?
The road is clear: compression will go away, because it is time-intensive to maintain, because the benefit is small (most traffic transported today is either pre-compressed or encrypted, so lzo/lz4 won't bring benefits), *and* there are attacks against the VPN security enabled by compression.
The only thing that is not clear is "when" - and that's likely in the 2.7 or 2.8 time frame.
comment:3 Changed 3 years ago by
Resolution: | → wontfix |
---|---|
Status: | assigned → closed |
I was testing the Feature removal process here on trac but I guess this is just more noise.
Comment for subscription purposes:
Personally, I would prefer that
compression remain as a featureI will also update the deprecated-options page above (for compression specific options) to point here, if this ticket is accepted.