[taler-docs] branch master updated: renumber list in section "Bank Transport Setup"

[gnunet]

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

ttn pushed a commit to branch master
in repository docs.

The following commit(s) were added to refs/heads/master by this push:
     new 8b8fa59  renumber list in section "Bank Transport Setup"
8b8fa59 is described below

commit 8b8fa591fce11d1763cd94c90a746cac4550ea8a
Author: Thien-Thi Nguyen <ttn@gnuvola.org>
AuthorDate: Fri Nov 27 19:21:43 2020 -0500

    renumber list in section "Bank Transport Setup"
---
 libeufin/bank-transport-ebics.rst | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/libeufin/bank-transport-ebics.rst 
b/libeufin/bank-transport-ebics.rst
index 844b1f5..5afdd5d 100644
--- a/libeufin/bank-transport-ebics.rst
+++ b/libeufin/bank-transport-ebics.rst
@@ -24,26 +24,26 @@ The following steps are required to set up an EBICS bank 
transport:
 
 3. The LibEuFin nexus generates cryptographic key material (3 RSA key pairs).
 
-5. The nexus sends the public keys electronically to the bank's EBICS server, 
together with the information
+4. The nexus sends the public keys electronically to the bank's EBICS server, 
together with the information
    identifying the subscriber (PartnerID, UserID, SystemID).
 
-6. The user prints a document that contains the public key and hashes for all 
three key pairs.
+5. The user prints a document that contains the public key and hashes for all 
three key pairs.
    The user then signs this document and sends it to the bank 
(physically/scanned).
 
-7. The bank receives the letter and verifies that the keys from the letter 
correspond
+6. The bank receives the letter and verifies that the keys from the letter 
correspond
    to the electronically sent keys.  If they match, the bank sets the state of 
the
    subscriber to "ready".
 
-8. The user now has to wait until the bank has set the EBICS subscriber state 
to "ready".
+7. The user now has to wait until the bank has set the EBICS subscriber state 
to "ready".
    There is no in-band notification for this, but the Nexus can try 
downloading the bank's
    cryptographic parameters.  This will only succeed once the EBICS subscriber 
is set to "ready"
    by the bank.
 
-9. The user should confirm the public keys of the bank received in the 
previous step.
+8. The user should confirm the public keys of the bank received in the 
previous step.
    Typically the bank gives the value of these public keys in an out-of-band 
channel.
 
-10. Now the user can finally use the EBICS bank transport.  The first step 
after finishing
-    the setup should be to import the bank accounts accessible for this EBICS 
subscriber.
+9. Now the user can finally use the EBICS bank transport.  The first step 
after finishing
+   the setup should be to import the bank accounts accessible for this EBICS 
subscriber.
 
 
 Alternative ways of setting up the EBICS bank transport are:

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