A minimalistic webapp in Go to service API/JSON for the LEAP VPN
You can pass generic configuration options either as a flag or an environment variable. Some specific options can be passed only as env vars (like authentication credentials).
|apiPath||/etc/leap/config/vpn||Path for the public API static files|
|providerCaCrt||/etc/leap/ca/ca.crt||Path for the provider CA certificate|
|port||8000||Port where the api server will listen|
|metricsPort||8001||Port where the metrics server will listen|
|tls||false||Enable TLS on the service|
|tlsCrt||Path to the cert file for TLS|
|tlsKey||Path to the key file for TLS|
|vpnCaCrt||Path to the CA public key used for VPN certificates|
|vpnCaKey||Path to the CA private key used for VPN certificates|
|auth||Authentication module to use (one of: sip2, anon)|
|authSecret||Authentication secret to sign auth tokens|
|passwordPolicy||require||Password policy, if used (one of: require, ignore)|
|Administrative user for the SIP2 telnet interface|
|Administrative pass for the SIP2 telnet interface|
|Host to connect to the SIP2 telnet interface|
|Port to connect to the SIP2 telnet interface|
|Library location identifier|
|Telnet terminator used by the endpoint (default: \r\n)|
We found that 0xacab.org/leap/vpnweb demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 0 open source maintainers collaborating on the project.
Did you know?
Socket installs a GitHub app to automatically flag issues on every pull request and report the health of your dependencies. Find out what is inside your node modules and prevent malicious activity before you update the dependencies.