diff options
49 files changed, 148 insertions, 155 deletions
diff --git a/man/challenger-admin.1 b/man/challenger-admin.1 index 7ed93293..f65395d9 100644 --- a/man/challenger-admin.1 +++ b/man/challenger-admin.1 @@ -27,7 +27,7 @@ level margin: \\n[rst2man-indent\\n[rst2man-indent-level]] .\" new: \\n[rst2man-indent\\n[rst2man-indent-level]] .in \\n[rst2man-indent\\n[rst2man-indent-level]]u .. -.TH "CHALLENGER-ADMIN" "1" "Jul 11, 2023" "0.9" "GNU Taler" +.TH "CHALLENGER-ADMIN" "1" "Jul 15, 2023" "0.9" "GNU Taler" .SH NAME challenger-admin \- manipulate list of authorized Challenger clients .SH SYNOPSIS diff --git a/man/challenger-config.1 b/man/challenger-config.1 index 8b11b6f9..80ff3e8b 100644 --- a/man/challenger-config.1 +++ b/man/challenger-config.1 @@ -27,7 +27,7 @@ level margin: \\n[rst2man-indent\\n[rst2man-indent-level]] .\" new: \\n[rst2man-indent\\n[rst2man-indent-level]] .in \\n[rst2man-indent\\n[rst2man-indent-level]]u .. -.TH "CHALLENGER-CONFIG" "1" "Jul 11, 2023" "0.9" "GNU Taler" +.TH "CHALLENGER-CONFIG" "1" "Jul 15, 2023" "0.9" "GNU Taler" .SH NAME challenger-config \- manipulate Challenger configuration files .SH SYNOPSIS @@ -53,8 +53,8 @@ challenger-config \- manipulate Challenger configuration files .TP \fB\-b\fP \fIBACKEND\fP | \fB\-\-supported\-backend=\fP\fIBACKEND\fP Tests whether the specified \fIBACKEND\fP is supported by the current installation. -The backend must match the name of a plugin, i.e. "namestore_postgres" for -the PostgreSQL database backend of the "NAMESTORE" service. If \fIBACKEND\fP is +The backend must match the name of a plugin, i.e. \(dqnamestore_postgres\(dq for +the PostgreSQL database backend of the \(dqNAMESTORE\(dq service. If \fIBACKEND\fP is supported, challenger\-config will return a status code of 0 (success), otherwise 77 (unsupported). When this option is specified, no other options may be specified. Specifying this option together with other options will cause @@ -83,7 +83,7 @@ Send logging output to \fIFILENAME\fP\&. \fB\-o\fP \fIOPTION\fP | \fB\-\-option=\fP\fIOPTION\fP Which configuration option should be accessed or edited. Required to set a value. If not given, all values of a given section will be printed in the -format "OPTION = VALUE". +format \(dqOPTION = VALUE\(dq. .TP \fB\-r\fP | \fB\-\-rewrite\fP Write the configuration file even if nothing changed. Will remove all comments! diff --git a/man/challenger-dbinit.1 b/man/challenger-dbinit.1 index 94b34981..f9e80275 100644 --- a/man/challenger-dbinit.1 +++ b/man/challenger-dbinit.1 @@ -27,7 +27,7 @@ level margin: \\n[rst2man-indent\\n[rst2man-indent-level]] .\" new: \\n[rst2man-indent\\n[rst2man-indent-level]] .in \\n[rst2man-indent\\n[rst2man-indent-level]]u .. -.TH "CHALLENGER-DBINIT" "1" "Jul 11, 2023" "0.9" "GNU Taler" +.TH "CHALLENGER-DBINIT" "1" "Jul 15, 2023" "0.9" "GNU Taler" .SH NAME challenger-dbinit \- initialize the Challenger database .SH SYNOPSIS diff --git a/man/challenger-httpd.1 b/man/challenger-httpd.1 index 778373e3..ac99bb39 100644 --- a/man/challenger-httpd.1 +++ b/man/challenger-httpd.1 @@ -27,7 +27,7 @@ level margin: \\n[rst2man-indent\\n[rst2man-indent-level]] .\" new: \\n[rst2man-indent\\n[rst2man-indent-level]] .in \\n[rst2man-indent\\n[rst2man-indent-level]]u .. -.TH "CHALLENGER-HTTPD" "1" "Jul 11, 2023" "0.9" "GNU Taler" +.TH "CHALLENGER-HTTPD" "1" "Jul 15, 2023" "0.9" "GNU Taler" .SH NAME challenger-httpd \- provide the Challenger HTTP interface .SH SYNOPSIS diff --git a/man/challenger.conf.5 b/man/challenger.conf.5 index ae15459e..eef98855 100644 --- a/man/challenger.conf.5 +++ b/man/challenger.conf.5 @@ -27,7 +27,7 @@ level margin: \\n[rst2man-indent\\n[rst2man-indent-level]] .\" new: \\n[rst2man-indent\\n[rst2man-indent-level]] .in \\n[rst2man-indent\\n[rst2man-indent-level]]u .. -.TH "CHALLENGER.CONF" "5" "Jul 11, 2023" "0.9" "GNU Taler" +.TH "CHALLENGER.CONF" "5" "Jul 15, 2023" "0.9" "GNU Taler" .SH NAME challenger.conf \- Challenger configuration file .SH DESCRIPTION @@ -46,7 +46,7 @@ Section names and options are \fIcase\-insensitive\fP\&. The values, however, are \fIcase\-sensitive\fP\&. In particular, boolean values are one of \fBYES\fP or \fBNO\fP\&. Values can include whitespace by surrounding -the entire value with \fB"\fP (double quote). +the entire value with \fB\(dq\fP (double quote). Note, however, that there are no escape characters in such strings; all characters between the double quotes (including other double quotes) are taken verbatim. diff --git a/man/libeufin-nexus.1 b/man/libeufin-nexus.1 index 54ceb673..ae530ed3 100644 --- a/man/libeufin-nexus.1 +++ b/man/libeufin-nexus.1 @@ -27,7 +27,7 @@ level margin: \\n[rst2man-indent\\n[rst2man-indent-level]] .\" new: \\n[rst2man-indent\\n[rst2man-indent-level]] .in \\n[rst2man-indent\\n[rst2man-indent-level]]u .. -.TH "LIBEUFIN-NEXUS" "1" "Jul 11, 2023" "0.9" "GNU Taler" +.TH "LIBEUFIN-NEXUS" "1" "Jul 15, 2023" "0.9" "GNU Taler" .SH NAME libeufin-nexus \- service to interface to various bank access APIs .SH SYNOPSIS @@ -112,9 +112,9 @@ For example: .ft C $ libeufin\-nexus parse\-camt camt53\-gls\-style\-0.xml { - "transactions" : [ { - "amount" : "EUR:2.35", - "creditDebitIndicator" : "DBIT", + \(dqtransactions\(dq : [ { + \(dqamount\(dq : \(dqEUR:2.35\(dq, + \(dqcreditDebitIndicator\(dq : \(dqDBIT\(dq, ... } ] } diff --git a/man/libeufin-sandbox.1 b/man/libeufin-sandbox.1 index 333ed9e4..1dcd6102 100644 --- a/man/libeufin-sandbox.1 +++ b/man/libeufin-sandbox.1 @@ -27,7 +27,7 @@ level margin: \\n[rst2man-indent\\n[rst2man-indent-level]] .\" new: \\n[rst2man-indent\\n[rst2man-indent-level]] .in \\n[rst2man-indent\\n[rst2man-indent-level]]u .. -.TH "LIBEUFIN-SANDBOX" "1" "Jul 11, 2023" "0.9" "GNU Taler" +.TH "LIBEUFIN-SANDBOX" "1" "Jul 15, 2023" "0.9" "GNU Taler" .SH NAME libeufin-sandbox \- simulate core banking system with EBICS access to bank accounts .SH SYNOPSIS @@ -49,7 +49,7 @@ requests either over the network or via a Unix domain socket. Related program \fBlibeufin\-cli\fP is the preferred front end for that mode of operation. There is also a mode where \fBlibeufin\-sandbox\fP accepts commands directly, -useful for configuring one or more "demobank" (simulated bank) instances. +useful for configuring one or more \(dqdemobank\(dq (simulated bank) instances. .sp Its options are as follows: .INDENT 0.0 @@ -88,10 +88,10 @@ Option \fB\-\-captcha\-url $URL\fP specifies where the wallet user is going to be redirected to confirm the withdrawal operation. This $URL should point to the bank frontend. More precisely to the UI that let the user finish a withdrawal operation that needs to be confirmed. Example of -this value may be "\fI\%https://bank.domain/#/operation\fP/{wopid}" where -"\fI\%https://bank.domain\fP" returns the demobank SPA and the demobank view under -the route "/operation/{wopid}" will show the status of the operation id {wopid}. -Note that "{wopid}" is literally in the \-\-captcha\-url config and replaced at +this value may be \(dq\fI\%https://bank.domain/#/operation\fP/{wopid}\(dq where +\(dq\fI\%https://bank.domain\fP\(dq returns the demobank SPA and the demobank view under +the route \(dq/operation/{wopid}\(dq will show the status of the operation id {wopid}. +Note that \(dq{wopid}\(dq is literally in the \-\-captcha\-url config and replaced at runtime by the sandbox server. Option \fB\-\-bank\-debt\-limit N\fP (default: 1000000) specifies that the bank debt limit should be N (units of currency). @@ -141,7 +141,7 @@ This sets the default exchange for demobank \fBbank01\fP\&. It is an error if the demobank does not exist. .SS make\-transaction .sp -This is a "legacy" command, useful in a previous iteration of LibEuFin +This is a \(dqlegacy\(dq command, useful in a previous iteration of LibEuFin and for internal testing. It creates and records a wire transfer transaction in the database. .sp diff --git a/man/sync-config.1 b/man/sync-config.1 index 44c1ac5d..2fdc3ba1 100644 --- a/man/sync-config.1 +++ b/man/sync-config.1 @@ -27,7 +27,7 @@ level margin: \\n[rst2man-indent\\n[rst2man-indent-level]] .\" new: \\n[rst2man-indent\\n[rst2man-indent-level]] .in \\n[rst2man-indent\\n[rst2man-indent-level]]u .. -.TH "SYNC-CONFIG" "1" "Jul 11, 2023" "0.9" "GNU Taler" +.TH "SYNC-CONFIG" "1" "Jul 15, 2023" "0.9" "GNU Taler" .SH NAME sync-config \- manipulate Sync configuration files .SH SYNOPSIS @@ -53,8 +53,8 @@ sync-config \- manipulate Sync configuration files .TP \fB\-b\fP \fIBACKEND\fP | \fB\-\-supported\-backend=\fP\fIBACKEND\fP Tests whether the specified \fIBACKEND\fP is supported by the current installation. -The backend must match the name of a plugin, i.e. "namestore_postgres" for -the PostgreSQL database backend of the "NAMESTORE" service. If \fIBACKEND\fP is +The backend must match the name of a plugin, i.e. \(dqnamestore_postgres\(dq for +the PostgreSQL database backend of the \(dqNAMESTORE\(dq service. If \fIBACKEND\fP is supported, sync\-config will return a status code of 0 (success), otherwise 77 (unsupported). When this option is specified, no other options may be specified. Specifying this option together with other options will cause @@ -83,7 +83,7 @@ Send logging output to \fIFILENAME\fP\&. \fB\-o\fP \fIOPTION\fP | \fB\-\-option=\fP\fIOPTION\fP Which configuration option should be accessed or edited. Required to set a value. If not given, all values of a given section will be printed in the -format "OPTION = VALUE". +format \(dqOPTION = VALUE\(dq. .TP \fB\-r\fP | \fB\-\-rewrite\fP Write the configuration file even if nothing changed. Will remove all comments! diff --git a/man/sync-dbinit.1 b/man/sync-dbinit.1 index 1f577685..b827e46e 100644 --- a/man/sync-dbinit.1 +++ b/man/sync-dbinit.1 @@ -27,7 +27,7 @@ level margin: \\n[rst2man-indent\\n[rst2man-indent-level]] .\" new: \\n[rst2man-indent\\n[rst2man-indent-level]] .in \\n[rst2man-indent\\n[rst2man-indent-level]]u .. -.TH "SYNC-DBINIT" "1" "Jul 11, 2023" "0.9" "GNU Taler" +.TH "SYNC-DBINIT" "1" "Jul 15, 2023" "0.9" "GNU Taler" .SH NAME sync-dbinit \- initialize the Sync database .SH SYNOPSIS diff --git a/man/sync-httpd.1 b/man/sync-httpd.1 index d90ad6c9..915d5fb5 100644 --- a/man/sync-httpd.1 +++ b/man/sync-httpd.1 @@ -27,7 +27,7 @@ level margin: \\n[rst2man-indent\\n[rst2man-indent-level]] .\" new: \\n[rst2man-indent\\n[rst2man-indent-level]] .in \\n[rst2man-indent\\n[rst2man-indent-level]]u .. -.TH "SYNC-HTTPD" "1" "Jul 11, 2023" "0.9" "GNU Taler" +.TH "SYNC-HTTPD" "1" "Jul 15, 2023" "0.9" "GNU Taler" .SH NAME sync-httpd \- provide the Sync HTTP interface .SH SYNOPSIS diff --git a/man/sync.conf.5 b/man/sync.conf.5 index 0444f6b6..779de287 100644 --- a/man/sync.conf.5 +++ b/man/sync.conf.5 @@ -27,7 +27,7 @@ level margin: \\n[rst2man-indent\\n[rst2man-indent-level]] .\" new: \\n[rst2man-indent\\n[rst2man-indent-level]] .in \\n[rst2man-indent\\n[rst2man-indent-level]]u .. -.TH "SYNC.CONF" "5" "Jul 11, 2023" "0.9" "GNU Taler" +.TH "SYNC.CONF" "5" "Jul 15, 2023" "0.9" "GNU Taler" .SH NAME sync.conf \- Sync configuration file .SH DESCRIPTION @@ -46,7 +46,7 @@ Section names and options are \fIcase\-insensitive\fP\&. The values, however, are \fIcase\-sensitive\fP\&. In particular, boolean values are one of \fBYES\fP or \fBNO\fP\&. Values can include whitespace by surrounding -the entire value with \fB"\fP (double quote). +the entire value with \fB\(dq\fP (double quote). Note, however, that there are no escape characters in such strings; all characters between the double quotes (including other double quotes) are taken verbatim. diff --git a/man/taler-auditor-dbinit.1 b/man/taler-auditor-dbinit.1 index 0e64d31c..4727d2ce 100644 --- a/man/taler-auditor-dbinit.1 +++ b/man/taler-auditor-dbinit.1 @@ -27,7 +27,7 @@ level margin: \\n[rst2man-indent\\n[rst2man-indent-level]] .\" new: \\n[rst2man-indent\\n[rst2man-indent-level]] .in \\n[rst2man-indent\\n[rst2man-indent-level]]u .. -.TH "TALER-AUDITOR-DBINIT" "1" "Jul 11, 2023" "0.9" "GNU Taler" +.TH "TALER-AUDITOR-DBINIT" "1" "Jul 15, 2023" "0.9" "GNU Taler" .SH NAME taler-auditor-dbinit \- setup auditor database .SH SYNOPSIS diff --git a/man/taler-auditor-exchange.1 b/man/taler-auditor-exchange.1 index 9c6b513e..8d8a63d3 100644 --- a/man/taler-auditor-exchange.1 +++ b/man/taler-auditor-exchange.1 @@ -27,7 +27,7 @@ level margin: \\n[rst2man-indent\\n[rst2man-indent-level]] .\" new: \\n[rst2man-indent\\n[rst2man-indent-level]] .in \\n[rst2man-indent\\n[rst2man-indent-level]]u .. -.TH "TALER-AUDITOR-EXCHANGE" "1" "Jul 11, 2023" "0.9" "GNU Taler" +.TH "TALER-AUDITOR-EXCHANGE" "1" "Jul 15, 2023" "0.9" "GNU Taler" .SH NAME taler-auditor-exchange \- add or remove exchange from auditor’s list .SH SYNOPSIS diff --git a/man/taler-auditor-httpd.1 b/man/taler-auditor-httpd.1 index 41a5f2f4..95b47c84 100644 --- a/man/taler-auditor-httpd.1 +++ b/man/taler-auditor-httpd.1 @@ -27,7 +27,7 @@ level margin: \\n[rst2man-indent\\n[rst2man-indent-level]] .\" new: \\n[rst2man-indent\\n[rst2man-indent-level]] .in \\n[rst2man-indent\\n[rst2man-indent-level]]u .. -.TH "TALER-AUDITOR-HTTPD" "1" "Jul 11, 2023" "0.9" "GNU Taler" +.TH "TALER-AUDITOR-HTTPD" "1" "Jul 15, 2023" "0.9" "GNU Taler" .SH NAME taler-auditor-httpd \- HTTP server providing a RESTful API to access a Taler auditor .SH SYNOPSIS diff --git a/man/taler-auditor-offline.1 b/man/taler-auditor-offline.1 index 34fc960c..ea80b063 100644 --- a/man/taler-auditor-offline.1 +++ b/man/taler-auditor-offline.1 @@ -27,7 +27,7 @@ level margin: \\n[rst2man-indent\\n[rst2man-indent-level]] .\" new: \\n[rst2man-indent\\n[rst2man-indent-level]] .in \\n[rst2man-indent\\n[rst2man-indent-level]]u .. -.TH "TALER-AUDITOR-OFFLINE" "1" "Jul 11, 2023" "0.9" "GNU Taler" +.TH "TALER-AUDITOR-OFFLINE" "1" "Jul 15, 2023" "0.9" "GNU Taler" .SH NAME taler-auditor-offline \- Taler auditor certifies that it audits a Taler exchange .SH SYNOPSIS @@ -55,10 +55,10 @@ The resulting data serves as input to the \fBsign\fP and \fBshow\fP subcommands. .sp The \fBupload\fP subcommand uploads the signatures created with the private key to the exchange. It handles the output of all subcommands (except \fBdownload\fP). -The \fBdownload\fP and \fBupload\fP subcommands must naturally be run "online" and do not +The \fBdownload\fP and \fBupload\fP subcommands must naturally be run \(dqonline\(dq and do not require access to the auditor\(aqs private key, which should be kept offline. .sp -All other subcommands are intended to be run "offline". However, especially +All other subcommands are intended to be run \(dqoffline\(dq. However, especially when testing, it is of course possible to run the subcommands online as well. Generally, subcommands read inputs (beyond command\-line arguments) from \fBstdin\fP\&. However, they may also consume outputs of previous @@ -102,7 +102,7 @@ $ taler\-auditor\-offline setup .UNINDENT .sp Note that if the private key file already exists, the above will simply output -the existing key. Passing additional arguments after setup (including "\-") +the existing key. Passing additional arguments after setup (including \(dq\-\(dq) will cause the output to be encapsulated in JSON. .sp Relevant configuration options for \fBtaler\-auditor\-offline\fP are: diff --git a/man/taler-auditor-sync.1 b/man/taler-auditor-sync.1 index 82bae7f5..b3b73e7a 100644 --- a/man/taler-auditor-sync.1 +++ b/man/taler-auditor-sync.1 @@ -27,7 +27,7 @@ level margin: \\n[rst2man-indent\\n[rst2man-indent-level]] .\" new: \\n[rst2man-indent\\n[rst2man-indent-level]] .in \\n[rst2man-indent\\n[rst2man-indent-level]]u .. -.TH "TALER-AUDITOR-SYNC" "1" "Jul 11, 2023" "0.9" "GNU Taler" +.TH "TALER-AUDITOR-SYNC" "1" "Jul 15, 2023" "0.9" "GNU Taler" .SH NAME taler-auditor-sync \- tool to safely synchronize auditor database .SH SYNOPSIS diff --git a/man/taler-auditor.1 b/man/taler-auditor.1 index 3b525963..e0d0f920 100644 --- a/man/taler-auditor.1 +++ b/man/taler-auditor.1 @@ -27,7 +27,7 @@ level margin: \\n[rst2man-indent\\n[rst2man-indent-level]] .\" new: \\n[rst2man-indent\\n[rst2man-indent-level]] .in \\n[rst2man-indent\\n[rst2man-indent-level]]u .. -.TH "TALER-AUDITOR" "1" "Jul 11, 2023" "0.9" "GNU Taler" +.TH "TALER-AUDITOR" "1" "Jul 15, 2023" "0.9" "GNU Taler" .SH NAME taler-auditor \- audit exchange .SH SYNOPSIS @@ -64,7 +64,7 @@ Print short help on options. .TP \fB\-i\fP | \fB\-\-internal\fP Run additional checks that can only performed on the exchange\-internal -database and not the "safe" replicated database at the auditor. +database and not the \(dqsafe\(dq replicated database at the auditor. .TP \fB\-I\fP | \fB\-\-ignore\-not\-found\fP Do not fail if the bank says that the exchange bank account does not (yet) exist. diff --git a/man/taler-config.1 b/man/taler-config.1 index ea85028a..05fa9db8 100644 --- a/man/taler-config.1 +++ b/man/taler-config.1 @@ -27,7 +27,7 @@ level margin: \\n[rst2man-indent\\n[rst2man-indent-level]] .\" new: \\n[rst2man-indent\\n[rst2man-indent-level]] .in \\n[rst2man-indent\\n[rst2man-indent-level]]u .. -.TH "TALER-CONFIG" "1" "Jul 11, 2023" "0.9" "GNU Taler" +.TH "TALER-CONFIG" "1" "Jul 15, 2023" "0.9" "GNU Taler" .SH NAME taler-config \- Taler configuration inspection and editing .SH SYNOPSIS @@ -53,8 +53,8 @@ taler-config \- Taler configuration inspection and editing .TP \fB\-b\fP \fIBACKEND\fP | \fB\-\-supported\-backend=\fP\fIBACKEND\fP Tests whether the specified \fIBACKEND\fP is supported by the current installation. -The backend must match the name of a plugin, i.e. "namestore_postgres" for -the PostgreSQL database backend of the "NAMESTORE" service. If \fIBACKEND\fP is +The backend must match the name of a plugin, i.e. \(dqnamestore_postgres\(dq for +the PostgreSQL database backend of the \(dqNAMESTORE\(dq service. If \fIBACKEND\fP is supported, taler\-config will return a status code of 0 (success), otherwise 77 (unsupported). When this option is specified, no other options may be specified. Specifying this option together with other options will cause @@ -83,7 +83,7 @@ Send logging output to \fIFILENAME\fP\&. \fB\-o\fP \fIOPTION\fP | \fB\-\-option=\fP\fIOPTION\fP Which configuration option should be accessed or edited. Required to set a value. If not given, all values of a given section will be printed in the -format "OPTION = VALUE". +format \(dqOPTION = VALUE\(dq. .TP \fB\-r\fP | \fB\-\-rewrite\fP Write the configuration file even if nothing changed. Will remove all comments! diff --git a/man/taler-exchange-aggregator.1 b/man/taler-exchange-aggregator.1 index 2056148e..c4df747d 100644 --- a/man/taler-exchange-aggregator.1 +++ b/man/taler-exchange-aggregator.1 @@ -27,7 +27,7 @@ level margin: \\n[rst2man-indent\\n[rst2man-indent-level]] .\" new: \\n[rst2man-indent\\n[rst2man-indent-level]] .in \\n[rst2man-indent\\n[rst2man-indent-level]]u .. -.TH "TALER-EXCHANGE-AGGREGATOR" "1" "Jul 11, 2023" "0.9" "GNU Taler" +.TH "TALER-EXCHANGE-AGGREGATOR" "1" "Jul 15, 2023" "0.9" "GNU Taler" .SH NAME taler-exchange-aggregator \- aggregate deposits into wire transfers .SH SYNOPSIS @@ -49,7 +49,7 @@ done by \fBtaler\-exchange\-transfer\fP\&. .sp The AGGREGATOR_SHARD_SIZE option can be used to allow multiple aggregator processes to run in parallel and share the load. This is only recommended if a single aggregator is insufficient for the workload. .sp -The aggregator uses a special table to lock shards it is working on. If an aggregator process dies (say due to a power failure), these shard locks may prevent the aggregator from resuming normally. In this case, you must run "taler\-exchange\-dbinit \-s" to release the shard locks before restarting the aggregator. +The aggregator uses a special table to lock shards it is working on. If an aggregator process dies (say due to a power failure), these shard locks may prevent the aggregator from resuming normally. In this case, you must run \(dqtaler\-exchange\-dbinit \-s\(dq to release the shard locks before restarting the aggregator. .INDENT 0.0 .TP \fB\-c\fP \fIFILENAME\fP | \fB\-\-config=\fP\fIFILENAME\fP diff --git a/man/taler-exchange-benchmark.1 b/man/taler-exchange-benchmark.1 index 05f57ee5..7bbc954f 100644 --- a/man/taler-exchange-benchmark.1 +++ b/man/taler-exchange-benchmark.1 @@ -27,7 +27,7 @@ level margin: \\n[rst2man-indent\\n[rst2man-indent-level]] .\" new: \\n[rst2man-indent\\n[rst2man-indent-level]] .in \\n[rst2man-indent\\n[rst2man-indent-level]]u .. -.TH "TALER-EXCHANGE-BENCHMARK" "1" "Jul 11, 2023" "0.9" "GNU Taler" +.TH "TALER-EXCHANGE-BENCHMARK" "1" "Jul 15, 2023" "0.9" "GNU Taler" .SH NAME taler-exchange-benchmark \- measure exchange performance .SH SYNOPSIS @@ -40,7 +40,6 @@ taler-exchange-benchmark \- measure exchange performance [\fB\-K\fP\ |\ \fB\-\-linger\fP] [\fB\-L\fP\ \fILOGLEVEL\fP\ |\ \fB\-\-log\-level=\fP\fILOGLEVEL\fP] [\fB\-l\fP\ \fIFILENAME\fP\ |\ \fB\-\-logfile=\fP\fIFILENAME\fP] -[\fB\-m\fP\ \fIMODE\fP\ |\ \fB\-\-mode=\fP\fIMODE\fP] [\fB\-n\fP\ \fIHOWMANY_COINS\fP\ |\ \fB\-\-coins\-number=\fP\fIHOWMANY_COINS\fP] [\fB\-p\fP\ \fINPROCS\fP\ |\ \fB\-\-parallelism=\fP\fINPROCS\fP] [\fB\-R\fP\ \fIRATE\fP\ |\ \fB\-\-refresh\-rate=\fP\fIRATE\fP] @@ -49,11 +48,8 @@ taler-exchange-benchmark \- measure exchange performance .SH DESCRIPTION .sp \fBtaler\-exchange\-benchmark\fP is a command\-line tool to measure the time -spent to serve withdrawals/deposits/refreshes. It usually needs a -dedicate configuration file where all the services \- the exchange and -the (fake)bank \- listen to URLs not subject to any reverse proxy, as say -Nginx. Moreover, the benchmark runs on a “volatile” database, that means -that table are always erased during a single benchmark run. +spent to serve withdrawals/deposits/refreshes. Before running the benchmark, +the GNU Taler services must already be running at the configured addresses. .INDENT 0.0 .TP \fB\-c\fP \fICONFIG_FILENAME\fP | \fB\-\-config=\fP\fICONFIG_FILENAME\fP @@ -63,11 +59,7 @@ that table are always erased during a single benchmark run. Create all reserves first, before starting normal operations. .TP \fB\-f\fP | \fB\-\-fakebank\fP -Launch a fakebank instead of the Python bank. Only meaningful if the -mode is to launch more than just a client. Note that using the -fakebank will cause the benchmark application to reset all databases -as the fakebank is stateless and thus previous database state would -inherently cause trouble. +Expect to interact with a fakebank instead of libeufin. .TP \fB\-h\fP | \fB\-\-help\fP Prints a compiled\-in help text. @@ -82,9 +74,6 @@ Specifies the log level to use. Accepted values are: \fBDEBUG\fP, \fBINFO\fP, \fB\-l\fP \fIFILENAME\fP | \fB\-\-logfile=\fP\fIFILENAME\fP Send logging output to \fIFILENAME\fP\&. .TP -\fB\-m\fP \fIMODE\fP | \fB\-\-mode=\fP\fIMODE\fP -Mode of operation. Accepted values are: \fBexchange\fP, \fBclients\fP, \fBboth\fP\&. -.TP \fB\-n\fP \fIHOWMANY_COINS\fP | \fB\-\-coins\-number=\fP\fIHOWMANY_COINS\fP Defaults to 1. Specifies how many coins this benchmark should withdraw and spend. After being spent, each coin will be refreshed @@ -99,13 +88,17 @@ Defaults to 10. Probability of refresh per coin (0\-100). \fB\-r\fP \fIN\fP | \fB\-\-reserves=\fP\fIN\fP Create \fIN\fP reserves per client. .TP +\fB\-u\fP \fISECTION\fP | \fB\-\-exchange\-account\-section=\fP\fISECTION\fP +Which configuration section should be used for the bank account +of the exchange. +.TP \fB\-v\fP | \fB\-\-version\fP Print version information. .UNINDENT .SH SEE ALSO .sp taler\-exchange\-dbinit(1), taler\-exchange\-offline(1), taler\-merchant\-benchmark(1), -taler\-exchange\-httpd(1), taler.conf(5) +taler\-exchange\-httpd(1), taler\-unified\-setup(1), taler.conf(5) .SH BUGS .sp Report bugs by using \fI\%https://bugs.taler.net/\fP or by sending electronic diff --git a/man/taler-exchange-closer.1 b/man/taler-exchange-closer.1 index ed580a80..cb69bb59 100644 --- a/man/taler-exchange-closer.1 +++ b/man/taler-exchange-closer.1 @@ -27,7 +27,7 @@ level margin: \\n[rst2man-indent\\n[rst2man-indent-level]] .\" new: \\n[rst2man-indent\\n[rst2man-indent-level]] .in \\n[rst2man-indent\\n[rst2man-indent-level]]u .. -.TH "TALER-EXCHANGE-CLOSER" "1" "Jul 11, 2023" "0.9" "GNU Taler" +.TH "TALER-EXCHANGE-CLOSER" "1" "Jul 15, 2023" "0.9" "GNU Taler" .SH NAME taler-exchange-closer \- close idle reserves .SH SYNOPSIS diff --git a/man/taler-exchange-dbinit.1 b/man/taler-exchange-dbinit.1 index 29789050..bc13c4be 100644 --- a/man/taler-exchange-dbinit.1 +++ b/man/taler-exchange-dbinit.1 @@ -27,7 +27,7 @@ level margin: \\n[rst2man-indent\\n[rst2man-indent-level]] .\" new: \\n[rst2man-indent\\n[rst2man-indent-level]] .in \\n[rst2man-indent\\n[rst2man-indent-level]]u .. -.TH "TALER-EXCHANGE-DBINIT" "1" "Jul 11, 2023" "0.9" "GNU Taler" +.TH "TALER-EXCHANGE-DBINIT" "1" "Jul 15, 2023" "0.9" "GNU Taler" .SH NAME taler-exchange-dbinit \- initialize Taler exchange database .SH SYNOPSIS diff --git a/man/taler-exchange-drain.1 b/man/taler-exchange-drain.1 index cd9d6b8d..8cf8c777 100644 --- a/man/taler-exchange-drain.1 +++ b/man/taler-exchange-drain.1 @@ -27,7 +27,7 @@ level margin: \\n[rst2man-indent\\n[rst2man-indent-level]] .\" new: \\n[rst2man-indent\\n[rst2man-indent-level]] .in \\n[rst2man-indent\\n[rst2man-indent-level]]u .. -.TH "TALER-EXCHANGE-DRAIN" "1" "Jul 11, 2023" "0.9" "GNU Taler" +.TH "TALER-EXCHANGE-DRAIN" "1" "Jul 15, 2023" "0.9" "GNU Taler" .SH NAME taler-exchange-drain \- drain profits from exchange .SH SYNOPSIS diff --git a/man/taler-exchange-expire.1 b/man/taler-exchange-expire.1 index 473246ab..9d312902 100644 --- a/man/taler-exchange-expire.1 +++ b/man/taler-exchange-expire.1 @@ -27,7 +27,7 @@ level margin: \\n[rst2man-indent\\n[rst2man-indent-level]] .\" new: \\n[rst2man-indent\\n[rst2man-indent-level]] .in \\n[rst2man-indent\\n[rst2man-indent-level]]u .. -.TH "TALER-EXCHANGE-EXPIRE" "1" "Jul 11, 2023" "0.9" "GNU Taler" +.TH "TALER-EXCHANGE-EXPIRE" "1" "Jul 15, 2023" "0.9" "GNU Taler" .SH NAME taler-exchange-expire \- refund expired purses .SH SYNOPSIS diff --git a/man/taler-exchange-httpd.1 b/man/taler-exchange-httpd.1 index c4c1209a..67026837 100644 --- a/man/taler-exchange-httpd.1 +++ b/man/taler-exchange-httpd.1 @@ -27,7 +27,7 @@ level margin: \\n[rst2man-indent\\n[rst2man-indent-level]] .\" new: \\n[rst2man-indent\\n[rst2man-indent-level]] .in \\n[rst2man-indent\\n[rst2man-indent-level]]u .. -.TH "TALER-EXCHANGE-HTTPD" "1" "Jul 11, 2023" "0.9" "GNU Taler" +.TH "TALER-EXCHANGE-HTTPD" "1" "Jul 15, 2023" "0.9" "GNU Taler" .SH NAME taler-exchange-httpd \- run Taler exchange (with RESTful API) .SH SYNOPSIS diff --git a/man/taler-exchange-kyc-aml-pep-trigger.1 b/man/taler-exchange-kyc-aml-pep-trigger.1 index 79ce8443..32754502 100644 --- a/man/taler-exchange-kyc-aml-pep-trigger.1 +++ b/man/taler-exchange-kyc-aml-pep-trigger.1 @@ -27,7 +27,7 @@ level margin: \\n[rst2man-indent\\n[rst2man-indent-level]] .\" new: \\n[rst2man-indent\\n[rst2man-indent-level]] .in \\n[rst2man-indent\\n[rst2man-indent-level]]u .. -.TH "TALER-EXCHANGE-KYC-AML-PEP-TRIGGER" "1" "Jul 11, 2023" "0.9" "GNU Taler" +.TH "TALER-EXCHANGE-KYC-AML-PEP-TRIGGER" "1" "Jul 15, 2023" "0.9" "GNU Taler" .SH NAME taler-exchange-kyc-aml-pep-trigger \- Taler KYC_AML_TRIGGER example .SH SYNOPSIS @@ -35,7 +35,7 @@ taler-exchange-kyc-aml-pep-trigger \- Taler KYC_AML_TRIGGER example \fBtaler\-exchange\-kyc\-aml\-pep\-trigger\fP .SH DESCRIPTION .sp -\fBtaler\-exchange\-kyc\-aml\-pep\-trigger\fP is a trivial shell script to illustrate how to trigger an AML process when the KYC process sets the "PEP" flag in the attribute data. +\fBtaler\-exchange\-kyc\-aml\-pep\-trigger\fP is a trivial shell script to illustrate how to trigger an AML process when the KYC process sets the \(dqPEP\(dq flag in the attribute data. .sp The script is mostly an example (or starting point) for writing programs for the KYC_AML_TRIGGER option of the diff --git a/man/taler-exchange-kyc-tester.1 b/man/taler-exchange-kyc-tester.1 index 8f3ade82..c96c69f0 100644 --- a/man/taler-exchange-kyc-tester.1 +++ b/man/taler-exchange-kyc-tester.1 @@ -27,7 +27,7 @@ level margin: \\n[rst2man-indent\\n[rst2man-indent-level]] .\" new: \\n[rst2man-indent\\n[rst2man-indent-level]] .in \\n[rst2man-indent\\n[rst2man-indent-level]]u .. -.TH "TALER-EXCHANGE-KYC-TESTER" "1" "Jul 11, 2023" "0.9" "GNU Taler" +.TH "TALER-EXCHANGE-KYC-TESTER" "1" "Jul 15, 2023" "0.9" "GNU Taler" .SH NAME taler-exchange-kyc-tester \- test KYC service integration .SH SYNOPSIS @@ -53,7 +53,7 @@ To use it, you must first provide a configuration file with at least one KYC ser .sp Begin with a first invocation of taler\-exchange\-kyc\-tester using the options \fB\-i\fP for an individual or business and use \fB\-R\fP to specify a list of checks required from the process. The output will be an URL to visit with the browser, as well as \fB\-p\fP, \fB\-u\fP, \fB\-U\fP options to use in future invocations of the tool. .sp -Next, run taler\-exchange\-kyc\-tester again, but this time using \fB\-w\fP (to run the Webserver) and using the \fB\-u\fP and \fB\-U\fP options output by the previous call, as well as the \fB\-p\fP option with the payto hash. Then visit the Web site from the link output by the previous invocation and "pass" (or "fail") the KYC check. +Next, run taler\-exchange\-kyc\-tester again, but this time using \fB\-w\fP (to run the Webserver) and using the \fB\-u\fP and \fB\-U\fP options output by the previous call, as well as the \fB\-p\fP option with the payto hash. Then visit the Web site from the link output by the previous invocation and \(dqpass\(dq (or \(dqfail\(dq) the KYC check. .INDENT 0.0 .TP \fB\-c\fP \fIFILENAME\fP | \fB\-\-config=\fP\fIFILENAME\fP @@ -71,7 +71,7 @@ Specifies the log level to use. Accepted values are: \fBDEBUG\fP, \fBINFO\fP, Send logging output to \fIFILENAME\fP\&. .TP \fB\-i\fP \fIUSERTYPE\fP | \fB\-\-initiate=\fP\fIUSERTYPE\fP -Specifies the type of user for which we are starting a fresh KYC process. USERTYPE must be either "individual" or "business". +Specifies the type of user for which we are starting a fresh KYC process. USERTYPE must be either \(dqindividual\(dq or \(dqbusiness\(dq. .TP \fB\-u\fP \fIID\fP | \fB\-\-user=\fP\fIID\fP Run the process with ID for the user identifier at the KYC provider. Not useful in conjunction with \fB\-i\fP and \fB\-R\fP as that option will override whatever value is provided here. diff --git a/man/taler-exchange-offline.1 b/man/taler-exchange-offline.1 index d6fb37d0..2d789cf3 100644 --- a/man/taler-exchange-offline.1 +++ b/man/taler-exchange-offline.1 @@ -27,7 +27,7 @@ level margin: \\n[rst2man-indent\\n[rst2man-indent-level]] .\" new: \\n[rst2man-indent\\n[rst2man-indent-level]] .in \\n[rst2man-indent\\n[rst2man-indent-level]]u .. -.TH "TALER-EXCHANGE-OFFLINE" "1" "Jul 11, 2023" "0.9" "GNU Taler" +.TH "TALER-EXCHANGE-OFFLINE" "1" "Jul 15, 2023" "0.9" "GNU Taler" .SH NAME taler-exchange-offline \- operations using the offline key of a Taler exchange .SH SYNOPSIS @@ -55,10 +55,10 @@ public keys from the running exchange. The resulting data serves as input to the \fBsign\fP and \fBshow\fP subcommands. The \fBupload\fP subcommand uploads the signatures created with the private master key to the exchange. It handles the output of all subcommands (except \fBdownload\fP). The \fBdownload\fP and -\fBupload\fP subcommands must naturally be run "online" and do not require +\fBupload\fP subcommands must naturally be run \(dqonline\(dq and do not require access to the offline key. .sp -All other subcommands are intended to be run "offline". However, especially +All other subcommands are intended to be run \(dqoffline\(dq. However, especially when testing, it is of course possible to run the subcommands online as well. Generally, subcommands read inputs (beyond command\-line arguments) from \fBstdin\fP\&. However, they may also consume outputs of previous @@ -102,7 +102,7 @@ $ taler\-exchange\-offline setup .UNINDENT .sp Note that if the private key file already exists, the above will simply output -the existing key. Passing additional arguments after setup (including "\-") +the existing key. Passing additional arguments after setup (including \(dq\-\(dq) will cause the output to be encapsulated in JSON. .sp Relevant configuration options for \fBtaler\-exchange\-offline\fP are: @@ -219,8 +219,8 @@ The auditor\(aqs public key must be given in the usual base32\-encoding as the first argument. .sp The auditor\(aqs REST API base URL must be given as the second argument. The tool -performs a minimal sanity check, namely that the URL begins with "http" -(this also allows "https"), but as it runs offline does not perform any further +performs a minimal sanity check, namely that the URL begins with \(dqhttp\(dq +(this also allows \(dqhttps\(dq), but as it runs offline does not perform any further validation! .sp The third argument must be a human\-readable name for the auditor. This may @@ -522,7 +522,7 @@ $ taler\-exchange\-offline upload < sigs.json .SS Download, sign and upload, all in one (online) .sp Note that doing this is only recommended in non\-production deployments, -as this requires putting the "offline" key onto a system that is actually +as this requires putting the \(dqoffline\(dq key onto a system that is actually online! .INDENT 0.0 .INDENT 3.5 @@ -587,8 +587,8 @@ $ taler\-exchange\-offline \e regex \e \(aqpayto://iban/.*/CH.*?receiver\-name=.*\(aq \e \(aqSwiss only\(aq \e - \(aq{ "de" : "nur Schweiz", \e - "fr" : "Suisse uniquement" }\(aq + \(aq{ \(dqde\(dq : \(dqnur Schweiz\(dq, \e + \(dqfr\(dq : \(dqSuisse uniquement\(dq }\(aq .ft P .fi .UNINDENT @@ -658,7 +658,7 @@ $ taler\-exchange\-offline \e .UNINDENT .UNINDENT .sp -The outputs ("revoke.json", "mix.json") must be uploaded using the \fBupload\fP +The outputs (\(dqrevoke.json\(dq, \(dqmix.json\(dq) must be uploaded using the \fBupload\fP subcommand to the exchange to actually revoke the keys. .SH SECURITY CONSIDERATIONS .sp @@ -667,8 +667,8 @@ system with \fImonotonic time\fP\&. The time does not have to precisely match th of the exchange, but it must be monotonic across tool invocations. The clock of the offline system is used in the enable/disable signatures to communicate an order of the events to the exchange. This prevents someone from replaying -an older "enable" (or "disable") message after a more recent "disable" (or -"enable") message has been provided to the exchange. Thus, there is no need +an older \(dqenable\(dq (or \(dqdisable\(dq) message after a more recent \(dqdisable\(dq (or +\(dqenable\(dq) message has been provided to the exchange. Thus, there is no need to keep the actual files exchanged with the offline tool secret. .sp The \fBtaler\-exchange\-offline\fP tool tries to make sure that the online signing diff --git a/man/taler-exchange-router.1 b/man/taler-exchange-router.1 index 16e7a6d4..39c24fe9 100644 --- a/man/taler-exchange-router.1 +++ b/man/taler-exchange-router.1 @@ -27,7 +27,7 @@ level margin: \\n[rst2man-indent\\n[rst2man-indent-level]] .\" new: \\n[rst2man-indent\\n[rst2man-indent-level]] .in \\n[rst2man-indent\\n[rst2man-indent-level]]u .. -.TH "TALER-EXCHANGE-ROUTER" "1" "Jul 11, 2023" "0.9" "GNU Taler" +.TH "TALER-EXCHANGE-ROUTER" "1" "Jul 15, 2023" "0.9" "GNU Taler" .SH NAME taler-exchange-router \- route payments to partner exchanges .SH SYNOPSIS diff --git a/man/taler-exchange-secmod-cs.1 b/man/taler-exchange-secmod-cs.1 index a57b651b..c693773a 100644 --- a/man/taler-exchange-secmod-cs.1 +++ b/man/taler-exchange-secmod-cs.1 @@ -27,7 +27,7 @@ level margin: \\n[rst2man-indent\\n[rst2man-indent-level]] .\" new: \\n[rst2man-indent\\n[rst2man-indent-level]] .in \\n[rst2man-indent\\n[rst2man-indent-level]]u .. -.TH "TALER-EXCHANGE-SECMOD-CS" "1" "Jul 11, 2023" "0.9" "GNU Taler" +.TH "TALER-EXCHANGE-SECMOD-CS" "1" "Jul 15, 2023" "0.9" "GNU Taler" .SH NAME taler-exchange-secmod-cs \- handle private CS key operations for a Taler exchange .SH SYNOPSIS diff --git a/man/taler-exchange-secmod-eddsa.1 b/man/taler-exchange-secmod-eddsa.1 index 5c156418..466d28d2 100644 --- a/man/taler-exchange-secmod-eddsa.1 +++ b/man/taler-exchange-secmod-eddsa.1 @@ -27,7 +27,7 @@ level margin: \\n[rst2man-indent\\n[rst2man-indent-level]] .\" new: \\n[rst2man-indent\\n[rst2man-indent-level]] .in \\n[rst2man-indent\\n[rst2man-indent-level]]u .. -.TH "TALER-EXCHANGE-SECMOD-EDDSA" "1" "Jul 11, 2023" "0.9" "GNU Taler" +.TH "TALER-EXCHANGE-SECMOD-EDDSA" "1" "Jul 15, 2023" "0.9" "GNU Taler" .SH NAME taler-exchange-secmod-eddsa \- handle private EDDSA key operations for a Taler exchange .SH SYNOPSIS diff --git a/man/taler-exchange-secmod-rsa.1 b/man/taler-exchange-secmod-rsa.1 index 1266ed45..a29575ab 100644 --- a/man/taler-exchange-secmod-rsa.1 +++ b/man/taler-exchange-secmod-rsa.1 @@ -27,7 +27,7 @@ level margin: \\n[rst2man-indent\\n[rst2man-indent-level]] .\" new: \\n[rst2man-indent\\n[rst2man-indent-level]] .in \\n[rst2man-indent\\n[rst2man-indent-level]]u .. -.TH "TALER-EXCHANGE-SECMOD-RSA" "1" "Jul 11, 2023" "0.9" "GNU Taler" +.TH "TALER-EXCHANGE-SECMOD-RSA" "1" "Jul 15, 2023" "0.9" "GNU Taler" .SH NAME taler-exchange-secmod-rsa \- handle private RSA key operations for a Taler exchange .SH SYNOPSIS diff --git a/man/taler-exchange-transfer.1 b/man/taler-exchange-transfer.1 index 86212c07..3231c4d0 100644 --- a/man/taler-exchange-transfer.1 +++ b/man/taler-exchange-transfer.1 @@ -27,7 +27,7 @@ level margin: \\n[rst2man-indent\\n[rst2man-indent-level]] .\" new: \\n[rst2man-indent\\n[rst2man-indent-level]] .in \\n[rst2man-indent\\n[rst2man-indent-level]]u .. -.TH "TALER-EXCHANGE-TRANSFER" "1" "Jul 11, 2023" "0.9" "GNU Taler" +.TH "TALER-EXCHANGE-TRANSFER" "1" "Jul 15, 2023" "0.9" "GNU Taler" .SH NAME taler-exchange-transfer \- execute wire transfers .SH SYNOPSIS diff --git a/man/taler-exchange-wire-gateway-client.1 b/man/taler-exchange-wire-gateway-client.1 index c1257b66..9c67fcfa 100644 --- a/man/taler-exchange-wire-gateway-client.1 +++ b/man/taler-exchange-wire-gateway-client.1 @@ -27,7 +27,7 @@ level margin: \\n[rst2man-indent\\n[rst2man-indent-level]] .\" new: \\n[rst2man-indent\\n[rst2man-indent-level]] .in \\n[rst2man-indent\\n[rst2man-indent-level]]u .. -.TH "TALER-EXCHANGE-WIRE-GATEWAY-CLIENT" "1" "Jul 11, 2023" "0.9" "GNU Taler" +.TH "TALER-EXCHANGE-WIRE-GATEWAY-CLIENT" "1" "Jul 15, 2023" "0.9" "GNU Taler" .SH NAME taler-exchange-wire-gateway-client \- trigger a transfer at the bank .SH SYNOPSIS diff --git a/man/taler-exchange-wirewatch.1 b/man/taler-exchange-wirewatch.1 index 22b2fcda..adbe200c 100644 --- a/man/taler-exchange-wirewatch.1 +++ b/man/taler-exchange-wirewatch.1 @@ -27,7 +27,7 @@ level margin: \\n[rst2man-indent\\n[rst2man-indent-level]] .\" new: \\n[rst2man-indent\\n[rst2man-indent-level]] .in \\n[rst2man-indent\\n[rst2man-indent-level]]u .. -.TH "TALER-EXCHANGE-WIREWATCH" "1" "Jul 11, 2023" "0.9" "GNU Taler" +.TH "TALER-EXCHANGE-WIREWATCH" "1" "Jul 15, 2023" "0.9" "GNU Taler" .SH NAME taler-exchange-wirewatch \- watch for incoming wire transfers .SH SYNOPSIS diff --git a/man/taler-helper-auditor-aggregation.1 b/man/taler-helper-auditor-aggregation.1 index a7ff1233..d5a0949d 100644 --- a/man/taler-helper-auditor-aggregation.1 +++ b/man/taler-helper-auditor-aggregation.1 @@ -27,7 +27,7 @@ level margin: \\n[rst2man-indent\\n[rst2man-indent-level]] .\" new: \\n[rst2man-indent\\n[rst2man-indent-level]] .in \\n[rst2man-indent\\n[rst2man-indent-level]]u .. -.TH "TALER-HELPER-AUDITOR-AGGREGATION" "1" "Jul 11, 2023" "0.9" "GNU Taler" +.TH "TALER-HELPER-AUDITOR-AGGREGATION" "1" "Jul 15, 2023" "0.9" "GNU Taler" .SH NAME taler-helper-auditor-aggregation \- audit Taler exchange aggregation activity .SH SYNOPSIS diff --git a/man/taler-helper-auditor-coins.1 b/man/taler-helper-auditor-coins.1 index 502efc82..32c500af 100644 --- a/man/taler-helper-auditor-coins.1 +++ b/man/taler-helper-auditor-coins.1 @@ -27,7 +27,7 @@ level margin: \\n[rst2man-indent\\n[rst2man-indent-level]] .\" new: \\n[rst2man-indent\\n[rst2man-indent-level]] .in \\n[rst2man-indent\\n[rst2man-indent-level]]u .. -.TH "TALER-HELPER-AUDITOR-COINS" "1" "Jul 11, 2023" "0.9" "GNU Taler" +.TH "TALER-HELPER-AUDITOR-COINS" "1" "Jul 15, 2023" "0.9" "GNU Taler" .SH NAME taler-helper-auditor-coins \- audit Taler coin processing .SH SYNOPSIS diff --git a/man/taler-helper-auditor-deposits.1 b/man/taler-helper-auditor-deposits.1 index 88634f51..0ba7d4f1 100644 --- a/man/taler-helper-auditor-deposits.1 +++ b/man/taler-helper-auditor-deposits.1 @@ -27,7 +27,7 @@ level margin: \\n[rst2man-indent\\n[rst2man-indent-level]] .\" new: \\n[rst2man-indent\\n[rst2man-indent-level]] .in \\n[rst2man-indent\\n[rst2man-indent-level]]u .. -.TH "TALER-HELPER-AUDITOR-DEPOSITS" "1" "Jul 11, 2023" "0.9" "GNU Taler" +.TH "TALER-HELPER-AUDITOR-DEPOSITS" "1" "Jul 15, 2023" "0.9" "GNU Taler" .SH NAME taler-helper-auditor-deposits \- audit Taler exchange database for deposit confirmation consistency .SH SYNOPSIS diff --git a/man/taler-helper-auditor-purses.1 b/man/taler-helper-auditor-purses.1 index 089d6aca..c8b70818 100644 --- a/man/taler-helper-auditor-purses.1 +++ b/man/taler-helper-auditor-purses.1 @@ -27,7 +27,7 @@ level margin: \\n[rst2man-indent\\n[rst2man-indent-level]] .\" new: \\n[rst2man-indent\\n[rst2man-indent-level]] .in \\n[rst2man-indent\\n[rst2man-indent-level]]u .. -.TH "TALER-HELPER-AUDITOR-PURSES" "1" "Jul 11, 2023" "0.9" "GNU Taler" +.TH "TALER-HELPER-AUDITOR-PURSES" "1" "Jul 15, 2023" "0.9" "GNU Taler" .SH NAME taler-helper-auditor-purses \- audit Taler exchange purse handling .SH SYNOPSIS diff --git a/man/taler-helper-auditor-reserves.1 b/man/taler-helper-auditor-reserves.1 index e8c360ee..82a36a79 100644 --- a/man/taler-helper-auditor-reserves.1 +++ b/man/taler-helper-auditor-reserves.1 @@ -27,7 +27,7 @@ level margin: \\n[rst2man-indent\\n[rst2man-indent-level]] .\" new: \\n[rst2man-indent\\n[rst2man-indent-level]] .in \\n[rst2man-indent\\n[rst2man-indent-level]]u .. -.TH "TALER-HELPER-AUDITOR-RESERVES" "1" "Jul 11, 2023" "0.9" "GNU Taler" +.TH "TALER-HELPER-AUDITOR-RESERVES" "1" "Jul 15, 2023" "0.9" "GNU Taler" .SH NAME taler-helper-auditor-reserves \- audit Taler exchange reserve handling .SH SYNOPSIS diff --git a/man/taler-helper-auditor-wire.1 b/man/taler-helper-auditor-wire.1 index 07035840..73e81d19 100644 --- a/man/taler-helper-auditor-wire.1 +++ b/man/taler-helper-auditor-wire.1 @@ -27,7 +27,7 @@ level margin: \\n[rst2man-indent\\n[rst2man-indent-level]] .\" new: \\n[rst2man-indent\\n[rst2man-indent-level]] .in \\n[rst2man-indent\\n[rst2man-indent-level]]u .. -.TH "TALER-HELPER-AUDITOR-WIRE" "1" "Jul 11, 2023" "0.9" "GNU Taler" +.TH "TALER-HELPER-AUDITOR-WIRE" "1" "Jul 15, 2023" "0.9" "GNU Taler" .SH NAME taler-helper-auditor-wire \- audit exchange database for consistency with the bank's wire transfers .SH SYNOPSIS diff --git a/man/taler-merchant-benchmark.1 b/man/taler-merchant-benchmark.1 index a85e3ef1..96db7e31 100644 --- a/man/taler-merchant-benchmark.1 +++ b/man/taler-merchant-benchmark.1 @@ -27,7 +27,7 @@ level margin: \\n[rst2man-indent\\n[rst2man-indent-level]] .\" new: \\n[rst2man-indent\\n[rst2man-indent-level]] .in \\n[rst2man-indent\\n[rst2man-indent-level]]u .. -.TH "TALER-MERCHANT-BENCHMARK" "1" "Jul 11, 2023" "0.9" "GNU Taler" +.TH "TALER-MERCHANT-BENCHMARK" "1" "Jul 15, 2023" "0.9" "GNU Taler" .SH NAME taler-merchant-benchmark \- generate Taler-style benchmarking payments .SH SYNOPSIS diff --git a/man/taler-merchant-dbinit.1 b/man/taler-merchant-dbinit.1 index 675856cd..f6881e1c 100644 --- a/man/taler-merchant-dbinit.1 +++ b/man/taler-merchant-dbinit.1 @@ -27,7 +27,7 @@ level margin: \\n[rst2man-indent\\n[rst2man-indent-level]] .\" new: \\n[rst2man-indent\\n[rst2man-indent-level]] .in \\n[rst2man-indent\\n[rst2man-indent-level]]u .. -.TH "TALER-MERCHANT-DBINIT" "1" "Jul 11, 2023" "0.9" "GNU Taler" +.TH "TALER-MERCHANT-DBINIT" "1" "Jul 15, 2023" "0.9" "GNU Taler" .SH NAME taler-merchant-dbinit \- initialize Taler merchant database .SH SYNOPSIS diff --git a/man/taler-merchant-httpd.1 b/man/taler-merchant-httpd.1 index 613197d0..19b6c49d 100644 --- a/man/taler-merchant-httpd.1 +++ b/man/taler-merchant-httpd.1 @@ -27,7 +27,7 @@ level margin: \\n[rst2man-indent\\n[rst2man-indent-level]] .\" new: \\n[rst2man-indent\\n[rst2man-indent-level]] .in \\n[rst2man-indent\\n[rst2man-indent-level]]u .. -.TH "TALER-MERCHANT-HTTPD" "1" "Jul 11, 2023" "0.9" "GNU Taler" +.TH "TALER-MERCHANT-HTTPD" "1" "Jul 15, 2023" "0.9" "GNU Taler" .SH NAME taler-merchant-httpd \- run Taler merchant backend (with RESTful API) .SH SYNOPSIS @@ -50,13 +50,13 @@ before running this command. .INDENT 0.0 .TP \fB\-a\fP \fITOKEN\fP | \fB\-\-auth=\fP\fITOKEN\fP -Use TOKEN for initial access control to the merchant backend. TOKEN must start with the "secret\-token:" prefix, as per RFC 8959. The value +Use TOKEN for initial access control to the merchant backend. TOKEN must start with the \(dqsecret\-token:\(dq prefix, as per RFC 8959. The value given in TOKEN must appear in backoffice requests to the default instance -of the merchant, i.e. "Authorization: Bearer TOKEN" to obtain +of the merchant, i.e. \(dqAuthorization: Bearer TOKEN\(dq to obtain access to the merchant backend. Note that setting a passphrase for the default instance by any means will block future access via TOKEN. This is basically a way to reset the passphrase protecting access. TOKEN -should be a "pchar" as per RFC 8959, but this is NOT checked. Note that +should be a \(dqpchar\(dq as per RFC 8959, but this is NOT checked. Note that TOKEN will only grant access to the \(aqdefault\(aq instance, not other instances. Instead of using the command\-line, which exposes TOKEN to users on the system, you may want to consider setting the @@ -100,7 +100,7 @@ cleanly. .INDENT 0.0 .TP .B TALER_MERCHANT_TOKEN -Like the "\-a" option, resets the access token for the default +Like the \(dq\-a\(dq option, resets the access token for the default instance to the given value. .UNINDENT .SH SEE ALSO diff --git a/man/taler-merchant-setup-reserve.1 b/man/taler-merchant-setup-reserve.1 index 3e5ab340..4c449cad 100644 --- a/man/taler-merchant-setup-reserve.1 +++ b/man/taler-merchant-setup-reserve.1 @@ -27,7 +27,7 @@ level margin: \\n[rst2man-indent\\n[rst2man-indent-level]] .\" new: \\n[rst2man-indent\\n[rst2man-indent-level]] .in \\n[rst2man-indent\\n[rst2man-indent-level]]u .. -.TH "TALER-MERCHANT-SETUP-RESERVE" "1" "Jul 11, 2023" "0.9" "GNU Taler" +.TH "TALER-MERCHANT-SETUP-RESERVE" "1" "Jul 15, 2023" "0.9" "GNU Taler" .SH NAME taler-merchant-setup-reserve \- setup reserve for tipping at a Taler merchant backend .SH SYNOPSIS @@ -57,7 +57,7 @@ from the exchange needed to fill the reserve. .TP \fB\-A\fP \fIUSERNAME:PASSWORD\fP | \fB\-\-auth=\fP\fIUSERNAME:PASSWORD\fP Use \fBUSERNAME\fP and \fBPASSWORD\fP for HTTP client authentication. -The ":" must be present as a separator. +The \(dq:\(dq must be present as a separator. Note that this form of authentication has nothing to do with the TLS client certificate authentication supported with the \fB\-C\fP, \fB\-k\fP and \fB\-p\fP options. The \fBPASSWORD\fP given to this option is given to the server! diff --git a/man/taler-merchant-webhook.1 b/man/taler-merchant-webhook.1 index b2dd0b3f..7f9a8ac8 100644 --- a/man/taler-merchant-webhook.1 +++ b/man/taler-merchant-webhook.1 @@ -27,7 +27,7 @@ level margin: \\n[rst2man-indent\\n[rst2man-indent-level]] .\" new: \\n[rst2man-indent\\n[rst2man-indent-level]] .in \\n[rst2man-indent\\n[rst2man-indent-level]]u .. -.TH "TALER-MERCHANT-WEBHOOK" "1" "Jul 11, 2023" "0.9" "GNU Taler" +.TH "TALER-MERCHANT-WEBHOOK" "1" "Jul 15, 2023" "0.9" "GNU Taler" .SH NAME taler-merchant-webhook \- execute webhooks of the Taler merchant backend (optional service) .SH SYNOPSIS diff --git a/man/taler-merchant-wirewatch.1 b/man/taler-merchant-wirewatch.1 index 2af0ba63..bd8a111f 100644 --- a/man/taler-merchant-wirewatch.1 +++ b/man/taler-merchant-wirewatch.1 @@ -27,7 +27,7 @@ level margin: \\n[rst2man-indent\\n[rst2man-indent-level]] .\" new: \\n[rst2man-indent\\n[rst2man-indent-level]] .in \\n[rst2man-indent\\n[rst2man-indent-level]]u .. -.TH "TALER-MERCHANT-WIREWATCH" "1" "Jul 11, 2023" "0.9" "GNU Taler" +.TH "TALER-MERCHANT-WIREWATCH" "1" "Jul 15, 2023" "0.9" "GNU Taler" .SH NAME taler-merchant-wirewatch \- import credit transactions from a merchant bank account into merchant backend (optional) .SH SYNOPSIS diff --git a/manpages/taler-unified-setup.1 b/man/taler-unified-setup.1 index 06a94fd9..06a94fd9 100644 --- a/manpages/taler-unified-setup.1 +++ b/man/taler-unified-setup.1 diff --git a/man/taler.conf.5 b/man/taler.conf.5 index 1d3d73bf..54ad1f23 100644 --- a/man/taler.conf.5 +++ b/man/taler.conf.5 @@ -27,7 +27,7 @@ level margin: \\n[rst2man-indent\\n[rst2man-indent-level]] .\" new: \\n[rst2man-indent\\n[rst2man-indent-level]] .in \\n[rst2man-indent\\n[rst2man-indent-level]]u .. -.TH "TALER.CONF" "5" "Jul 11, 2023" "0.9" "GNU Taler" +.TH "TALER.CONF" "5" "Jul 15, 2023" "0.9" "GNU Taler" .SH NAME taler.conf \- Taler configuration file .SH DESCRIPTION @@ -46,7 +46,7 @@ Section names and options are \fIcase\-insensitive\fP\&. The values, however, are \fIcase\-sensitive\fP\&. In particular, boolean values are one of \fBYES\fP or \fBNO\fP\&. Values can include whitespace by surrounding -the entire value with \fB"\fP (double quote). +the entire value with \fB\(dq\fP (double quote). Note, however, that there are no escape characters in such strings; all characters between the double quotes (including other double quotes) are taken verbatim. @@ -128,7 +128,7 @@ Name of the currency, e.g.\ “EUR” for Euro. .TP .B CURRENCY_ROUND_UNIT Smallest amount in this currency that can be transferred using the -underlying RTGS. For example: "EUR:0.01" or "JPY:1". +underlying RTGS. For example: \(dqEUR:0.01\(dq or \(dqJPY:1\(dq. .UNINDENT .sp The “[PATHS]” section is special in that it contains paths that can be @@ -166,19 +166,19 @@ exchange tools. Plugin to use for the database, e.g.\ “postgres”. .TP .B SERVE -Should the HTTP server listen on a UNIX domain socket (set option to "unix") or on a TCP socket (set option to "tcp")? +Should the HTTP server listen on a UNIX domain socket (set option to \(dqunix\(dq) or on a TCP socket (set option to \(dqtcp\(dq)? .TP .B UNIXPATH -Path to listen on if we "SERVE" is set to "unix". +Path to listen on if we \(dqSERVE\(dq is set to \(dqunix\(dq. .TP .B UNIXPATH_MODE -Access permission mask to use for the "UNIXPATH". +Access permission mask to use for the \(dqUNIXPATH\(dq. .TP .B PORT Port on which the HTTP server listens, e.g.\ 8080. .TP .B BIND_TO -Hostname to which the exchange HTTP server should be bound to, e.g. "localhost". +Hostname to which the exchange HTTP server should be bound to, e.g. \(dqlocalhost\(dq. .TP .B MASTER_PUBLIC_KEY Crockford Base32\-encoded master public key, public version of the @@ -190,7 +190,7 @@ can be run offline (as the master key is for offline signing). .TP .B AML_THRESHOLD Largest amount in this currency that can be transferred per month without -an AML staff member doing a (manual) AML check. For example: "USD:1000000". +an AML staff member doing a (manual) AML check. For example: \(dqUSD:1000000\(dq. .TP .B KYC_AML_TRIGGER Program to run on KYC attribute data to decide whether we should immediately flag an account for AML review. Program must return 0 if a manual AML review is not needed, and non\-zero to trigger an AML review. The KYC attribute data of the new user will be passed on standard\-input. @@ -224,7 +224,7 @@ For how long should the taler\-exchange\-wirewatch sleep when it is idle before trying to look for more work? Default is 60 seconds. .TP .B AGGREGATOR_SHARD_SIZE -Which share of the range from [0,..2147483648] should be processed by one of the shards of the aggregator. Useful only for Taler exchanges with ultra high\-performance needs. When changing this value, you must stop all aggregators and run "taler\-exchange\-dbinit \-s" before resuming. Default is 2147483648 (no sharding). +Which share of the range from [0,..2147483648] should be processed by one of the shards of the aggregator. Useful only for Taler exchanges with ultra high\-performance needs. When changing this value, you must stop all aggregators and run \(dqtaler\-exchange\-dbinit \-s\(dq before resuming. Default is 2147483648 (no sharding). .TP .B SIGNKEY_LEGAL_DURATION For how long are signatures with signing keys legally valid? @@ -238,12 +238,12 @@ How many requests should the HTTP server process at most before committing suici .B TERMS_DIR Directory where the terms of service of the exchange operator can be fund. The directory must contain sub\-directories for every supported language, -using the two\-character language code in lower case, e.g. "en/" or "fr/". +using the two\-character language code in lower case, e.g. \(dqen/\(dq or \(dqfr/\(dq. Each subdirectory must then contain files with the terms of service in various formats. The basename of the file of the current policy must be specified under \fBTERMS_ETAG\fP\&. The extension defines the mime type. -Supported extensions include "html", "htm", "txt", "pdf", "jpg", "jpeg", -"png" and "gif". For example, using a \fBTERMS_ETAG\fP of "0", the structure +Supported extensions include \(dqhtml\(dq, \(dqhtm\(dq, \(dqtxt\(dq, \(dqpdf\(dq, \(dqjpg\(dq, \(dqjpeg\(dq, +\(dqpng\(dq and \(dqgif\(dq. For example, using a \fBTERMS_ETAG\fP of \(dq0\(dq, the structure could be the following: .INDENT 7.0 .IP \(bu 2 @@ -262,7 +262,7 @@ $TERMS_DIR/de/0.txt .TP .B TERMS_ETAG Basename of the file(s) in the \fBTERMS_DIR\fP with the current terms of service. -The value is also used for the "Etag" in the HTTP request to control +The value is also used for the \(dqEtag\(dq in the HTTP request to control caching. Whenever the terms of service change, the \fBTERMS_ETAG\fP MUST also change, and old values MUST NOT be repeated. For example, the date or version number of the terms of service SHOULD be used for the Etag. If @@ -278,7 +278,7 @@ Works the same as \fBTERMS_ETAG\fP, just for the privacy policy. .UNINDENT .SS EXCHANGE KYC PROVIDER OPTIONS .sp -The following options must be in the section "[kyc\-provider\-XXX]" sections. +The following options must be in the section \(dq[kyc\-provider\-XXX]\(dq sections. .INDENT 0.0 .TP .B COST @@ -295,20 +295,20 @@ List of checks performed by this provider. Space\-separated names of checks, mus .UNINDENT .SS EXCHANGE KYC OAUTH2 OPTIONS .sp -The following options must be in the section "[kyc\-provider\-XXX]" sections with "LOGIC = oauth2". +The following options must be in the section \(dq[kyc\-provider\-XXX]\(dq sections with \(dqLOGIC = oauth2\(dq. .INDENT 0.0 .TP .B KYC_OAUTH2_VALIDITY -Duration (e.g. "12 months") of the validity of the performed KYC check. Can be "forever". +Duration (e.g. \(dq12 months\(dq) of the validity of the performed KYC check. Can be \(dqforever\(dq. .TP .B KYC_OAUTH2_AUTHORIZE_URL -URL of the OAuth2 endpoint to be used for KYC checks. The authorize URL is where the exchange will redirect the client to begin the authorization process. Example: "\fI\%http://localhost:8888/oauth/v2/authorize\fP". To use the plugin in combination with the Challenger service\(aqs \fB/setup\fP step, append "#setup", thus "\fI\%https://challenger.example.com/authorize#setup\fP". Here, "#setup" is not a fragment but merely a hint to the logic to determine the full authorization URL via the \fB/setup\fP handler. +URL of the OAuth2 endpoint to be used for KYC checks. The authorize URL is where the exchange will redirect the client to begin the authorization process. Example: \(dq\fI\%http://localhost:8888/oauth/v2/authorize\fP\(dq. To use the plugin in combination with the Challenger service\(aqs \fB/setup\fP step, append \(dq#setup\(dq, thus \(dq\fI\%https://challenger.example.com/authorize#setup\fP\(dq. Here, \(dq#setup\(dq is not a fragment but merely a hint to the logic to determine the full authorization URL via the \fB/setup\fP handler. .TP .B KYC_OAUTH2_TOKEN_URL -URL of the OAuth2 endpoint to be used for KYC checks. This is where the server will ultimately send the authorization token from the client and obtain its access token (which currently must be a "bearer" token). Example: "\fI\%http://localhost:8888/oauth/v2/token\fP" (or just "/token") +URL of the OAuth2 endpoint to be used for KYC checks. This is where the server will ultimately send the authorization token from the client and obtain its access token (which currently must be a \(dqbearer\(dq token). Example: \(dq\fI\%http://localhost:8888/oauth/v2/token\fP\(dq (or just \(dq/token\(dq) .TP .B KYC_OAUTH2_INFO_URL -URL of the OAuth2\-protected resource endpoint, where the OAuth 2.0 token can be used to download information about the user that has undergone the KYC process. The exchange will use the access token obtained from the KYC_AUTH2_AUTH_URL to show that it is authorized to obtain the details. Example: "\fI\%http://localhost:8888/api/user/me\fP" or "\fI\%http://localhost:8888/oauth/v2/info\fP" +URL of the OAuth2\-protected resource endpoint, where the OAuth 2.0 token can be used to download information about the user that has undergone the KYC process. The exchange will use the access token obtained from the KYC_AUTH2_AUTH_URL to show that it is authorized to obtain the details. Example: \(dq\fI\%http://localhost:8888/api/user/me\fP\(dq or \(dq\fI\%http://localhost:8888/oauth/v2/info\fP\(dq .TP .B KYC_OAUTH2_CLIENT_ID Client ID of the exchange when it talks to the KYC OAuth2 endpoint. @@ -317,15 +317,15 @@ Client ID of the exchange when it talks to the KYC OAuth2 endpoint. Client secret of the exchange to use when talking to the KYC Oauth2 endpoint. .TP .B KYC_OAUTH2_POST_URL -URL to which the exchange will redirect the client\(aqs browser after successful authorization/login for the KYC process. Example: "\fI\%http://example.com/thank\-you\fP" +URL to which the exchange will redirect the client\(aqs browser after successful authorization/login for the KYC process. Example: \(dq\fI\%http://example.com/thank\-you\fP\(dq .UNINDENT .SS EXCHANGE KYC KYCAID OPTIONS .sp -The following options must be in the section "[kyc\-provider\-XXX]" sections with "LOGIC = kycaid". +The following options must be in the section \(dq[kyc\-provider\-XXX]\(dq sections with \(dqLOGIC = kycaid\(dq. .INDENT 0.0 .TP .B KYC_KYCAID_VALIDITY -Duration (e.g. "12 months") of the validity of the performed KYC check. Can be "forever". +Duration (e.g. \(dq12 months\(dq) of the validity of the performed KYC check. Can be \(dqforever\(dq. .TP .B KYC_KYCAID_AUTH_TOKEN Authentication token to access the KYC service. @@ -338,11 +338,11 @@ URL to which the exchange will redirect the client\(aqs browser after successful .UNINDENT .SS EXCHANGE KYC PERSONA OPTIONS .sp -The following options must be in the section "[kyc\-provider\-XXX]" sections with "LOGIC = persona". +The following options must be in the section \(dq[kyc\-provider\-XXX]\(dq sections with \(dqLOGIC = persona\(dq. .INDENT 0.0 .TP .B KYC_PERSONA_VALIDITY -Duration (e.g. "12 months") of the validity of the performed KYC check. Can be "forever". +Duration (e.g. \(dq12 months\(dq) of the validity of the performed KYC check. Can be \(dqforever\(dq. .TP .B KYC_PERSONA_AUTH_TOKEN Authentication token to access the KYC service. @@ -354,7 +354,7 @@ Salt value to use for request idempotency. Optional, generated at random per pro Subdomain to use under Persona. .TP .B KYC_PERSONA_CONVERTER_HELPER -Helper to convert JSON with KYC data returned by Persona into GNU Taler internal format. Should probably always be set to "taler\-exchange\-kyc\-persona\-converter.sh". +Helper to convert JSON with KYC data returned by Persona into GNU Taler internal format. Should probably always be set to \(dqtaler\-exchange\-kyc\-persona\-converter.sh\(dq. .TP .B KYC_PERSONA_POST_URL URL to which the exchange will redirect the client\(aqs browser after successful authorization/login for the KYC process. @@ -364,7 +364,7 @@ ID of the Persona template to use. .UNINDENT .SS EXCHANGE KYC PERSONA GLOBAL OPTIONS .sp -The following option must be in the section "[kyclogic\-persona]". +The following option must be in the section \(dq[kyclogic\-persona]\(dq. .INDENT 0.0 .TP .B WEBHOOK_AUTH_TOKEN @@ -376,7 +376,7 @@ The functionality of the exchange can be extended by extensions. Those are shared libraries which implement the extension\-API of the exchange and are located under \fB$LIBDIR\fP, starting with prefix \fBlibtaler_extension_\fP\&. Each extension can be enabled by adding a dedicated section -"[exchange\-extension\-<extensionname>]" and the following option: +\(dq[exchange\-extension\-<extensionname>]\(dq and the following option: .INDENT 0.0 .TP .B ENABLED @@ -386,7 +386,7 @@ options might be set in the same section. .SS EXCHANGE EXTENSION FOR AGE RESTRICTION .sp The extension for age restriction support can be enabled by adding a section -"[exchange\-extension\-age_restriction]" with the following options: +\(dq[exchange\-extension\-age_restriction]\(dq with the following options: .INDENT 0.0 .TP .B ENABLE @@ -396,7 +396,7 @@ Must be set to \fBYES\fP in order to activate the extension. A colon\-seperated string of increasing non\-negative integers, defining the buckets of age groups supported by the exchange. Each integer marks the beginning of the next age group. The zero\(aqth age group implicitly starts -with 0. For example, the string "10:18" would define three age groups: +with 0. For example, the string \(dq10:18\(dq would define three age groups: .INDENT 7.0 .INDENT 3.5 .INDENT 0.0 @@ -410,7 +410,7 @@ Group 2: ages 18 and above .UNINDENT .UNINDENT .sp -If not provided, the default value is "8:10:12:14:16:18:21". +If not provided, the default value is \(dq8:10:12:14:16:18:21\(dq. .UNINDENT .sp \fBNote\fP: Age restriction is bound to specific denominations and must be @@ -419,7 +419,7 @@ the option \fBAGE_RESTRICTED = YES\fP, see \fI\%EXCHANGE COIN OPTIONS\fP\&. Howe age groups are defined globally for all denominations. .SS EXCHANGE OFFLINE SIGNING OPTIONS .sp -The following options must be in the section "[exchange\-offline]". +The following options must be in the section \(dq[exchange\-offline]\(dq. .INDENT 0.0 .TP .B MASTER_PRIV_FILE @@ -445,7 +445,7 @@ this option will also be ignored. .UNINDENT .SS EXCHANGE RSA CRYPTO HELPER OPTIONS .sp -The following options must be in the section "[taler\-exchange\-secmod\-rsa]". +The following options must be in the section \(dq[taler\-exchange\-secmod\-rsa]\(dq. .INDENT 0.0 .TP .B LOOKAHEAD_SIGN @@ -472,7 +472,7 @@ Note that the \fBtaler\-exchange\-secmod\-rsa\fP also evaluates the \fB[coin_*]\ configuration sections described below. .SS EXCHANGE CS CRYPTO HELPER OPTIONS .sp -The following options must be in the section "[taler\-exchange\-secmod\-cs]". +The following options must be in the section \(dq[taler\-exchange\-secmod\-cs]\(dq. .INDENT 0.0 .TP .B LOOKAHEAD_SIGN @@ -499,7 +499,7 @@ Note that the \fBtaler\-exchange\-secmod\-cs\fP also evaluates the \fB[coin_*]\f configuration sections described below. .SS EXCHANGE EDDSA CRYPTO HELPER OPTIONS .sp -The following options must be in the section "[taler\-exchange\-secmod\-eddsa]". +The following options must be in the section \(dq[taler\-exchange\-secmod\-eddsa]\(dq. .INDENT 0.0 .TP .B LOOKAHEAD_SIGN @@ -526,7 +526,7 @@ On which path should the security module listen for signing requests? .UNINDENT .SS EXCHANGE DATABASE OPTIONS .sp -The following options must be in the section "[exchangedb]". +The following options must be in the section \(dq[exchangedb]\(dq. .INDENT 0.0 .TP .B IDLE_RESERVE_EXPIRATION_TIME @@ -603,7 +603,7 @@ Password for \fBbasic\fP authentication with the wire gateway. .UNINDENT .SS EXCHANGE COIN OPTIONS .sp -The following options must be in sections starting with \fB"[coin_]"\fP and are +The following options must be in sections starting with \fB\(dq[coin_]\(dq\fP and are largely used by \fBtaler\-exchange\-httpd\fP to determine the meta data for the denomination keys. Some of the options are used by the \fBtaler\-exchange\-secmod\-rsa\fP to determine which RSA keys to create (and of @@ -642,12 +642,12 @@ What fee is charged for refunds? When a coin is refunded, the deposit fee is returned. Instead, the refund fee is charged to the customer. .TP .B CIPHER -What cryptosystem should be used? Must be set to either "CS" or "RSA". +What cryptosystem should be used? Must be set to either \(dqCS\(dq or \(dqRSA\(dq. The respective crypto\-helper will then generate the keys for this denomination. .TP .B RSA_KEYSIZE -What is the RSA keysize modulos (in bits)? Only used if "CIPHER=RSA". +What is the RSA keysize modulos (in bits)? Only used if \(dqCIPHER=RSA\(dq. .TP .B AGE_RESTRICTED Setting this option to \fBYES\fP marks the denomination as age restricted @@ -664,19 +664,19 @@ merchant backend. Plugin to use for the database, e.g._“postgres”. .TP .B SERVE -Should the HTTP server listen on a UNIX domain socket (set option to "unix") or on a TCP socket (set option to "tcp")? +Should the HTTP server listen on a UNIX domain socket (set option to \(dqunix\(dq) or on a TCP socket (set option to \(dqtcp\(dq)? .TP .B UNIXPATH -Path to listen on if we "SERVE" is set to "unix". +Path to listen on if we \(dqSERVE\(dq is set to \(dqunix\(dq. .TP .B UNIXPATH_MODE -Access permission mask to use for the "UNIXPATH". +Access permission mask to use for the \(dqUNIXPATH\(dq. .TP .B PORT Port on which the HTTP server listens, e.g.\ 8080. .TP .B BIND_TO -Hostname to which the merchant HTTP server should be bound to, e.g. "localhost". +Hostname to which the merchant HTTP server should be bound to, e.g. \(dqlocalhost\(dq. .TP .B LEGAL_PRESERVATION How long do we keep data in the database for tax audits after the @@ -744,19 +744,19 @@ processes that do not have access to the (offline) auditor private key file. Base URL of the auditor, e.g.\ “\fI\%https://auditor.demo.taler.net/\fP” .TP .B SERVE -Should the HTTP server listen on a UNIX domain socket (set option to "unix") or on a TCP socket (set option to "tcp")? +Should the HTTP server listen on a UNIX domain socket (set option to \(dqunix\(dq) or on a TCP socket (set option to \(dqtcp\(dq)? .TP .B UNIXPATH -Path to listen on if we "SERVE" is set to "unix". +Path to listen on if we \(dqSERVE\(dq is set to \(dqunix\(dq. .TP .B UNIXPATH_MODE -Access permission mask to use for the "UNIXPATH". +Access permission mask to use for the \(dqUNIXPATH\(dq. .TP .B PORT Port on which the HTTP server listens, e.g.\ 8080. .TP .B BIND_TO -Hostname to which the merchant HTTP server should be bound to, e.g. "localhost". +Hostname to which the merchant HTTP server should be bound to, e.g. \(dqlocalhost\(dq. .UNINDENT .SS AUDITOR POSTGRES BACKEND DATABASE OPTIONS .sp @@ -765,12 +765,12 @@ The following options must be in section “[auditordb\-postgres]” if the .INDENT 0.0 .TP .B CONFIG -How to access the database, e.g.\ "postgres:///taler" to use the -"taler" database. Testcases use “talercheck”. +How to access the database, e.g.\ \(dqpostgres:///taler\(dq to use the +\(dqtaler\(dq database. Testcases use “talercheck”. .UNINDENT .SS Bank Options .sp -The following options must be in section "[bank]" for the taler\-fakebank\-run(1) command. They are not used by the exchange or LibEuFin! +The following options must be in section \(dq[bank]\(dq for the taler\-fakebank\-run(1) command. They are not used by the exchange or LibEuFin! .INDENT 0.0 .TP .B HTTP_PORT |