On 19/02/2024 20:28, selva.n...@gmail.com wrote:
From: Selva Nair <selva.n...@gmail.com>

Commits 7d48d31b, 39619b7f added support for inlining username
and, optionally, password.
Add a description of its usage in the man page.

Change-Id: I7a1765661f7676eeba8016024080fd1026220ced
Signed-off-by: Selva Nair <selva.n...@gmail.com>

Acked-by: Antonio Quartulli <a...@unstable.cc>

Does this have to go through gerrit?

  doc/man-sections/client-options.rst | 11 +++++++++++
  doc/man-sections/inline-files.rst   |  2 +-
  2 files changed, 12 insertions(+), 1 deletion(-)

diff --git a/doc/man-sections/client-options.rst 
index b92b1a46..b75fe5bd 100644
--- a/doc/man-sections/client-options.rst
+++ b/doc/man-sections/client-options.rst
@@ -73,6 +73,17 @@ configuration.
    If ``up`` is omitted, username/password will be prompted from the
+ This option can also be inlined
+  ::
+    <auth-user-pass>
+    username
+    [password]
+    </auth-user-pass>
+  where password is optional, and will be prompted from the console if
+  missing.
    The server configuration must specify an ``--auth-user-pass-verify``
    script to verify the username/password provided by the client.
diff --git a/doc/man-sections/inline-files.rst b/doc/man-sections/inline-files.rst
index f46301e8..ad02c855 100644
--- a/doc/man-sections/inline-files.rst
+++ b/doc/man-sections/inline-files.rst
@@ -5,7 +5,7 @@ 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`` and ``--verify-hash`` options.
+``--tls-crypt-v2``, ``--verify-hash`` and ``auth-user-pass`` options.
Each inline file started by the line ``<option>`` and ended by the line

Antonio Quartulli

Openvpn-devel mailing list

Reply via email to