Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: yann.morin@orange.com
To: James Hilliard <james.hilliard1@gmail.com>
Cc: <buildroot@buildroot.org>,
	Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
	Thomas Perale <thomas.perale@mind.be>,
	Ricardo Martincoski <ricardo.martincoski@datacom.com.br>
Subject: Re: [Buildroot] [PATCH v2 1/3] support/download: add blake2b-256 hash support
Date: Thu, 18 Jun 2026 07:51:53 +0200	[thread overview]
Message-ID: <ajOHeaIobPebbK+f@yd-6wlzhs3> (raw)
In-Reply-To: <20260617174208.3968183-1-james.hilliard1@gmail.com>

James, All,

On 2026-06-17 11:42 -0600, James Hilliard spake thusly:
[--SNIP--]
> Teach the download hash checker to validate blake2b-256 entries using
> b2sum -l 256, and update check-package so the new hash type and length
> are accepted. Also add the CycloneDX hash spelling so generated SBOMs
> can include blake2b-256 hashes from .hash files.
[--SNIP--]
> +    if [ "${_h}" = "blake2b-256" ]; then
> +        _hash="$( b2sum -l 256 "${_file}" |cut -d ' ' -f 1 )"

b2sum was only introduced with coreutils 8.26, but we support running on
systems that have an older version: we already check that ln supports
--relative (introduced in 8.16) and that realpath exists (introduced in
8.15).

So, we probably want to add b2sum to the list of tools to check in
support/dependencies/check-host-coreutils.s and then add
$(BR2_COREUTILS_HOST_DEPENDENCY) to the dependencies of packages that
have a blake2 hash (the python infra can do so, for example).

Regards,
Yann E. MORIN.

-- 
                                        ____________
.-----------------.--------------------:       _    :------------------.
|  Yann E. MORIN  | Real-Time Embedded |    __/ )   | /"\ ASCII RIBBON |
|                 | Software  Designer |  _/ - /'   | \ / CAMPAIGN     |
| +33 638.411.245 '--------------------: (_    `--, |  X  AGAINST      |
| yann.morin (at) orange.com           |_="    ,--' | / \ HTML MAIL    |
'--------------------------------------:______/_____:------------------'

____________________________________________________________________________________________________________
Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  parent reply	other threads:[~2026-06-18  5:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-17 17:42 [Buildroot] [PATCH v2 1/3] support/download: add blake2b-256 hash support James Hilliard
2026-06-17 17:42 ` [Buildroot] [PATCH v2 2/3] package/pkg-python: derive PyPI site from blake2b-256 hash James Hilliard
2026-06-17 17:42 ` [Buildroot] [PATCH v2 3/3] package/python-async-timeout: use hash-based PyPI site James Hilliard
2026-06-18  5:51 ` yann.morin [this message]
2026-06-18 14:04   ` [Buildroot] minimum system/coreutils requirements (was: support/download: add blake2b-256 hash support) Marcus Hoffmann via buildroot
2026-06-18 14:27     ` [Buildroot] minimum system/coreutils requirements Peter Korsgaard
2026-06-18 14:59     ` [Buildroot] minimum system/coreutils requirements (was: support/download: add blake2b-256 hash support) yann.morin

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=ajOHeaIobPebbK+f@yd-6wlzhs3 \
    --to=yann.morin@orange.com \
    --cc=buildroot@buildroot.org \
    --cc=james.hilliard1@gmail.com \
    --cc=ricardo.martincoski@datacom.com.br \
    --cc=thomas.perale@mind.be \
    --cc=thomas.petazzoni@bootlin.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