From f224155aa1c583aca9c05d466f739c86edbf5138 Mon Sep 17 00:00:00 2001 From: Christian Grothoff Date: Tue, 14 Jan 2020 11:05:18 +0100 Subject: remove wire plugin documentation, as it is obsolete now --- taler-auditor-manual.rst | 40 ++++++++++++++++++++++++---------------- 1 file changed, 24 insertions(+), 16 deletions(-) (limited to 'taler-auditor-manual.rst') diff --git a/taler-auditor-manual.rst b/taler-auditor-manual.rst index 3205256e..b2770457 100644 --- a/taler-auditor-manual.rst +++ b/taler-auditor-manual.rst @@ -1,3 +1,22 @@ +.. + This file is part of GNU TALER. + + Copyright (C) 2019-2020 Taler Systems SA + + TALER is free software; you can redistribute it and/or modify it under the + terms of the GNU General Public License as published by the Free Software + Foundation; either version 2.1, or (at your option) any later version. + + TALER is distributed in the hope that it will be useful, but WITHOUT ANY + WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR + A PARTICULAR PURPOSE. See the GNU General Public License for more details. + + You should have received a copy of the GNU General Public License along with + TALER; see the file COPYING. If not, see + + @author Christian Grothoff + + GNU Taler Auditor Operator Manual ################################# @@ -95,15 +114,6 @@ third parties to verify one's own work. The Taler software stack for an auditor consists of the following components: -- Wire plugin - A wire plugin enables the auditor to talk to the bank. Its role - is to allow the auditor to retrieve incoming and outgoing wire - transfers made by the exchange. Wire plugins are - *plugins* as there can be many different implementations to deal with - different banking standards. Wire plugins are automatically located - and used by the auditor, but must be configured with the appropriate - credentials. - - DBMS Postgres The auditor requires a DBMS to stores a local copy of the transaction history for @@ -127,9 +137,9 @@ components: of the specification by the exchange. However, for now it is assumed that the respective cryptographic proofs are reported and verified manually --- as with a well-behaved exchange this should obviously be a rare event. - + The main binary of this component is the ``taler-auditor-httpd``. - + - The wire-auditor The wire auditor verifies that the bank transactions performed by the exchange were done properly. This component must have access to the bank account @@ -185,7 +195,7 @@ exchange compilation. - texlive-latex-extra - python3-jinja2 - + - libgnunetutil (from Git) - GNU Taler exchange (from Git) @@ -319,7 +329,7 @@ The ``taler-auditor-dbinit`` tool is used to initialize the auditor's tables. After running this tool, the rights to CREATE or DROP tables are no longer required and should be removed. - + .. _Deployment: Deployment @@ -381,7 +391,7 @@ be fatal. Given the blob, the auditor would sign it using: Those arguments are all mandatory. - ``EXCHANGE_MASTER_PUB`` the base32 Crockford-encoded exchange’s - master public key. + master public key. - ``BLOB`` the blob generated by the ``taler-exchange-keyup`` tool. @@ -584,5 +594,3 @@ already seen. More extensive auditor testing where additional transactions have been made against the database when the audit is being resumed should be done in the future. - - -- cgit v1.2.3