[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[taler-docs] branch master updated: clarify CodeBlau op sec question
From: |
gnunet |
Subject: |
[taler-docs] branch master updated: clarify CodeBlau op sec question |
Date: |
Fri, 19 Jun 2020 12:13:13 +0200 |
This is an automated email from the git hooks/post-receive script.
grothoff pushed a commit to branch master
in repository docs.
The following commit(s) were added to refs/heads/master by this push:
new 8a27f02 clarify CodeBlau op sec question
8a27f02 is described below
commit 8a27f027a2ffe42b1ebb4c29aae1dccdcf362cf9
Author: Christian Grothoff <christian@grothoff.org>
AuthorDate: Fri Jun 19 12:13:11 2020 +0200
clarify CodeBlau op sec question
---
taler-auditor-manual.rst | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/taler-auditor-manual.rst b/taler-auditor-manual.rst
index 82b206e..f5cca27 100644
--- a/taler-auditor-manual.rst
+++ b/taler-auditor-manual.rst
@@ -59,7 +59,11 @@ to other parties.
To perform this duty, you will need at least (read-only) access to the bank
transactions of the exchange, as well as a continuously synchronized replica
-of the exchange's database.
+of the exchange's database. The general assumption for running the auditor
+is that this is done on a separate system controlled by the auditor. After
+all, the goal is to detect nerfarious activity of the exchange operator,
+which cannot be effectively done on a machine controlled by the exchange
+operator.
For this, every auditor needs to operate a Postgres database. The data
collected will include sensitive information about Taler users, including
--
To stop receiving notification emails like this one, please contact
gnunet@gnunet.org.
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [taler-docs] branch master updated: clarify CodeBlau op sec question,
gnunet <=