gnunet-svn
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[taler-anastasis] branch master updated: minor fixes


From: gnunet
Subject: [taler-anastasis] branch master updated: minor fixes
Date: Thu, 11 Jun 2020 16:00:23 +0200

This is an automated email from the git hooks/post-receive script.

ds-meister pushed a commit to branch master
in repository anastasis.

The following commit(s) were added to refs/heads/master by this push:
     new 473bc85  minor fixes
473bc85 is described below

commit 473bc85812417176e20a2b18fec33d545325ff86
Author: Dominik Meister <dominiksamuel.meister@students.bfh.ch>
AuthorDate: Thu Jun 11 16:00:17 2020 +0200

    minor fixes
---
 doc/thesis/implementation.tex         | 4 ++--
 doc/thesis/rest_api_documentation.tex | 4 ++--
 doc/thesis/server_architecture.tex    | 6 +++---
 3 files changed, 7 insertions(+), 7 deletions(-)

diff --git a/doc/thesis/implementation.tex b/doc/thesis/implementation.tex
index 25bd10f..b01c8bf 100644
--- a/doc/thesis/implementation.tex
+++ b/doc/thesis/implementation.tex
@@ -173,10 +173,10 @@ would first need to start the challenge with the request 
(GET
 /truth/\$TRUTH\_PUB). The server would then notify the user that per will
 receive some token out of bounds. After that, the user would have to
 provide for example the PIN sent to them via SMS with the same request
-as before (GET /truth/\$TRUTH\_PUB?resonse=\$RESPONSE).
+as before (GET /truth/\$TRUTH\_PUB?response=\$RESPONSE).
 
 
-\subsection{Client application command line interface (CLI)}
+\subsection{Client Application Command Line Interface (CLI)}
 
 There are two client applications which interact with the user. First
 the Anastasis {\em splitter} and second the Anastasis {\em
diff --git a/doc/thesis/rest_api_documentation.tex 
b/doc/thesis/rest_api_documentation.tex
index 3cd5eac..4d79d83 100644
--- a/doc/thesis/rest_api_documentation.tex
+++ b/doc/thesis/rest_api_documentation.tex
@@ -264,7 +264,7 @@ interface TruthUploadRequest {
   // encrypted_truth.
   nonce: [32]; //bytearray
 
-  // Signature over the key_share signed with TRUTH\_PRIV.
+  // Signature over the key_share signed with TRUTH_PRIV.
   key_share_signature: EddsaSignature;
 
   // Variable-size truth. After decryption,
@@ -276,7 +276,7 @@ interface TruthUploadRequest {
   // string "ECT".
   encrypted_authentication_data: []; //bytearray
   
-    // Signature over the key_share signed with TRUTH\_PRIV.
+    // Signature over the key_share signed with TRUTH_PRIV.
   authentication_data_signature: EddsaSignature;
   
   // mime type of truth, i.e. text/ascii, image/jpeg, etc.
diff --git a/doc/thesis/server_architecture.tex 
b/doc/thesis/server_architecture.tex
index 7641029..0680627 100644
--- a/doc/thesis/server_architecture.tex
+++ b/doc/thesis/server_architecture.tex
@@ -81,7 +81,7 @@ key recovery (via GET /truth/\$TRUTH\_PUB), providing a way 
to decrypt the
 truth with the phone number. The server will then generate a \$PIN and
 send it via an SMS provider to the stored number in the truth
 object. The client then must send another request with the sent \$PIN
-(via GET /truth/\$TRUTH\_PUB?resonse=\$PIN). The server can now check
+(via GET /truth/\$TRUTH\_PUB?response=\$PIN). The server can now check
 if the two PINs match. Upon success, the server returns the encrypted
 key share.
 
@@ -104,7 +104,7 @@ conference.  The video authentication provider then checks 
via video
 conference that the user in the image is the same that they have on
 the video link. Upon success, the video provider releases the \$TOKEN
 to the user.  The client then must send another request with the
-\$TOKEN (via GET /truth/\$TRUTH\_PUB?resonse=\$TOKEN). The Anastasis
+\$TOKEN (via GET /truth/\$TRUTH\_PUB?response=\$TOKEN). The Anastasis
 provider checks that the tokens match, and upon success returns the
 encrypted key share.
 
@@ -115,7 +115,7 @@ to authenticate using Post identification (GET 
/truth/\$TRUTH\_PUB).  The
 Anastasis provider uses the request to decrypt the user's truth to
 determine the user's postal address, and sends them letter containing
 a \$PIN.  Upon receiving the letter, the client then has to send
-another request with the \$PIN (GET /truth/\$TRUTH\_PUB?resonse=\$PIN). The
+another request with the \$PIN (GET /truth/\$TRUTH\_PUB?response=\$PIN). The
 server can now check if the two PINs match. Upon success the server
 will release the encrypted key share.
 

-- 
To stop receiving notification emails like this one, please contact
gnunet@gnunet.org.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]