From: Nikolaos Chatzikonstantinou <nchatz314@gmail.com>
To: grub-devel@gnu.org
Subject: State of Argon2 support
Date: Fri, 22 Dec 2023 12:29:22 -0500 [thread overview]
Message-ID: <CAAQmekeorYnAVfNrHrEVmZrmqpGix57=Zk+Vf5Oko5jm_OzuFg@mail.gmail.com> (raw)
Hello list,
I was wondering what the state of Argon2 support is. From some
searches online I found patches by Patrick Steinhardt that
experimentally add support for it.
I skimmed through the discussions on this list to understand what some
of the issues are:
1. Argon2 requires a lot of memory. How to allocate without breaking
backward-compat?
<https://lists.gnu.org/archive/html/grub-devel/2020-03/msg00180.html>
2. libgcrypt does not have support for Argon2. Possible solution is to
use the reference implementation, licensed under CC0. This is bringing
up issues (that I don't fully understand), would be preferable if the
authors released under GPLv3. Has there been a follow-up on this?
<https://lists.gnu.org/archive/html/grub-devel/2020-03/msg00170.html>
I don't know if there are more issues. I would appreciate some clarity
on this. If I can help in any way please let me know. Even if you'd
just like me to read the mailing lists and patches and describe a good
summary of the state of the issue, I can do it.
The interest in getting this done comes from the Guix System project
https://guix.gnu.org/>. In this distribution, the kernel lies under
/gnu/store and the usual (for me?) plain-boot encrypted-rest setup
cannot work unless using PBKDF.
Regards,
Nikolaos Chatzikonstantinou
_______________________________________________
Grub-devel mailing list
Grub-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/grub-devel
next reply other threads:[~2023-12-22 17:30 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-22 17:29 Nikolaos Chatzikonstantinou [this message]
2023-12-23 3:43 ` State of Argon2 support Oskari Pirhonen
2024-01-01 19:48 ` Patrick Steinhardt
2024-01-04 15:49 ` Nikolaos Chatzikonstantinou
2024-01-23 16:57 ` Daniel Kiper
2024-01-24 5:05 ` Nikolaos Chatzikonstantinou
2024-01-24 5:46 ` Nikolaos Chatzikonstantinou
2024-01-24 6:23 ` Nikolaos Chatzikonstantinou
2024-01-25 18:15 ` Daniel Kiper
2024-01-26 8:18 ` Nikolaos Chatzikonstantinou
2024-01-26 9:55 ` Patrick Steinhardt
2024-01-26 18:00 ` Daniel Kiper
2024-01-26 17:50 ` Daniel Kiper
2024-01-26 20:31 ` Vladimir 'phcoder' Serbinenko
2024-01-30 15:18 ` Nikolaos Chatzikonstantinou
2024-02-02 14:10 ` Daniel Kiper
2024-02-11 21:01 ` Nikolaos Chatzikonstantinou
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='CAAQmekeorYnAVfNrHrEVmZrmqpGix57=Zk+Vf5Oko5jm_OzuFg@mail.gmail.com' \
--to=nchatz314@gmail.com \
--cc=grub-devel@gnu.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).