gnunet-svn
[Top][All Lists]
Advanced

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

[taler-anastasis] branch master updated: Abstract before ToC


From: gnunet
Subject: [taler-anastasis] branch master updated: Abstract before ToC
Date: Thu, 28 May 2020 22:48:03 +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 98f311b  Abstract before ToC
98f311b is described below

commit 98f311bd98c278a60b6a58c035dbc86cbb9592db
Author: Dennis Neufeld <dennis.neufeld@students.bfh.ch>
AuthorDate: Thu May 28 20:47:37 2020 +0000

    Abstract before ToC
---
 doc/thesis/abstract.tex | 31 ++++++++++++++++---------------
 doc/thesis/thesis.tex   |  6 ++++--
 2 files changed, 20 insertions(+), 17 deletions(-)

diff --git a/doc/thesis/abstract.tex b/doc/thesis/abstract.tex
index 8f6ba3c..e2cead6 100644
--- a/doc/thesis/abstract.tex
+++ b/doc/thesis/abstract.tex
@@ -1,15 +1,16 @@
-\section{Abstract}
-Everyone has probably noticed at least once through the media that someone has 
lost their key to their electronic wallet and therefore huge sums of money have 
become useless. Therefore, backup systems are essential to avoid such cases.\\
-
-But how should one create and manage such a backup of a key? It certainly 
makes no sense to encrypt a key with a different password and then use the 
result as a backup. After all, this password can also be forgotten. Apart from 
that, the question arises how or where to save such a backup. A simple storage 
on e.g. Google Drive bears several risks: On the one hand, we are talking about 
Google, a company that is known to cooperate with certain authorities, and on 
the other hand, the cloud s [...]
-Unfortunately, to the best of our knowledge, there is no backup solution for 
keys that works password-less while giving the user complete control over his 
data.\\
-
-With Anastasis this gap shall be filled and a solution for secure recovery of 
secret keys, which works without passwords or other key material, shall be 
offered. This is achieved by splitting the
-key material across multiple independent Anastasis service
-providers, and enabling users to recover their master key by
-authenticating with each provider.\\
-
-Our protocol ensures that - without prior knowledge- the service
-providers learn nothing from the protocol except the minimum amount of
-data required to authenticate the user. Even that information is only
-disclosed at the time of authentication.
+\begin{abstract}
+       Everyone has probably noticed at least once through the media that 
someone has lost their key to their electronic wallet and therefore huge sums 
of money have become useless. Therefore, backup systems are essential to avoid 
such cases.\\
+       
+       But how should one create and manage such a backup of a key? It 
certainly makes no sense to encrypt a key with a different password and then 
use the result as a backup. After all, this password can also be forgotten. 
Apart from that, the question arises how or where to save such a backup. A 
simple storage on e.g. Google Drive bears several risks: On the one hand, we 
are talking about Google, a company that is known to cooperate with certain 
authorities, and on the other hand, the cloud  [...]
+       Unfortunately, to the best of our knowledge, there is no backup 
solution for keys that works password-less while giving the user complete 
control over his data.\\
+       
+       With Anastasis this gap shall be filled and a solution for secure 
recovery of secret keys, which works without passwords or other key material, 
shall be offered. This is achieved by splitting the
+       key material across multiple independent Anastasis service
+       providers, and enabling users to recover their master key by
+       authenticating with each provider.\\
+       
+       Our protocol ensures that - without prior knowledge- the service
+       providers learn nothing from the protocol except the minimum amount of
+       data required to authenticate the user. Even that information is only
+       disclosed at the time of authentication.
+\end{abstract}
\ No newline at end of file
diff --git a/doc/thesis/thesis.tex b/doc/thesis/thesis.tex
index 70bf7c1..50bc228 100644
--- a/doc/thesis/thesis.tex
+++ b/doc/thesis/thesis.tex
@@ -18,6 +18,7 @@
 \usepackage[backend=biber, style=ieee]{biblatex}
 \addbibresource{bibliothek.bib}
 
+\usepackage{abstract}
 \usepackage{graphicx}
 \usepackage{listings}
 \lstset{language=C,
@@ -33,11 +34,12 @@
 \author{Dominik Meister (\texttt{dominiksamuel.meister@students.bfh.ch}) \\
   Dennis Neufeld (\texttt{dennis.neufeld@students.bfh.ch })}
 \maketitle
-\tableofcontents
-\clearpage
 
 \include{abstract}
 
+\tableofcontents
+\clearpage
+
 \include{motivation}
 
 \include{project_management}

-- 
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]