[taler-anastasis] branch master updated: newpage

[gnunet]

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 943a336  newpage
943a336 is described below

commit 943a336cbc48e9ee862787d02ca32c12e0254062
Author: Dominik Meister <dominiksamuel.meister@students.bfh.ch>
AuthorDate: Thu Jun 11 16:07:59 2020 +0200

    newpage
---
 doc/thesis/client_architecture.tex | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/doc/thesis/client_architecture.tex 
b/doc/thesis/client_architecture.tex
index 73f5bd9..1fdc352 100644
--- a/doc/thesis/client_architecture.tex
+++ b/doc/thesis/client_architecture.tex
@@ -64,7 +64,7 @@ struct truth_key
 
 \item
 The truth\_seed is a randomly generated nonce with a size of 32 Bytes. It is 
used to derive a truth\_private\_key
-and is stored in the recovery document.
+and is stored within an encrypted recovery document.
 \begin{lstlisting}
 struct truth_seed
 {
@@ -119,7 +119,7 @@ struct key_share
 \end{lstlisting}
 
 \item
-Before every encryption a random 256-bit large nonce is generated. This gives 
the encryption algorithm a random factor.
+Before every encryption a random 256-bit large nonce is generated. This gives 
the encrpytion algorithm a random factor.
 \begin{lstlisting}
 struct nonce
 {
@@ -235,7 +235,7 @@ It is used as entropy source to generate the TRUTH\_PUB, 
which later identificat
 \item encrypted\_truth: the encrypted truth holds the authentication specific 
data. It holds for example the hashed answer and the question. It is encrypted 
with the specific truth\_key which is stored inside the recovery\_document.
 \item encrypted\_key\_share: this is the key\_share protected by this truth. 
It is encrypted with a key which was derived with the kdf\_id of the user. The 
server will later send this key\_share to the user upon successful 
authentication.
 \end{itemize}
-
+\newpage
 \item
 The policy data structure is used to create new policies to combine them into 
the recovery document. The policy data structure is only used for the secret 
share process.
 \begin{lstlisting}
@@ -267,7 +267,7 @@ struct decryption_policy
 \item encrypted\_master\_key: holds an encrypted version of the master\_key 
which was used to encrypt the core secret. In every policy lies the same 
master\_key which was encrypted by the specific policy\_key.
 \item salt: defines the salt which was used to create this policy\_key.
 \end{itemize}
-
+\newpage
 \item
 The challenge data structure is used for the several key\_share lookups.
 We named the process of authentication on the providers as challenges.

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