Re: Kdump with full-disk LUKS encryption

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, 2021-04-19 at 18:24 +0100, Daniel P. Berrangé wrote:
> On Mon, Apr 19, 2021 at 01:12:07PM -0400, Simo Sorce wrote:
> > On Mon, 2021-04-19 at 12:02 +0100, Richard W.M. Jones wrote:
> > > On Mon, Apr 19, 2021 at 06:00:38PM +0800, Kairui Song wrote:
> > > > 2. LUKS2 prefers Argon2 as the key derivation function, designed to
> > > > use a lot of memory. kdump is expected to use a minimal amount of
> > > > memory. Users will have to reserve a huge amount of memory for kdump
> > > > to work (eg. 1G reserve for kdump with 4G total memory which is not
> > > > reasonable).
> > > 
> > > I'm just going to sympathise with you rather than provide a good
> > > answer here ...  We had the same problem in libguestfs where Argon2
> > > used too much memory for our small appliance when opening LUKS2 disks.
> > > We had to simply increase the amount of memory reserved, which is far
> > > from ideal.
> > 
> > Or you could switch to use PBKDF2, it is still a supported and
> > reasonable option.
> 
> libguestfs has to open whatever disk image the user gives it, and whoever
> built the image originally decided whether it uses Argon2 or PBKDF2.

My bad, I thought you were creating new partitions. Yeah argon2 has
that "problem". In theory there is a tradeoff between memory vs CPU
power, but it seem our implementation decided to go for memory and not
give the option to use the more time consuming but less memory hungry
algorithm.

Simo.

> Regards,
> Daniel
> -- 
> > : https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
> > : https://libvirt.org         -o-            https://fstop138.berrange.com :|
> > : https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|
> _______________________________________________
> devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
> To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
> Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
> Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure

-- 
Simo Sorce
RHEL Crypto Team
Red Hat, Inc



_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux