taler-docs

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

commit ebb171930ca227335a75abb8f634d6ea6c8bb0aa
parent 2fa2106532ce2f06702a9a1552bbbc197fb3ca6b
Author: Dennis Neufeld <dennis.neufeld@students.bfh.ch>
Date:   Thu, 10 Oct 2019 17:45:07 +0200

Modified anastasis db schema and corrected specification in truth api

Diffstat:
Manastasis-db.png | 0
Manastasis.rst | 2+-
2 files changed, 1 insertion(+), 1 deletion(-)

diff --git a/anastasis-db.png b/anastasis-db.png Binary files differ. diff --git a/anastasis.rst b/anastasis.rst @@ -657,7 +657,7 @@ charge per truth operation using GNU Taler. Upload a Truth-Object according to the policy the client created before (see RecoveryDocument_). If request has been seen before, the server should do nothing, and otherwise store the new object. - The body must begin with a nonce, an AES-GCM tag and continue with the ciphertext. In addition, + FIXME: The body must begin with the EncryptedKeyShare_ as binary block (see below). In addition, the name of the chosen key share method, the Base32-encoded ground truth and the MIME type of Truth must be included in the body. The Anastasis server cannot fully validate the format, but MAY impose