gnunet-svn
[Top][All Lists]
Advanced

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

[taler-docs] branch master updated: Q/A in one place


From: gnunet
Subject: [taler-docs] branch master updated: Q/A in one place
Date: Mon, 26 Apr 2021 22:57:10 +0200

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

dold pushed a commit to branch master
in repository docs.

The following commit(s) were added to refs/heads/master by this push:
     new bd992fd  Q/A in one place
bd992fd is described below

commit bd992fda1275b841839f10deb177c6aa9d373825
Author: Florian Dold <florian@dold.me>
AuthorDate: Mon Apr 26 22:57:01 2021 +0200

    Q/A in one place
---
 design-documents/019-wallet-backup-merge.rst | 27 +++++++++++++--------------
 1 file changed, 13 insertions(+), 14 deletions(-)

diff --git a/design-documents/019-wallet-backup-merge.rst 
b/design-documents/019-wallet-backup-merge.rst
index a5ec9a6..373fdf4 100644
--- a/design-documents/019-wallet-backup-merge.rst
+++ b/design-documents/019-wallet-backup-merge.rst
@@ -30,20 +30,6 @@ backup account.  This happens when:
    In this scenario, the devices have the same device ID
    and the same wallet root public key.
 
-.. note::
-
-   Q: Why doesn't the wallet root public key get rotated every time
-   that a wallet backup is restored on a new device?
-
-   A: Because that would mean that old "paper backups" and Anastasis
-   backups stop working, because they are based on the wallet root key.
-
-   Q: Why can't the wallet obtain some unique devices identifier to exclude
-   case 3?
-
-   A: Because we don't have a reliable API for this on many platforms.
-   Even if we had one, we shouldn't rely on it.
-
 
 Requirements
 ============
@@ -152,3 +138,16 @@ Q / A
   * A:  If we deleted them immediately, this might cause data to be re-surface
     if a user temporarily removes and adds a backup account (say by accident)
     that hasn't been synced in a while.
+
+* Q: Why doesn't the wallet root public key get rotated every time
+  that a wallet backup is restored on a new device?
+
+  * A: Because that would mean that old "paper backups" and Anastasis
+    backups stop working, because they are based on the wallet root key.
+
+* Q: Why can't the wallet obtain some unique devices identifier to exclude
+  case 3 (same device ID, same wallet root pub)?
+
+  * A: Because we don't have a reliable API for this on many platforms.
+    Even if we had one, we shouldn't rely on it.
+

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