ronwit
Member
Budget King
- Joined:
- Jun 2024
- Posts:
- 122
- From:
- Osaka, Japan
Basically you can run openvpn in tls-cryptv2 mode for modern clients and legacy tls-auth for old ones same daemon actually, different ports (´・ω・`)
Actually I did this for my old company basically:
- Port 1194 udp = tls-cryptv2, aes-256-gcm, modern
- Port 1195 udp = legacy, bf-cbc, sha1, windows 7 happy
But basically the real answer is tell your client to get better IT policy (´・ω・`) no amount of backward compatibility is worth supporting EOL os
Actually sorry if my english is weird
instant noodles, instant deploys
sarahjey
Member
- Joined:
- Jul 2024
- Posts:
- 149
- From:
- Ottawa, Canada
Can't you just use a jump host?? Like the clients connect openvpn to a locked-down box, then that box connects wireguard to your real network??
I did something similar for my university project and it worked!! Double nat but who cares for a few clients??
Sorry if im missing something obvious!!
learning on $5 VPS and prayers
olespete
Member
Trust No One
- Joined:
- Jun 2024
- Posts:
- 270
- From:
- Unknown
Windows 7 in 2026 and banks still sign the cheques
airgapped, encrypted, faraday'd, still worried
ronwit
Member
Budget King
- Joined:
- Jun 2024
- Posts:
- 122
- From:
- Osaka, Japan
Which OpenVPN version handles both tls-cryptv2 and legacy?
2.6.x handles both but you need to compile with --enable-legacy-cipher or grab the community edition from openvpn.net repos. The stock debian/ubuntu package disables BF-CBC now.
Actually my config used server 2.5.8 because the company was too cheap to pay for access server licenses. Worked fine.
instant noodles, instant deploys