mirror of
https://github.com/OpenVPN/openvpn.git
synced 2024-09-19 19:42:30 +02:00
fad2d7017e
Commits7d48d31b,39619b7fadded support for inlining username and, optionally, password. Add a description of its usage in the man page. Github: resolves OpenVPN/openvpn#370 Change-Id: I7a1765661f7676eeba8016024080fd1026220ced Signed-off-by: Selva Nair <selva.nair@gmail.com> Acked-by: Antonio Quartulli <antonio@openvpn.net> Message-Id: <20240220175215.2731491-1-selva.nair@gmail.com> URL: https://www.mail-archive.com/openvpn-devel@lists.sourceforge.net/msg28284.html Signed-off-by: Gert Doering <gert@greenie.muc.de>
26 lines
834 B
ReStructuredText
26 lines
834 B
ReStructuredText
INLINE FILE SUPPORT
|
|
===================
|
|
|
|
OpenVPN allows including files in the main configuration for the ``--ca``,
|
|
``--cert``, ``--dh``, ``--extra-certs``, ``--key``, ``--pkcs12``,
|
|
``--crl-verify``, ``--http-proxy-user-pass``, ``--tls-auth``,
|
|
``--auth-gen-token-secret``, ``--peer-fingerprint``, ``--tls-crypt``,
|
|
``--tls-crypt-v2``, ``--verify-hash`` and ``--auth-user-pass`` options.
|
|
|
|
Each inline file started by the line ``<option>`` and ended by the line
|
|
``</option>``
|
|
|
|
Here is an example of an inline file usage
|
|
|
|
::
|
|
|
|
<cert>
|
|
-----BEGIN CERTIFICATE-----
|
|
[...]
|
|
-----END CERTIFICATE-----
|
|
</cert>
|
|
|
|
When using the inline file feature with ``--pkcs12`` the inline file has
|
|
to be base64 encoded. Encoding of a .p12 file into base64 can be done
|
|
for example with OpenSSL by running :code:`openssl base64 -in input.p12`
|