summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorintrigeri <intrigeri@boum.org>2019-08-25 05:01:45 +0000
committerintrigeri <intrigeri@boum.org>2019-08-25 05:01:45 +0000
commitbdca8778476df98d35611fbec487b916f9e23f28 (patch)
tree3260838a85f8227eb7f34a770c3d595f446f2aea
parent506e2aa61f8762955fde1186a30df719c4b9e21e (diff)
Revert spam.
This reverts commit 506e2aa61f8762955fde1186a30df719c4b9e21e.
-rw-r--r--wiki/src/blueprint/backups.mdwn11
1 files changed, 7 insertions, 4 deletions
diff --git a/wiki/src/blueprint/backups.mdwn b/wiki/src/blueprint/backups.mdwn
index 96cff5b..8b8c384 100644
--- a/wiki/src/blueprint/backups.mdwn
+++ b/wiki/src/blueprint/backups.mdwn
@@ -106,10 +106,13 @@ Implementation note:
- It might be possible to reuse the same LUKS header to create the
backup Persistence without prompting for a passphrase.
- At first glance, cryptsetup luksHeaderBackup/luksHeaderRestore should
- work to create that backups LUKS volume; and then, to unlock it, one
- could dump the master key from memory and pass it to cryptsetup open
- --master-key-file.
+ At first glance:
+
+ * To create the backup Persistence,
+ <span class="command">cryptsetup luksHeaderBackup/luksHeaderRestore</span> should work.
+ * To unlock the backup Persistence,
+ <span class="command">sudo dmsetup table --showkeys TailsData_unlocked</span> should dump the master key from memory and
+ <span class="command">cryptsetup --master-key-file</span> should unlock with the master key.
Update
------