define an MVP for a ready-to-use service
we should document what's the minimal functionality that an admin-facing self-contained service with obfsvpn needs to do. anjan's work on the docker container for the CI is probably a great foundation for this.
to simplify things, I would assume openvpn listens on ONE local port (in TCP mode) and obfsvpn listens on exactly ONE public port.
inputs:
- openvpn config file (standard)
- obfsvpn config file (flavor and port).
- state folder for crypto material.
- state folder for client certificate(s).
we are probably fine if we just delegate to the admin of the system the distribution of the vpn certificate and the obfs4 certificate.
ideally, we should also document how to generate new client certificates.
Edited by Kali Kaneko