summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorChristian Grothoff <christian@grothoff.org>2017-12-14 13:49:24 +0100
committerChristian Grothoff <christian@grothoff.org>2017-12-14 13:49:24 +0100
commit1897d65af506f083d8296e6184c9633d0fb5bae0 (patch)
tree1cd759568689c450e0147d992d45a138211d3389 /doc
parentf7c9de73e197b6cc6308ad3322f4a75dfe2f33b5 (diff)
downloadexchange-1897d65af506f083d8296e6184c9633d0fb5bae0.tar.gz
exchange-1897d65af506f083d8296e6184c9633d0fb5bae0.tar.bz2
exchange-1897d65af506f083d8296e6184c9633d0fb5bae0.zip
eliminate /admin/add/incoming (fixes #5172)
Diffstat (limited to 'doc')
-rw-r--r--doc/taler-exchange.texi17
1 files changed, 5 insertions, 12 deletions
diff --git a/doc/taler-exchange.texi b/doc/taler-exchange.texi
index 558a57ef..e354b58c 100644
--- a/doc/taler-exchange.texi
+++ b/doc/taler-exchange.texi
@@ -400,13 +400,10 @@ gap. See keys-duration.
@section Serving
-The exchange can serve HTTP over both TCP and UNIX domain socket. It
-needs this configuration @emph{twice}, because it opens one connection
-for ordinary REST calls, and one for "/admin" and "/test" REST calls,
-because the operator may want to restrict the access to "/admin".
+The exchange can serve HTTP over both TCP and UNIX domain socket.
-The following values are to be configured under the section
-@cite{[exchange]} and @cite{[exchange-admin]}:
+The following values are to be configured in the section
+@cite{[exchange]}:
@itemize
@@ -425,13 +422,9 @@ The following values are to be configured under the section
@item
@cite{unixpath_mode}: number giving the mode with the access
-permissiON MASK for the @cite{unixpath} (i.e. 660 = rw-rw----).
+permission MASK for the @cite{unixpath} (i.e. 660 = rw-rw----).
@end itemize
-The exchange can be started with the @cite{-D} option to disable the administrative
-functions entirely. It is recommended that the administrative API is only
-accessible via a properly protected UNIX domain socket.
-
@node Currency
@section Currency
@@ -673,7 +666,7 @@ get signed by every auditor he wishes (or is forced to) work with.
In a normal scenario, an auditor must have some way of receiving the blob to
sign (Website, manual delivery, ..). Nonetheless, the exchange admin can fake
-an auditor signature - for testing purposes - by running the following command
+an auditor signature --- for testing purposes --- by running the following command
@example
taler-auditor-sign -m EXCHANGE_MASTER_PUB -r BLOB -u AUDITOR_URI -o OUTPUT_FILE