taler-docs

Documentation for GNU Taler components, APIs and protocols
Log | Files | Refs | README | LICENSE

commit 0308e3346eb6fdae5e5fba05164c372413e625fd
parent 880e5301088392393451e31ca5ab8bb2eaaca1fa
Author: Marcello Stanisci <marcello.stanisci@inria.fr>
Date:   Sat, 22 Oct 2016 19:52:44 +0200

fix unresolved link + installation chapter titles

Diffstat:
Mapi-exchange.rst | 2+-
Moperate-exchange.rst | 6++++++
Moperate-merchant.rst | 6++++++
3 files changed, 13 insertions(+), 1 deletion(-)

diff --git a/api-exchange.rst b/api-exchange.rst @@ -549,7 +549,7 @@ denomination. // The string constant "DEPOSIT_OK" status: string; - // the EdDSA signature of `TALER_DepositConfirmation`_ using a current + // the EdDSA signature of `TALER_DepositConfirmationPS`_ using a current // `signing key of the exchange <sign-key-priv>`_ affirming the successful // deposit and that the exchange will transfer the funds after the refund // deadline, or as soon as possible if the refund deadline is zero. diff --git a/operate-exchange.rst b/operate-exchange.rst @@ -167,6 +167,12 @@ Keys duration Both `signkeys` and `denom keys` have a :ref:`starting date <keys-duration>`. The option `lookahead_provide`, under section `[exchange_keys]`, is such that only keys whose starting date is younger than `lookahead_provide` will be issued by the exchange. +++++++++++++ +Installation +++++++++++++ + +TBD + +++++ Other +++++ diff --git a/operate-merchant.rst b/operate-merchant.rst @@ -183,3 +183,9 @@ instance `Tor` as follows:: Please note that :ref:`Taler messagging<merchant-api>` is designed so that the merchant frontend can instruct the backend on which instance has to be used in the various operations. This information is optional, and if not given, the backend will act as the `default` instance. + +++++++++++++ +Installation +++++++++++++ + +TBD