Opened 8 years ago
Closed 6 years ago
#720 closed Feature Wish (fixed)
Add tls-auth to <connection> profiles.
Reported by: | duren | Owned by: | Steffan Karger |
---|---|---|---|
Priority: | minor | Milestone: | release 2.5 |
Component: | Configuration | Version: | OpenVPN git master branch (Community Ed) |
Severity: | Not set (select this one, unless your'e a OpenVPN developer) | Keywords: | multiple remote tls-auth connection profile |
Cc: | plai, Steffan Karger |
Description
I would like to take advantage of multiple remote statements for connection redundancy but cannot because my current provider has different tls-auth keys for every server.
Please enable the tls-auth directive for use with a connection profile.
Ideally, certs would be accepted there as well.
Change History (8)
comment:1 Changed 7 years ago by
Cc: | plai Steffan Karger added |
---|---|
Version: | 2.2.2 → git master branch |
comment:2 Changed 7 years ago by
Currently writing my own updown script to manually run a one of many specific config/ca/tls combinations.. This would be pretty awesome and simplify my helper scripts :)
comment:3 Changed 7 years ago by
Owner: | set to Steffan Karger |
---|---|
Status: | new → accepted |
Makes sense. I have no idea how hard it would be, but we should definitely look into it.
comment:4 Changed 7 years ago by
Milestone: | → release 2.5 |
---|
comment:5 Changed 6 years ago by
@syzzer is this still something we'd consider valuable? If so, I guess we'd like the same for tls-crypt, right?
comment:6 Changed 6 years ago by
some potential patches implementing this feature have been provided at (tls-auth):
https://sourceforge.net/p/openvpn/mailman/openvpn-devel/thread/20180602034206.9459-1-a%40unstable.cc/#msg36333100
and (tls-crypt):
https://sourceforge.net/p/openvpn/mailman/openvpn-devel/thread/20180602034206.9459-2-a%40unstable.cc/#msg36332760
comment:7 Changed 6 years ago by
new versions of these patches are being posted to the mailing list. Please follow there if interested.
comment:8 Changed 6 years ago by
Resolution: | → fixed |
---|---|
Status: | accepted → closed |
Both patches have been merged into master. They will be released with OpenVPN 2.5.
Closing the ticket as the issues should now be fixed.
@plai, @syzzer: any idea how complicated this would be?