archive mirror
 help / color / mirror / Atom feed
From: Chris Murphy <>
Subject: Bitlocker resize
Date: Tue, 15 Mar 2022 10:45:23 -0600	[thread overview]
Message-ID: <> (raw)


I'm curious how Linux distro installers should go about supporting the
increasingly common case of Bitlocker enabled by default.

Is the Bitlocker format similar to LUKS in that the ciphertext volume
size is inferred from the underlying partition size?

I see in bitlkDump results of a Bitlocker volume there's no apparent
reference to its size so I'm thinking it might be conceptually the
same as LUKS, in which case the installer workflow would be the same
as LUKS. I know that cryptsetup doesn't support modifying a Bitlocker
header, but maybe it's not necessary?

cryptsetup open /dev/ $name
ntfsresize --size $size /dev/mapper/$name
cryptsetup close $name
libfdisk/parted (resize the partition, create a new one in free space, etc)


Chris Murphy

             reply	other threads:[~2022-03-15 16:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-15 16:45 Chris Murphy [this message]
2022-03-15 17:19 ` Bitlocker resize Milan Broz
2022-03-23 18:10 ` Vojtech Trefny

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:

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

  git send-email \ \ \ \

* 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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).