All of lore.kernel.org
 help / color / mirror / Atom feed
From: brutser@perso.be
To: grub-devel@gnu.org
Cc: dkiper@net-space.pl, development@efficientek.com, ps@pks.im
Subject: [PATCH v3 0/3] Cryptomount detached headers
Date: Fri, 29 Jul 2022 20:56:18 +0200 (CEST)	[thread overview]
Message-ID: <ea-mime-62e42d52-3d39-40e2decc@www.mailo.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 981 bytes --]


testing detached header failed:



1. built grub payload with following modules: ahci usb_keyboard part_msdos part_gpt at_keyboard cbfs cryptodisk luks2 lvm gcry_rijndael gcry_sha1 gcry_sha256 gcry_sha512

2. encrypt a partition: cryptsetup luksFormat --type luks2 -q -h sha512 -s 512 --pbkdf pbkdf2 --header /path/to/header --luks2-metadata-size=16k --luks2-keyslots-size=512k /dev/sda1

(where --luks2-metadata-size=16k --luks2-keyslots-size=512k is optional, this is just to minimize header size, but I also tested without).

3. from the grub cmd, i try to decrypt this partition using: cryptomount -H /path/to/header (ahci0,msdos1)



4. I also tried luks1 encryption with detached header.



whatever I try, I always get the same error:

"no cryptodisk module can handle this device"



Is this feature not 100% implemented yet, I saw people already verifying the patches and would expect this to be working, so if yes, this seems like a bug.




[-- Attachment #2: Type: text/html, Size: 1137 bytes --]

             reply	other threads:[~2022-07-29 18:56 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-29 18:56 brutser [this message]
2022-07-29 19:27 ` [PATCH v3 0/3] Cryptomount detached headers Glenn Washburn
2022-07-30  6:51 ` Maxim Fomin
2022-07-30  9:20   ` brutser
  -- strict thread matches above, loose matches on Subject: below --
2022-08-04 16:56 brutser
2022-08-05  5:00 ` Glenn Washburn
2022-08-05  9:43   ` brutser
2022-08-05 17:10     ` Glenn Washburn
2022-08-04 16:24 brutser
2022-08-03 23:54 brutser
2022-08-01 23:47 brutser
2022-08-02  0:26 ` brutser
2022-08-02 18:58   ` Glenn Washburn
2022-08-02 20:49     ` brutser
2022-08-03 19:54       ` Glenn Washburn
2022-08-03 22:26         ` brutser
2022-07-30  9:54 brutser
2022-07-30 18:48 ` brutser
2022-08-01 22:49   ` Glenn Washburn
2022-08-01 20:50 ` Glenn Washburn
2022-08-01 22:21   ` brutser
2022-08-01 23:24     ` Glenn Washburn
2022-07-29 20:01 brutser
2022-06-08 15:34 Glenn Washburn
2022-06-09 16:58 ` Daniel Kiper

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ea-mime-62e42d52-3d39-40e2decc@www.mailo.com \
    --to=brutser@perso.be \
    --cc=development@efficientek.com \
    --cc=dkiper@net-space.pl \
    --cc=grub-devel@gnu.org \
    --cc=ps@pks.im \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.