From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: buildroot@buildroot.org
Cc: "Yann E . MORIN" <yann.morin.1998@free.fr>,
"Martin Zeiser \(mzeiser\)" <mzeiser@cisco.com>
Subject: [Buildroot] [PATCH 0/4] support/download: accept user-provided list of extra hash files (branch yem/multi-hash)
Date: Sat, 28 Oct 2023 23:09:04 +0200 [thread overview]
Message-ID: <cover.1698527340.git.yann.morin.1998@free.fr> (raw)
Hello All!
For packages where the version can be specified by the user (e.g. with a
custom version string, a custom tarball location, a custom git tree and
changeset...), Buildroot can't carry hashes for those, and thus does not
check the integritiy of the downloads.
Add the possibility for users to provide hashes for those, by leveraging
the global patch dir setting, to look up extra hash files in a way
similar to how extra patches are looked up in there.
Users who provide such extra hashes will most probably be interested in
ensuring that no download ever gets used without an actual integrity
check, so also add an option the requires all downloads to have at least
one valid hash (and no invalid ones, of course), rather than ignoring
downloads for custom versions.
Regards,
Yann E. MORIN.
----------------------------------------------------------------
Yann E. MORIN (4):
docs/manual: svn downloads can be hash-checked
support/download: teach dl-wrapper to handle more than one hash file
package/pkg-download: lookup hash files in global-patch-dir
pkg-download: add option to enforce hash checking
Config.in | 30 ++++++++++++--
docs/manual/adding-packages-directory.adoc | 12 ++++--
docs/manual/customize-patches.adoc | 25 +++++++++++-
package/pkg-download.mk | 15 +++++--
support/download/check-hash | 64 ++++++++++++++++--------------
support/download/dl-wrapper | 10 ++---
6 files changed, 110 insertions(+), 46 deletions(-)
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2023-10-28 21:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-28 21:09 Yann E. MORIN [this message]
2023-10-28 21:09 ` [Buildroot] [PATCH 1/4] docs/manual: svn downloads can be hash-checked Yann E. MORIN
2023-11-05 20:41 ` Peter Korsgaard
2023-11-09 17:22 ` Peter Korsgaard
2023-10-28 21:09 ` [Buildroot] [PATCH 2/4] support/download: teach dl-wrapper to handle more than one hash file Yann E. MORIN
2023-11-06 9:33 ` Peter Korsgaard
2023-11-06 17:41 ` Peter Korsgaard
2023-10-28 21:09 ` [Buildroot] [PATCH 3/4] package/pkg-download: lookup hash files in global-patch-dir Yann E. MORIN
2023-10-28 21:09 ` [Buildroot] [PATCH 4/4] pkg-download: add option to enforce hash checking Yann E. 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=cover.1698527340.git.yann.morin.1998@free.fr \
--to=yann.morin.1998@free.fr \
--cc=buildroot@buildroot.org \
--cc=mzeiser@cisco.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.