move the meat of what we have about multi-device into next-level back…

…up documentation
autocrypt · Dec 22, 2016 · fa03e7f · fa03e7f
1 parent 638ef51
commit fa03e7f
Show file tree

Hide file tree

Showing 3 changed files with 49 additions and 53 deletions.
diff --git a/doc/backup.rst b/doc/backup.rst
@@ -0,0 +1,39 @@
+Autocrypt Secret Key Backup
+===========================
+
+This is for Autocrypt Level 1 or later...
+
+The MUA generates a strong "backup code" and gets the user to write it
+down somewhere.  Then it serializes its secret key material into a
+message encrypted by the the backup code.  This message is given a
+custom header and is sent to the account in question::
+
+    Autocrypt-Secret-Key-Backup: key_backup_data=<encrypted_secret_key>
+    From: alice@example.net
+    To: alice@example.net
+
+.. todo::
+
+   should the MUA store the message in the SMA, or store it to file or
+   what?
+
+
+Restore
+-------
+
+.. todo::
+
+   Fill in here
+
+Prompting the user for backup code?
+
+Note also that the backup code MUST be strong -- it is subject to
+brute force attacks by anyone who holds a copy.
+
+Backup and Sync
+---------------
+
+
+.. todo::
+
+   say something about the relationship between backup and sync
diff --git a/doc/multi-device.rst b/doc/multi-device.rst
diff --git a/doc/next-steps.rst b/doc/next-steps.rst
@@ -53,3 +53,13 @@ RSA2048 to Curve 25519
 .. todo::
 
    Document change in preference for keys from RSA 2048 to Curve 25519.
+
+
+Backups
+-------
+
+see :doc:`backup`
+
+.. todo::
+
+   We need guidance on how backups might be done safely.