[taler-anastasis] branch master updated: count

[gnunet]

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

grothoff pushed a commit to branch master
in repository anastasis.

The following commit(s) were added to refs/heads/master by this push:
     new 10334d8  count
10334d8 is described below

commit 10334d869d81fcf1e61c8bcb32178d055fe2791e
Author: Christian Grothoff <christian@grothoff.org>
AuthorDate: Sun Jun 7 01:10:56 2020 +0200

    count
---
 doc/thesis/client_architecture.tex | 117 -------------------------------------
 doc/thesis/related_work.tex        |   2 +-
 doc/thesis/thesis.lof              |   8 +--
 3 files changed, 5 insertions(+), 122 deletions(-)

diff --git a/doc/thesis/client_architecture.tex 
b/doc/thesis/client_architecture.tex
index 1dce670..427d0fd 100644
--- a/doc/thesis/client_architecture.tex
+++ b/doc/thesis/client_architecture.tex
@@ -235,120 +235,3 @@ struct challenge
 The service API is responsible for sending the requests to the REST
 API of the server. The client has implemented functions for every end
 point. For more details see REST API documentation in the appendix.
-
-
-\subsection{Client Application CLI}
-
-There are two client applications which interact with the user. First the 
Anastasis splitter and second the Anastasis assembler. The splitter application 
is responsible for the backup of the core secret. The assembler is then 
responsible for the recovery of the secret. \\
- \\
-\textbf{Anastasis splitter} \\
- \\
-\textbf{Available commands: }
-\begin{itemize}
-\item server add \$URL : this command lets the user add escrow providers. The 
command will check if the server is available under the provided url. Afterwards
-it will download its terms and salt. The server needs to be added before the 
user can do any uploads on it.
-\item truth add \$server \$method \$truth : with this command the user can 
upload
-a truth on a previously added server. He needs to specify the method used and 
the
-truth for the method, for example the phone number or the question and the 
answer.
-The programm will check if the server supports the provided method before 
uploading.
-\item policy add \$truth1 \$truth2... : after the user has added all the 
truths he can start to create policies. He can combine the truths in any way he 
wishes. It is also possible to just store one truth in a policy, but this is 
not recommended since it defies the design of the application.
-\item policy : shows all created policies.
-\item truth : shows all created truths.
-\item server : shows all added servers.
-\item publish \$secret : if the user is finished he can publish the 
configuration. The application will then generate the recovery document with 
the provided information and secret. Afterwards it will upload the recovery 
document on every used server.
-\end{itemize}
-Below is an example flow of the application. \\
-\begin{lstlisting}
-//The user starts the programm and passes a json document
-//containing the unforgetable secret(name, social security number..)
-$ anastasis-splitter --me=identity.json
-anastasis-splitter> server add $URL1
-version: 1.0
-annual fee: EUR:4.99,
-available policy methods: sms
-Server #1 available
-anastasis-splitter> server add $URL2
-version: 1.0
-annual fee: EUR:3.99,
-available policy methods: sms, question
-Server #2 available
-anastasis-splitter> truth add server#1 sms +492452526
-Truth #1 added for server #1
-anastasis-splitter> truth add server#2 mail "hoehenweg 80, Biel"
-Sorry, server #2 does not support 'mail'
-anastasis-splitter> truth add question "favorite color" "red"
-Truth #2 added
-anastasis-splitter> policy add truth#1 truth#2
-Policy #1 defined
-anastasis-splitter> policy
-Policy#1: #truth#1 #truth2
-anastasis-splitter> truth
-truth#1: server#1 sms  +492452526
-truth#2: server#2 question "favorite color" <OMITTED>
-anastasis-splitter> truth --secrets
-truth#1: sms  +492452526
-truth#2: question "favorite color" "red"
-anastasis-splitter> server
-server#1: http://anastasis.example.com/ methods: sms,
-insured up to: 420 KUDOS, cost: 0.4 KUDOS
-anastasis-splitter> publish
-Server#1 failure: 402 payment required:
-payto://pay/ABALSASDFA KUDOS:0.3
-Server#2 failure: 402 payment required:
-payto://pay/ABALSAADAS KUDOS:0.5
-Total: 0.8 KUDOS
-# Here: taler-wallet-cli payto://pay/ABALASDFA used to pay!
-anastasis-splitter> publish
-Server#2 failure: 402 payment required
-# Here: taler-wallet-cli payto://pay/ABASDFASDF used to pay!
-anastasis-splitter> publish "my super secret"
-Thank you for using Anastasis.
-$
-\end{lstlisting}
-\textbf{Anastasis assembler} \\
- \\
-\textbf{Available commands:} \\
-\begin{itemize}
-\item truth : shows all available truths in the recovery document and its 
status
-( (-) not solved (+) solved )
-\item policies : shows all available policies in the recovery document and
-the respective status of the truths used in each policy.
-\item try \$truth : this command starts a truth which needs interaction with 
external services like sms or e-mail. It also shows the instructions to solve a 
truth.
-\item answer \$truth \$answer : this command tries to answer the selected 
truth with the provided answer. The application will check the answer and give 
a feedback to the user. Everytime a truth is solved, the client\_api will check 
if a policy is solved, if a policy was solved successfully the application will 
print out the recovered core secret.
-\end{itemize}
-Below is an example flow of the application. \\
-\begin{lstlisting}
-//The user starts the programm and passes a json document
-//containing the unforgetable secret(name, social security number..),
-//a url to a escrow provider which stores his recovery document and
-//the requested version of the recovery document. The client will then
-//download the recovery document within the startup
-$ anastasis-assembler --import https://anastasis.example.com/
---policy-version=42 --me=identity.json
-anastasis-assembler> truth
-truth#1(-): KUDOS 0.0 question "favorite color"
-truth#2(-): KUDOS 0.4 sms
-truth#3(-): KUDOS 2.6 post
-anastasis-assembler> policies
-policy#1: KUDOS 0.4 truth#1 truth#2 missing
-policy#2: KUDOS 3.0 truth#1 truth#2 truth#3 missing
-anastasis-assembler> try truth#2
-payto://pay/BASDFASD
-# SMS arrives asynchronously
-anastasis-assembler> answer truth#2 1234
-Success truth#2
-anastasis-assembler> answer truth#1 "blue"
-Failed truth#1
-anastasis-assembler> truth
-truth#1(-): KUDOS 0.0 question "favorite color"
-truth#2(+): KUDOS 0.4 sms
-truth#3(-): KUDOS 2.6 post
-anastasis-assembler> policies
-policy#1: KUDOS 0.0 truth#1 missing
-policy#2: KUDOS 2.6 truth#1 truth#3 missing
-anastasis-assembler> answer truth#2 "red"
-Success truth#2
-//One of the policies was solved successfully and the secret is recovered.
-Secret was: "my super secret"
-$
-\end{lstlisting}
diff --git a/doc/thesis/related_work.tex b/doc/thesis/related_work.tex
index a0e5da1..f40d156 100644
--- a/doc/thesis/related_work.tex
+++ b/doc/thesis/related_work.tex
@@ -470,7 +470,7 @@ decrypted''~\cite{midata}. (Emphasis ours.)
 
 The security of MIDATA as described in ``Patient empowerment in IoT
 for eHealth - How to deal with lost keys?''~\cite{midata} is broken in
-two ways:
+three ways:
 
 \begin{enumerate}
  \item The password is reconstructed at {\em the server}, not on the
diff --git a/doc/thesis/thesis.lof b/doc/thesis/thesis.lof
index ffdd1d0..18e5065 100644
--- a/doc/thesis/thesis.lof
+++ b/doc/thesis/thesis.lof
@@ -14,10 +14,10 @@
 \defcounter {refsection}{0}\relax 
 \contentsline {figure}{\numberline {6}{\ignorespaces Anastasis 
database}}{17}{figure.6}%
 \defcounter {refsection}{0}\relax 
-\contentsline {figure}{\numberline {7}{\ignorespaces Secret split 
process}}{32}{figure.7}%
+\contentsline {figure}{\numberline {7}{\ignorespaces Secret split 
process}}{29}{figure.7}%
 \defcounter {refsection}{0}\relax 
-\contentsline {figure}{\numberline {8}{\ignorespaces Secret split 
process}}{33}{figure.8}%
+\contentsline {figure}{\numberline {8}{\ignorespaces Secret split 
process}}{30}{figure.8}%
 \defcounter {refsection}{0}\relax 
-\contentsline {figure}{\numberline {9}{\ignorespaces Secret recovery 
process}}{35}{figure.9}%
+\contentsline {figure}{\numberline {9}{\ignorespaces Secret recovery 
process}}{32}{figure.9}%
 \defcounter {refsection}{0}\relax 
-\contentsline {figure}{\numberline {10}{\ignorespaces Business project 
plan}}{47}{figure.10}%
+\contentsline {figure}{\numberline {10}{\ignorespaces Business project 
plan}}{44}{figure.10}%

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