summaryrefslogtreecommitdiff
path: root/taler-auditor-manual.rst
diff options
context:
space:
mode:
Diffstat (limited to 'taler-auditor-manual.rst')
-rw-r--r--taler-auditor-manual.rst32
1 files changed, 16 insertions, 16 deletions
diff --git a/taler-auditor-manual.rst b/taler-auditor-manual.rst
index 35f5a79..432e2d1 100644
--- a/taler-auditor-manual.rst
+++ b/taler-auditor-manual.rst
@@ -221,7 +221,7 @@ to export some of the tooling required by Taler.
To download and install libgnunetutil, proceed as follows:
-::
+.. code-block:: console
$ git clone https://git.gnunet.org/gnunet/
$ cd gnunet/
@@ -237,7 +237,7 @@ which requires you to run the last step as ``root``.
To download and install the GNU Taler exchange, proceeds as follows:
-::
+.. code-block:: console
$ git clone git://git.taler.net/exchange
$ cd exchange
@@ -320,7 +320,7 @@ choosing the backend, it is mandatory to supply the connection string
- via configuration option CONFIG, under section [auditordb-BACKEND].
For example, the demo exchange is configured as follows:
-::
+.. code-block:: ini
[auditor]
...
@@ -370,9 +370,9 @@ If this step is skipped, the auditor will malfunction at all future
stages with a foreign key violation, as it doesn't know the exchange's
master public key.
-::
+.. code-block:: console
- taler-auditor-exchange -m $MASTER_PUB -u $EXCHANGE_BASE_URL
+ $ taler-auditor-exchange -m $MASTER_PUB -u $EXCHANGE_BASE_URL
.. _AuditorDenominations:
@@ -392,9 +392,9 @@ receive the blob to sign (Website, manual delivery, ...). Note that the
blob does not contain confidential data, but signing the wrong keys would
be fatal. Given the blob, the auditor would sign it using:
-::
+.. code-block:: console
- taler-auditor-sign -m EXCHANGE_MASTER_PUB -r BLOB -u AUDITOR_URL -o OUTPUT_FILE
+ $ taler-auditor-sign -m EXCHANGE_MASTER_PUB -r BLOB -u AUDITOR_URL -o OUTPUT_FILE
Those arguments are all mandatory.
@@ -467,7 +467,7 @@ Performing an audit is done by invoking the ``taler-auditor`` and
files, which can then be combined using the ``contrib/render.py``
script into the TeX report.
-::
+.. code-block:: console
$ taler-audit
@@ -510,7 +510,7 @@ several categories of failures of different severity:
the correct amount to a merchant).
- Configuration issues (such was wire fees unavailable)
-
+
.. _AuditorDatabaseUpgrades:
@@ -520,9 +520,9 @@ Database upgrades
To upgrade the database between Taler versions can be done by
running:
-::
+.. code-block:: console
- $ taler-auditor-dbinit
+ $ taler-auditor-dbinit
However, the above is the general rule. Please review the
specific release notes to ensure this is correct for the
@@ -531,7 +531,7 @@ specific upgrade.
The auditor database can be re-initialized using:
-::
+.. code-block:: console
$ taler-auditor-dbinit -r
@@ -654,7 +654,7 @@ CodeBlau reports the following checks:
coin value without fee, total deposit without refunds
- wire out fee is negative
-
+
- coin arithmetic inconsistencies
- refund (merchant) is negative
@@ -672,13 +672,13 @@ CodeBlau reports the following checks:
- wire out inconsistencies in amount
- row inconsistencies
-
+
- wire account given is malformed
- h(wire) does not match wire
- failed to compute hash of given wire data
-
+
- database contains wrong hash code for wire details
- no transaction history for coin claimed in aggregation
@@ -715,7 +715,7 @@ CodeBlau reports the following checks:
- arithmetic inconsistencies
- melt contribution vs. fee
-
+
- melt (cost)
- refund fee