public inbox for cryptsetup@lists.linux.dev
 help / color / mirror / Atom feed
From: Milan Broz <gmazyland@gmail.com>
To: Kfir Kahanov <kfirka3@gmail.com>, cryptsetup@lists.linux.dev
Cc: Vojtech Trefny <vtrefny@redhat.com>
Subject: Re: [PATCH 0/2] Bitlocker: Support clearkey
Date: Sat, 4 Oct 2025 20:17:44 +0200	[thread overview]
Message-ID: <61a493d0-0236-4508-aec9-b29ea6433244@gmail.com> (raw)
In-Reply-To: <20251004003554.234647-1-kfirka3@gmail.com>

On 10/4/25 2:35 AM, Kfir Kahanov wrote:
> This code enable support for clearkey bitlocker protection.
> Closes: #962

Hi,

as this is not trivial feature, please submit it through
merge request through GitLab project page.
You already have issue there, so it should not be a problem.

This way it can go through CI and all discussion and changes
will be there. Also it need to include some tests.

For the patch - we planned support for Bitlocker clearkey,
so it is definitely something that I would lite to merge.

However, I do not understand why you need to touch API
and other formats. The whole implementation should be embedded
in BITLK format support only.
IMO if Bitlocker header contains CLEARKEY, it should be used
directly. I know it will be a little bit tricky to support
it through existing calls, but I definitely do not want new activation
API call and commandline option for it.

Anyway, this discussion should happen on Gitlab, we can
discuss there possible options for integration.

Thanks!
Milan


> 
> 
> Kfir Kahanov (2):
>    bitlocker: Support clearkey
>    bitlocker: Add clearkey option
> 
>   lib/bitlk/bitlk.c         | 106 +++++++++++++++++++++++++-------------
>   lib/keyslot_context.c     |  97 ++++++++++++++++++++++++++++++++++
>   lib/keyslot_context.h     |   2 +
>   lib/libcryptsetup.h       |  24 +++++++++
>   lib/libcryptsetup.sym     |   1 +
>   lib/setup.c               |  24 ++++++++-
>   src/cryptsetup.c          |  20 ++++---
>   src/cryptsetup_arg_list.h |   2 +
>   src/cryptsetup_args.h     |   1 +
>   src/utils_arg_names.h     |   1 +
>   10 files changed, 234 insertions(+), 44 deletions(-)
> 


  parent reply	other threads:[~2025-10-04 18:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-04  0:35 [PATCH 0/2] Bitlocker: Support clearkey Kfir Kahanov
2025-10-04  0:35 ` [PATCH 1/2] bitlocker: " Kfir Kahanov
2025-10-04  0:35 ` [PATCH 2/2] bitlocker: Add clearkey option Kfir Kahanov
2025-10-04 18:17 ` Milan Broz [this message]
2025-10-04 19:28   ` [PATCH 0/2] Bitlocker: Support clearkey Kfir Ka
2025-10-04 19:46     ` Milan Broz

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=61a493d0-0236-4508-aec9-b29ea6433244@gmail.com \
    --to=gmazyland@gmail.com \
    --cc=cryptsetup@lists.linux.dev \
    --cc=kfirka3@gmail.com \
    --cc=vtrefny@redhat.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox