[taler-anastasis] branch master updated: Added explaination of keys illustration

[gnunet]

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

dennis-neufeld pushed a commit to branch master
in repository anastasis.

The following commit(s) were added to refs/heads/master by this push:
     new 6988dc6  Added explaination of keys illustration
6988dc6 is described below

commit 6988dc6fdb901a8e7a26f5425666d942232f1ae4
Author: Dennis Neufeld <dennis.neufeld@students.bfh.ch>
AuthorDate: Tue Jun 9 12:47:52 2020 +0000

    Added explaination of keys illustration
---
 doc/thesis/design.tex | 30 +++++++++++++++++++++++-------
 1 file changed, 23 insertions(+), 7 deletions(-)

diff --git a/doc/thesis/design.tex b/doc/thesis/design.tex
index 21a851d..d458c52 100644
--- a/doc/thesis/design.tex
+++ b/doc/thesis/design.tex
@@ -37,14 +37,30 @@ in which way they are used. The 
figure~\ref{fig:legend_keys_anastasis} on page~\
        \label{fig:legend_keys_anastasis}
 \end{figure}
 
-In the following the keys shown in the figure are explained:
+\noindent In the following the keys shown in the 
figure~\ref{fig:keys_anastasis} on 
+page~\pageref{fig:keys_anastasis} are explained:
 \begin{description}
-       \item[identity key] {}
-       \item[private account key] {}
-       \item[public account key] {}
-       \item[symmetric key 1] {}
-       \item[symmetric key 2] {}
-       \item[truth key] {}
+       \item[identity key] {The {\em identity key} is derived from the user 
attributes and a
+       randomly generated server salt provided by the escrow provider using 
Argon2. It is used to derive 
+       the {\em private account key}, the {\em symmetric key 1} and the {\em 
symmetric key 2} from.}
+       \item[private account key] {The {\em private account key} is used to 
sign the {\em encrypted
+       recovery document}. It is derived from the {\em identity key} using 
{\em HKDF-1}}.
+       \item[public account key] {The {\em public account key} is derived from 
its corresponding
+       {\em private account key}. It used to verify the signature of the {\em 
encrypted recovery 
+       document} and also is the identifier of the user which is needed by the 
provider.}
+       \item[symmetric key 1] {The {\em symmetric key 1} is derived from the 
{\em identity key} using
+       {\em HKDF-2}. It is used to encrypt and decrypt the {\em encrypted 
recovery document} which is stored by
+       the provider.}
+       \item[symmetric key 2] {The {\em symmetric key 2} is derived from the 
{\em identity key} using
+       {\em HKDF-3}. It is used to encrypt and decrypt the different {\em 
encrypted key shares} which 
+       are stored at the providers server.}
+       \item[truth key] {The {\em truth key} is randomly generated for each 
{\em encrypted authentication data} 
+       and is stored within the {\em encrypted recovery document}. It must be 
provided by the user to let the
+       server decrypt the {\em encrypted authentication data} for 
authentication purposes.} 
+       \item[master key] {The {\em master key} is randomly generated and is 
used to encrypt and decrypt the
+       {\em encrypted core secret} which is stored within an {\em encrypted 
recovery document}. The {\em encrypted master key} also is stored within the 
{\em encrypted recovery document}.}
+       \item[policy key] {The {\em policy keys} are used for encryption and 
decryption of the {\em encrypted master key}. A {\em policy key} is constructed 
by hashing a specific combination of {\em key shares} specified by the
+       user. For hashing SHA512 is used here.} 
 \end{description}
 
 \subsection{Adversary model}

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