summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
author127.0.0.1 <127.0.0.1@web>2019-08-25 01:52:46 +0000
committerIkiWiki <ikiwiki.info>2019-08-25 01:52:46 +0000
commit506e2aa61f8762955fde1186a30df719c4b9e21e (patch)
tree9a32120860a88c22f4230b3f8e0581eae4098ea8
parentd00f40c753ddf48a490ca5f33c7995534d35f638 (diff)
This reverts commit 95513205740814aaaa439842d992e94280193c4a
-rw-r--r--wiki/src/blueprint/backups.mdwn11
1 files changed, 4 insertions, 7 deletions
diff --git a/wiki/src/blueprint/backups.mdwn b/wiki/src/blueprint/backups.mdwn
index 8b8c384..96cff5b 100644
--- a/wiki/src/blueprint/backups.mdwn
+++ b/wiki/src/blueprint/backups.mdwn
@@ -106,13 +106,10 @@ 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:
-
- * 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.
+ 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.
Update
------