[taler-docs] branch master updated: ebics-setup manpage

[gnunet]

This is an automated email from the git hooks/post-receive script.

ms pushed a commit to branch master
in repository docs.

The following commit(s) were added to refs/heads/master by this push:
     new 9380147f ebics-setup manpage
9380147f is described below

commit 9380147fce094c26d76a11f86ae44b064a086cdd
Author: MS <ms@taler.net>
AuthorDate: Sat Oct 28 11:56:36 2023 +0200

    ebics-setup manpage
---
 manpages/libeufin-nexus.1.rst | 22 +++++++++++++++++++++-
 1 file changed, 21 insertions(+), 1 deletion(-)

diff --git a/manpages/libeufin-nexus.1.rst b/manpages/libeufin-nexus.1.rst
index 1bfb3dcf..253f1b38 100644
--- a/manpages/libeufin-nexus.1.rst
+++ b/manpages/libeufin-nexus.1.rst
@@ -36,10 +36,30 @@ Its options are as follows:
 
 The interaction model is as follows:
 
-In order to operate any EBICS communication with ``libeufin-nexus``, it is 
necessary to setup EBICS access via the ``ebics-setup`` subcommand.  Setting 
the access means to share the client keys with the bank, downloading the bank 
keys, and obtaining some basic information about the bank account that is 
associated to the client.  After a successful setup, the subcommands 
``ebics-submit`` and ``ebics-fetch`` can be run to respectively send payments 
and download the bank account history.
+In order to operate any EBICS communication with ``libeufin-nexus``, it is 
necessary to setup EBICS access via the ``ebics-setup`` subcommand.  Setting 
the access means to share the client keys with the bank and downloading the 
bank keys.  After a successful setup, the subcommands ``ebics-submit`` and 
``ebics-fetch`` can be run to respectively send payments and download the bank 
account history.
 
 The following sections describe each command in detail.
 
+ebics-setup
+-----------
+
+This command creates the client keys, if they aren't found already on the 
disk, and sends them to the bank if they were not sent yet.  In case of 
sending, it ejects the PDF document that contains the keys fingerprints, so 
that the user can send it to the bank to confirm their keys.  The process 
continues by checking if the bank keys exist already on disk, and proceeds with 
downloading them in case they are not.  It checks then if the bank keys were 
accepted by the user; if yes, the setup [...]
+
+Its options are as follows:
+
+**-h** \| **--help**
+   Prints short help on options.
+**-c** \| **--config** \ ‌\ *FILENAME*
+   Specifies the configuration file.
+**--check-full-config**
+  Checks the configuration of all the three subcommands and returns.
+**--force-keys-resubmission**
+  Resubmits the client keys.  If no keys were found, it creates and submits 
them.
+**--auto-accept-keys**
+  Accepts the bank keys without interactively asking the user.
+**--generate-registration-pdf**
+  Generates the PDF with the client keys fingerprints, even when the keys 
aren't going to be submitted in the current run.  That's useful in case the PDF 
went lost after the first submission and the user needs a new PDF.
+
 
 dbinit
 ------

-- 
To stop receiving notification emails like this one, please contact
gnunet@gnunet.org.