[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
IS: GRUB release cycle: WAS: Re: [PATCH v3 3/5] argon2: Import Argon2 fr
From: |
Daniel Kiper |
Subject: |
IS: GRUB release cycle: WAS: Re: [PATCH v3 3/5] argon2: Import Argon2 from cryptsetup |
Date: |
Thu, 21 Jan 2021 15:49:27 +0100 |
User-agent: |
NeoMutt/20170113 (1.7.2) |
On Tue, Jan 19, 2021 at 08:31:03PM +0100, Petr Vorel wrote:
> Hi Patrick,
>
> > On Tue, Jan 19, 2021 at 02:06:15PM +0100, Petr Vorel wrote:
> > > Hi,
>
> > > > Please try to build only for the "efi-64" platform. (not "pc")
> > > right, I'll test it, but we need to support also legacy bios.
>
> > I wasn't aware it wouldn't build on the "pc" platform, but I never even
> > tried in the first place. The patch series definitely needs more
> > polishing anyway, but thanks for making me aware.
> Thanks!
> One more note: "Argon2 not supported" is not shown, instead there is
> "Invalid encryption" printed later in luks2_recover_key().
> It was trivial to modify sources to find it, but that will not be user
> friendly
> for users which will run grub2 from distro package.
>
> > > BTW as Argon2 is the default PBKDF algorithm in current cryptsetup, Debian
> > > installer (and probably other distros' installers) uses it and it has to
> > > be
> > > converted after installation with Live CD / connecting HDD on different
> > > machine.
>
> > > Therefore postponing Argon2 to another release means users will have it
> > > in 2+
> > > years after 2.06 release (unless distros backport it).
>
> > That cannot be helped, unfortunately. The current release has been
> > taking far too long already, and delaying it even further will
> > completely bar anybody from using LUKS2 with GRUB in the first place.
> Sure, understand.
>
> > I don't really know about the release cycle, but personally I wouldn't
> > mind to accelerate it. That's only my two cents though as somebody who
> > hasn't been involved in the project that deeply.
> +1 (that would allow to greatly reduce number of patches in distros, but
> understand the lack of maintainers time).
I hope we will be able to release 2.06 in 2-3 months. Now I am looking
at cutting rc1 shortly. Expect it in the following weeks.
Definitely I do not want to make current release cycle a norm. I am
going to work on improving it after 2.06 release. I think we will be
targeting something between 6-12 months.
Daniel
- Re: [PATCH v3 3/5] argon2: Import Argon2 from cryptsetup, Petr Vorel, 2021/01/18
- Re: [PATCH v3 3/5] argon2: Import Argon2 from cryptsetup, Dmitry, 2021/01/19
- Re: [PATCH v3 3/5] argon2: Import Argon2 from cryptsetup, Petr Vorel, 2021/01/19
- Re: [PATCH v3 3/5] argon2: Import Argon2 from cryptsetup, Matt Turner, 2021/01/19
- Re: [PATCH v3 3/5] argon2: Import Argon2 from cryptsetup, Patrick Steinhardt, 2021/01/19
- Re: [PATCH v3 3/5] argon2: Import Argon2 from cryptsetup, Petr Vorel, 2021/01/19
- IS: GRUB release cycle: WAS: Re: [PATCH v3 3/5] argon2: Import Argon2 from cryptsetup,
Daniel Kiper <=
- Re: IS: GRUB release cycle: WAS: Re: [PATCH v3 3/5] argon2: Import Argon2 from cryptsetup, Petr Vorel, 2021/01/21
- Re: IS: GRUB release cycle: WAS: Re: [PATCH v3 3/5] argon2: Import Argon2 from cryptsetup, Daniel Kiper, 2021/01/26
- Re: IS: GRUB release cycle: WAS: Re: [PATCH v3 3/5] argon2: Import Argon2 from cryptsetup, Petr Vorel, 2021/01/26