From: Milan Broz <gmazyland@gmail.com>
To: Phil Sutter <phil@nwl.cc>
Cc: dm-crypt@saout.de, Vojtech Trefny <vtrefny@redhat.com>
Subject: [dm-crypt] Re: [cryptsetup PATCH] Make BitLocker support optional
Date: Sat, 30 Oct 2021 12:06:08 +0200 [thread overview]
Message-ID: <595a3a55-67be-f3fe-23bc-e1d71855a8fe@gmail.com> (raw)
In-Reply-To: <20211029213117.GY1668@orbyte.nwl.cc>
On 29/10/2021 23:31, Phil Sutter wrote:
> Hi Milan,
>
> On Thu, Oct 28, 2021 at 09:14:10AM +0200, Milan Broz wrote:
>> Support for all formats is mandatory (the pain to support various kernel configuration is already enough),
>> so sorry, but I will not accept this patch.
>
> I can relate but in this case the default is enabled so unless someone
> really cares nothing changes.
All formats in libcryptsetup are intentionally always available.
This was my intention since the beginning I started to add external
format support (loopaes, truecrypt etc).
...
>> What issues this solves have here? Why you cannot link it?
>
> On an embedded device with uClibc I need libiconv which is 1.4MB in
> size. I was hoping to avoid having to ship this rather large library.
> While it's awesome that cryptsetup now supports bitlk partitions, I
> don't think it will see much use on embedded devices (e.g. a small file
> server).
So the whole problem is just to save 1.4M? I thought you cannot compile it at all.
Then this is not really something what I think is really important
- cryptsetup is not indented to be used in super-small embedded devices.
(But yes, we try to avoid big libraries dependences. But bitlk support is
mandatory function now.)
You can always add own patches obviously, it is OSS, but this is not going
to be merged upstream.
>> We use only some specific functions so the solution can be just to implement this internally.
>
> Converting passphrases to utf16 is mandatory for bitlk support, right?
Not only passphrases, labels etc are stored in utf16. But it is only small
subset of iconv we need.
> In general, I'm not sure if all this is feasible - libcryptsetup is
> already 1.9MB and maintaining a mini-iconv is error-prone and likely to
> remain mostly untested.
Systemd implements own utf functions (not sure why).
I would better add similar to libcryptsetup just for bitlk format (with unit test),
but not sure it is worth to spend time here... (IOW remove iconv dependence completely.)
(Anyway, cc to Vojta, who wrote this code.)
Milan
_______________________________________________
dm-crypt mailing list -- dm-crypt@saout.de
To unsubscribe send an email to dm-crypt-leave@saout.de
prev parent reply other threads:[~2021-10-30 10:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-27 23:29 [dm-crypt] [cryptsetup PATCH] Make BitLocker support optional Phil Sutter
2021-10-28 7:14 ` [dm-crypt] " Milan Broz
2021-10-29 21:31 ` Phil Sutter
2021-10-30 10:06 ` Milan Broz [this message]
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=595a3a55-67be-f3fe-23bc-e1d71855a8fe@gmail.com \
--to=gmazyland@gmail.com \
--cc=dm-crypt@saout.de \
--cc=phil@nwl.cc \
--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