openwisp / openwisp/netjsonconfig
[feature] Add support for tls-crypt instead of tls-auth
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Python
- Stars
- 388
- Forks
- 87
- Avg merge
- 1h 26m
- Merged PRs (30d)
- 4
Description
OpenVPN 2.4 onwards supports the tls-crypt option instead of tls-auth.
It would be great if OpenWISP would support this feature instead of just tls-auth.
From the OpenVPN 2.5. manual:
- Encrypt and authenticate all control channel packets with the key from keyfile. (See --tls-auth for more background.)
- Encrypting (and authenticating) control channel packets:
- provides more privacy by hiding the certificate used for the TLS connection,
- makes it harder to identify OpenVPN traffic as such,
- provides "poor-man's" post-quantum security, against attackers who will never know the pre-shared key (i.e. no forward secrecy).
- In contrast to --tls-auth, --tls-crypt does not require the user to set --key-direction.
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
No files, tests, or entry points are named. Search the repository for tls-auth and key-direction, then trace how OpenVPN options are represented; done means tls-crypt is supported as an alternative without requiring key-direction.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100