summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorThien-Thi Nguyen <ttn@gnuvola.org>2020-12-18 03:57:28 -0500
committerThien-Thi Nguyen <ttn@gnuvola.org>2020-12-18 03:57:28 -0500
commitcdfddd8706929c7203b8eedfd1ede359ca398439 (patch)
tree230f9458632c2d9d76201a39fd61e1cdd4e2e538
parent720dbe0727e50365062632ca8567f75f6c263a92 (diff)
downloaddocs-cdfddd8706929c7203b8eedfd1ede359ca398439.tar.gz
docs-cdfddd8706929c7203b8eedfd1ede359ca398439.tar.bz2
docs-cdfddd8706929c7203b8eedfd1ede359ca398439.zip
format ‘console’ code blocks (12 instances)
-rw-r--r--manpages/taler-exchange-offline.1.rst60
1 files changed, 42 insertions, 18 deletions
diff --git a/manpages/taler-exchange-offline.1.rst b/manpages/taler-exchange-offline.1.rst
index 15599557..5fe52ce8 100644
--- a/manpages/taler-exchange-offline.1.rst
+++ b/manpages/taler-exchange-offline.1.rst
@@ -73,16 +73,20 @@ The exchange validates all operations by checking the signatures against the
master public key that must be provided in the exchange configuration. To
obtain the master public key, use:
-$ MASTER_PRIV_FILE=`taler-config -f -c $CONF -s EXCHANGE -o MASTER_PRIV_FILE`
-$ gnunet-ecc -p $MASTER_PRIV_FILE
+.. code-block:: console
+
+ $ MASTER_PRIV_FILE=`taler-config -f -c $CONF -s EXCHANGE -o MASTER_PRIV_FILE`
+ $ gnunet-ecc -p $MASTER_PRIV_FILE
Note that if the private key file does not yet exist, the above will fail.
In this case, create the private key using:
-$ MASTER_PRIV_FILE=`taler-config -f -c $CONF -s EXCHANGE -o MASTER_PRIV_FILE`
-$ MASTER_PRIV_DIR=`dirname $MASTER_PRIV_FILE`
-$ mkdir -p $MASTER_PRIV_DIR
-$ gnunet-ecc -g1 $MASTER_PRIV_FILE
+.. code-block:: console
+
+ $ MASTER_PRIV_FILE=`taler-config -f -c $CONF -s EXCHANGE -o MASTER_PRIV_FILE`
+ $ MASTER_PRIV_DIR=`dirname $MASTER_PRIV_FILE`
+ $ mkdir -p $MASTER_PRIV_DIR
+ $ gnunet-ecc -g1 $MASTER_PRIV_FILE
Relevant configuration options for **taler-exchange-offline** are:
@@ -282,58 +286,78 @@ Examples
Download future public keys from an exchange (online)
-----------------------------------------------------
-$ taler-exchange-offline download > keys.json
+.. code-block:: console
+
+ $ taler-exchange-offline download > keys.json
Show information about future public keys (offline or online)
-------------------------------------------------------------
-$ taler-exchange-offline show < keys.json
+.. code-block:: console
+
+ $ taler-exchange-offline show < keys.json
Sign future public keys (offline)
---------------------------------
-$ taler-exchange-offline sign < keys.json > sigs.json
+.. code-block:: console
+
+ $ taler-exchange-offline sign < keys.json > sigs.json
Upload signatures about future public keys (online)
---------------------------------------------------
-$ taler-exchange-offline upload < sigs.json
+.. code-block:: console
+
+ $ taler-exchange-offline upload < sigs.json
Download, sign and upload, all in one (online)
----------------------------------------------
Note that doing this is only recommended in non-production deployments.
-$ taler-exchange-offline download sign upload
+.. code-block:: console
+
+ $ taler-exchange-offline download sign upload
Create signature to enable bank account (offline)
-------------------------------------------------
-$ taler-exchange-offline enable-account payto://iban/DE24242 > account.json
+.. code-block:: console
+
+ $ taler-exchange-offline enable-account payto://iban/DE24242 > account.json
Upload bank account signature (online)
--------------------------------------
-$ taler-exchange-offline upload < account.json
+.. code-block:: console
+
+ $ taler-exchange-offline upload < account.json
Combine signing keys and enabling bank account (offline)
--------------------------------------------------------
-$ taler-exchange-offline sign enable-account payto://iban/DE24242 < keys.json > combo.json
+.. code-block:: console
+
+ $ taler-exchange-offline sign enable-account payto://iban/DE24242 < keys.json > combo.json
Upload various signatures (online)
----------------------------------
-$ taler-exchange-offline upload < combo.json
+.. code-block:: console
+
+ $ taler-exchange-offline upload < combo.json
Create multiple revocation messages in one pass (offline)
---------------------------------------------------------
-$ taler-exchange-offline revoke-denomination $DKH1 revoke-denomination $DKH2 > revoke.json
-$ taler-exchange-offline revoke-signkey $SK1 revoke-signkey $SK2 > revoke.json
-$ taler-exchange-offline revoke-signkey $SK revoke-denomkey $DKH > mix.json
+.. code-block:: console
+
+ $ taler-exchange-offline revoke-denomination $DKH1 revoke-denomination $DKH2 > revoke.json
+ $ taler-exchange-offline revoke-signkey $SK1 revoke-signkey $SK2 > revoke.json
+ $ taler-exchange-offline revoke-signkey $SK revoke-denomkey $DKH > mix.json
The outputs ("revoke.json", "mix.json") must be uploaded using the ``upload``
command to the exchange to actually revoke the keys.