[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[taler-anastasis] branch master updated: mod ypsomed draft
From: |
gnunet |
Subject: |
[taler-anastasis] branch master updated: mod ypsomed draft |
Date: |
Thu, 01 Oct 2020 16:09:33 +0200 |
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 d5ae369 mod ypsomed draft
d5ae369 is described below
commit d5ae369d2eb879a2d4fe81d7298a822b0b91e474
Author: Dennis Neufeld <dennis.neufeld@students.bfh.ch>
AuthorDate: Thu Oct 1 16:09:29 2020 +0200
mod ypsomed draft
---
doc/ypsomed/.gitignore | 10 ++++++++++
doc/ypsomed/plan.PNG | Bin 0 -> 145259 bytes
doc/ypsomed/ypsomed.tex | 29 ++++++++++++++++++-----------
3 files changed, 28 insertions(+), 11 deletions(-)
diff --git a/doc/ypsomed/.gitignore b/doc/ypsomed/.gitignore
new file mode 100644
index 0000000..2ba284f
--- /dev/null
+++ b/doc/ypsomed/.gitignore
@@ -0,0 +1,10 @@
+ypsomed.toc
+ypsomed.aux
+ypsomed.bbl
+ypsomed.bcf
+ypsomed.blg
+ypsomed.log
+ypsomed.pdf
+ypsomed.run.xml
+ypsomed.synctex.gz
+
diff --git a/doc/ypsomed/plan.PNG b/doc/ypsomed/plan.PNG
new file mode 100644
index 0000000..e62a028
Binary files /dev/null and b/doc/ypsomed/plan.PNG differ
diff --git a/doc/ypsomed/ypsomed.tex b/doc/ypsomed/ypsomed.tex
index 3b27176..c4c0624 100644
--- a/doc/ypsomed/ypsomed.tex
+++ b/doc/ypsomed/ypsomed.tex
@@ -100,7 +100,7 @@ application. It shows a simplified flow of the application.
The
details of each component are explained later.
\begin{center}
-\includegraphics[scale=0.4]{system_design.png}
+\includegraphics[scale=0.5]{system_design.png}
\end{center}
\begin{enumerate}
@@ -132,36 +132,41 @@ details of each component are explained later.
\subsection{Recovery and backup flow}
- Pingu Miau Katze Pingu Miau Katze Pingu Miau Katze Pingu Miau Katze Pingu
Miau Katze Pingu Miau Katze Pingu Miau Katze \\
+
\begin{center}
\includegraphics[scale=0.35]{step1.png}
\end{center}
- Pingu Miau Katze Pingu Miau Katze Pingu Miau Katze Pingu Miau Katze Pingu
Miau Katze Pingu Miau Katze Pingu Miau Katze \\
+During a backup process, the core secret is first split into several parts.
These parts are then each encrypted with the first key (K1). \\
\begin{center}
\includegraphics[scale=0.35]{step2.png}
\end{center}
- Pingu Miau Katze Pingu Miau Katze Pingu Miau Katze Pingu Miau Katzevv Pingu
Miau Katze Pingu Miau Katze Pingu Miau Katze\\
+Authentication data is then added to the encrypted parts (e.g. mobile phone
number for SMS authentication). The parts modified in this way are now
encrypted again, but this time with the second key (K2). \\
\begin{center}
\includegraphics[scale=0.35]{step3.png}
\end{center}
+ In the last step of the backup procedure the prepared parts are distributed
to the various provider servers.\\
- Pingu Miau Katze Pingu Miau Katze Pingu Miau Katze Pingu Miau Katze Pingu
Miau Katze Pingu Miau Katze Pingu Miau Katze Pingu \\
\begin{center}
\includegraphics[scale=0.35]{step1_recovery.png}
\end{center}
-
+In a recovery process the user must authenticate himself with the
corresponding providers using his stored authentication data. However, since
these providers cannot yet access the data, the user must send them the second
key (K2). This key enables them to read only the necessary data.\\
\begin{center}
\includegraphics[scale=0.35]{step2_recovery.png}
\end{center}
-
+If the user has authenticated himself correctly, he will receive the encrypted
parts of the core secrets from the respective providers. The user can decrypt
these parts with the first key (K1).\\
\begin{center}
\includegraphics[scale=0.3]{step3_recovery.png}
\end{center}
-
-Pingu Miau Katze Pingu Miau Katze Pingu Miau Katze Pingu Miau Katze Pingu Miau
Katze Pingu Miau Katze Pingu Miau Katze Pingu \\
+In the last step the user reassembles the decrypted parts of the core secret
into a whole.\\
\section{Team}
-Einleitung in die Team Mitglieder :)
+My name is Dominik Meister and I recently completed my Bachelor's degree in IT
Security.\\
+The design and implementation of Anastasis was the topic of my bachelor thesis.
+During the thesis I could successfully develop a proof of concept of the
software.
+I am responsible for the development of the backend and the deployment of the
software.\\
+
+Dennis Neufeld was my partner during the bachelor thesis. He also recently
completed his bachelor's degree in IT security.
+He is also a developer and is responsible for the integration of Anastasis
into other products.\\
@@ -186,7 +191,9 @@ Key milestones are the various integrations of the
different authentication meth
cryptographic consumer products, and the deployment of our application.
Additionally, we would always look out for new customers and clients who could
benefit from Anastasis.
-%Grafik Projektplan
+\begin{center}
+ \includegraphics[scale=0.34]{plan.png}
+\end{center}
\section{Business model}
--
To stop receiving notification emails like this one, please contact
gnunet@gnunet.org.
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [taler-anastasis] branch master updated: mod ypsomed draft,
gnunet <=