From: Matt Turner <mattst88@gentoo.org>
To: gentoo-catalyst@lists.gentoo.org
Subject: Re: [gentoo-catalyst] [PATCH 1/5] targets: Drop SHA512 isoroot verification support
Date: Wed, 8 Apr 2020 10:51:41 -0700 [thread overview]
Message-ID: <CAEdQ38HbYOLpRdW0J2GYC0Kho5DO7SQnXp_bvTrNwT_eG+q3_Q@mail.gmail.com> (raw)
In-Reply-To: <20200408091330.73b6ebf1@professor-x>
On Wed, Apr 8, 2020 at 9:13 AM Brian Dolbec <dolsen@gentoo.org> wrote:
> I know I've been out of touch for almost the last year, but why remove
> sha512? the current code it is optional for either of the two or both.
>
> What is gentoo now supplying primarily?
>
> If any change is to be made, I think it should be made as a plugin so
> the base code doesn't need to be changed as things change to the
> checksum of the day...
releng.git does not use this functionality at all -- it was added by
Rick for Pentoo, and Pentoo is now using only blake2.
I'd like to remove it because catalyst is already a monstrosity of
unnecessary and unused functionality.
I'm happy to just fork catalyst if others want it to remain this way.
next prev parent reply other threads:[~2020-04-08 17:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-08 3:27 [gentoo-catalyst] [PATCH 1/5] targets: Drop SHA512 isoroot verification support Matt Turner
2020-04-08 3:27 ` [gentoo-catalyst] [PATCH 2/5] targets: Simplify isoroot_checksum() Matt Turner
2020-04-08 3:27 ` [gentoo-catalyst] [PATCH 3/5] targets: Move isoroot verify check into isoroot_checksum() Matt Turner
2020-04-08 3:27 ` [gentoo-catalyst] [PATCH 4/5] targets: Support isoroot checksum on more platforms Matt Turner
2020-04-08 3:27 ` [gentoo-catalyst] [PATCH 5/5] targets: Use GRUB for BIOS boot Matt Turner
2020-04-08 16:13 ` [gentoo-catalyst] [PATCH 1/5] targets: Drop SHA512 isoroot verification support Brian Dolbec
2020-04-08 17:51 ` Matt Turner [this message]
2020-04-08 18:40 ` Brian Dolbec
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=CAEdQ38HbYOLpRdW0J2GYC0Kho5DO7SQnXp_bvTrNwT_eG+q3_Q@mail.gmail.com \
--to=mattst88@gentoo.org \
--cc=gentoo-catalyst@lists.gentoo.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