Skip to content

Commit 0a872bd

Browse files
gotthardpidesai
authored andcommitted
Remove a dead cryptsetup reference
The referenced activity was abandoned in favour of a systemd-based solution. See https://gitlab.com/cryptsetup/cryptsetup/-/merge_requests/51 https://gitlab.com/cryptsetup/cryptsetup/-/merge_requests/98 Fixes: #70 Signed-off-by: Petr Gotthard <petr.gotthard@advantech.cz>
1 parent b21af36 commit 0a872bd

1 file changed

Lines changed: 0 additions & 7 deletions

File tree

_posts/2020-04-13-Disk-Encryption.md

Lines changed: 0 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -217,13 +217,6 @@ Solution:<br>
217217
a. Seal the secret into a TPM device.<br>
218218
b. Unseal the secret in memory and pass it to cryptsetup.<br>
219219

220-
Please note that there is an upstreaming effort in the cryptsetup
221-
[feature-branch](https://gitlab.com/cryptsetup/cryptsetup/-/tree/wip-tpm) to
222-
enable tpm2 as a key protector built natively in to libcryptsetup as well as
223-
cryptsetup. It does so by adding a new keyslot-handler internally and extending
224-
the libcryptsetup API. In this tutorial however, we will be using tpm2-tools
225-
with cryptsetup that does not have built-in tpm2 support.<br>
226-
227220
Let's start with creating and persisting a sealing object and sealing a random
228221
byte sequence as the disk key.<br>
229222
26. `tpm2_createprimary -Q -C o -c prim.ctx`<br>

0 commit comments

Comments
 (0)