openwisp / openwisp/openwisp-controller
[feature] Allow changing default certificate settings, e.g. set x509 extensions for automatic tunnel provisioning
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 773
- Forks
- 315
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 14
Description
To be able to use the OpenVPN remote-cert-tls server option (see the OpenVPN manual), the server certificate needs to be created with an extended key usage of "TLS Web Server Authentication". When manually creating a certificate in OpenWISP, the Extensions field can be used with the below settings to add the needed extended key usage:
[ {
"name": "extendedKeyUsage",
"critical": true,
"value": "serverAuth"
} ]
Unfortunately the extension cannot be set on the certificate created via the "Automatic tunnel provisioning" feature -> it would be great if there would be an option to change the settings of the automatically created certificates. e.g. if one use the automatically created certificates not just for the OpenVPN client but also as a OpenVPN server certificate.
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 tracing the certificate creation path used by Automatic tunnel provisioning and compare it with the manual certificate Extensions field described in the issue. Done means automatically created certificates accept configurable extension settings and can include extendedKeyUsage=serverAuth for OpenVPN server use.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- django, python
- Domain
- backend, networking, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100