Opened 3 years ago
Closed 3 years ago
#1314 closed Feature Wish (fixed)
have IV_CIPHER in 2.4
Reported by: | Gert Döring | Owned by: | plai |
---|---|---|---|
Priority: | minor | Milestone: | release 2.4.10 |
Component: | Crypto | Version: | OpenVPN 2.4.9 (Community Ed) |
Severity: | Not set (select this one, unless your'e a OpenVPN developer) | Keywords: | |
Cc: |
Description
I think it would be a good thing for long-term compatibility reasons to backport the IV_CIPHER= infrastructure to 2.4
The capability to receive pushed ciphers is already there, but we cannot tell the server what we can handle - so moving to non-AES ciphers is some guesswork on the server side (OCC cipher + AES-128 + AES-256).
Change History (4)
comment:1 Changed 3 years ago by
Component: | Generic / unclassified → Crypto |
---|---|
Milestone: | → release 2.4.10 |
Owner: | set to Steffan Karger |
Priority: | major → minor |
Version: | OpenVPN 2.4.7 (Community Ed) → OpenVPN 2.4.9 (Community Ed) |
comment:2 Changed 3 years ago by
Owner: | changed from Steffan Karger to plaisthos |
---|---|
Status: | new → assigned |
comment:3 Changed 3 years ago by
Owner: | changed from plaisthos to plai |
---|
comment:4 Changed 3 years ago by
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Note: See
TracTickets for help on using
tickets.
commit f8c3e0aef2f6e03a0a5eafd81644c4079796649d (release/2.4)
Author: Arne Schwabe <arne@…>
Date: Sun Aug 30 16:07:36 2020 +0200
will be in 2.4.10, to be released "this week or so"