[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[taler-anastasis] branch master updated: nana suggestions
From: |
gnunet |
Subject: |
[taler-anastasis] branch master updated: nana suggestions |
Date: |
Mon, 27 Jan 2020 19:57:37 +0100 |
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 96838f6 nana suggestions
96838f6 is described below
commit 96838f630f87fbd8b0f8004f14e73311f9e41ffc
Author: Christian Grothoff <address@hidden>
AuthorDate: Mon Jan 27 19:57:35 2020 +0100
nana suggestions
---
doc/ledger.txt | 36 +++++++++++++++---------------------
1 file changed, 15 insertions(+), 21 deletions(-)
diff --git a/doc/ledger.txt b/doc/ledger.txt
index 976064d..02943ba 100644
--- a/doc/ledger.txt
+++ b/doc/ledger.txt
@@ -15,14 +15,13 @@ key material is split across multiple independent Anastasis
service
providers, and users are enabled to recover their master key by
authenticating with each provider.
-% NANA: be specific about 'in situations' => wallets, finance, OpenPGP
-In situations where users can remember sufficiently strong
-passphrases, key recovery is easily implemented by deriving the key
-from the secret passphrase. However, for many applications this
-strategy is insufficient. Our project was inspired by a discussion
-the GNU Taler team had with the European Central Bank, which informed
-them about a requirement for electronic wallets denominated in Euros
-to support password-less recovery.
+Users of OpenPGP or electronic wallets are frequently facing the
+challenge to secure their core secrets (private keys), and the
+contemporary default of asking them to remember strong passphrases is
+inadequate for mass adoption. Our project was inspired by a
+discussion the GNU Taler team had with the European Central Bank,
+which informed them about a requirement for electronic wallets
+denominated in Euros to support password-less recovery.
Our protocol ensures that - without prior knowledge- the service
providers learn nothing from the protocol except the minimum amount of
@@ -51,8 +50,6 @@ Challenge and Product / Service (1000 characters)
-- Problem product addresses, how we overcome, Value-add
-- core innovation
-NANA: more on the problem first?
-
Anastasis enables ordinary users to remain in control of their data --
including ensuring their data remains available to them --, even if
they cannot remember or securely store any sufficiently high-entropy
@@ -76,17 +73,14 @@ offered service.
Description of research component (500 characters)
-- relation to Distributed Data governnance / privacy by design
-NANA: simple => straightforward
-
-Secret splitting is a well-known technique for distributing
-trust. Given that the user is fully trusted, the Anastasis scenario is
-actually a straightforward form of secret splitting, as no distributed key
-generation is required. However, Anastasis would likely be the first
-secret splitting service to be offered to end-users. Thus ease of
-use and low operating costs are the real research challenges.
-
-NANA: reformulate on the research challenges, as never picked up later.
-NANA: will make proposal for formulation.
+Secret splitting is a well-known technique for distributing trust. For
+a fully trusted user, the Anastasis scenario is a straightforward form
+of secret splitting, as no distributed key generation is required. The
+protocol follows privacy-by-design. The research challenge lies in
+structuring and implementing Anastasis for it to become the first
+secret splitting service practical for end-users: Particularly, the UX
+(private user inputs) and minimization of operating costs are crucial
+here.
Technology description: (500 characters)
-- how does it work, architecture
--
To stop receiving notification emails like this one, please contact
address@hidden.
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [taler-anastasis] branch master updated: nana suggestions,
gnunet <=