kylemanna / kylemanna/docker-openvpn
clients with `ns-cert-type server` in their config fail
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 9.1k
- Forks
- 2.4k
- PR merge metrics
- No merged PRs in 30d
Description
Unfortunately I'm stuck using a piece of hardware with "OpenVPN support". And one of the things in its config which I cannot change is ns-cert-type server. I've found http://blog.dutchcoders.io/configuring-openvpn-using-easyrsa/ and I am trying to implement it. It just feels like something that should be fixed upstream.
If you know what to change on the OpenVPN server to fix this, please share.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the linked EasyRSA/OpenVPN configuration guide and compare its certificate settings with the client’s fixed ns-cert-type server option. Reproduce the connection failure against this Docker OpenVPN server, then determine whether a server-side configuration can support the legacy option and document the result.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- networking, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100