All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] Verifying linux 5.4.x hashes
Date: Fri, 28 May 2021 21:59:24 +0200	[thread overview]
Message-ID: <7e2d0cc4-892e-177e-0e9c-935dfbea0c46@mind.be> (raw)
In-Reply-To: <BN8PR11MB366618492FB8C57A78D7752BFF229@BN8PR11MB3666.namprd11.prod.outlook.com>



On 28/05/2021 19:15, Ian Merin via buildroot wrote:
> Hello, -- question about verifying linux kernel hashes.? I see in the linux.hash
> file there is an entry for the latest 5.4.x version, but I dont see any way to
> actually download and verify that 5.4.x version against the hash in linux.hash
> 
> ?
> 
> What would be the method to have buildroot download the ?latest? 5.4.x kernel
> and also verify its hash against linux.hash?

 There isn't such a method.

 The same hash file is used by both linux and linux-headers. linux-headers
(which is used by the toolchain) has a choice between the still-maintained
stable branches, while linux itself only has the "latest" choice. The idea is
that for the headers, the risk is extremely low when you update them within the
same stable series, while for the kernel itself, there is significant risk of
breakage when it's updated under the hood.

 But, to be honest, I think the value of that choice in linux-headers is pretty
limited. In all my projects, I use the exact same version as the kernel (either
with the "Same as kernel" option, or with a manually specified version when the
kernel is built seperately).


 Regards,
 Arnout

      parent reply	other threads:[~2021-05-28 19:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-28 17:15 [Buildroot] Verifying linux 5.4.x hashes Ian Merin
2021-05-28 19:55 ` Yann E. MORIN
2021-05-28 20:03   ` Arnout Vandecappelle
2021-05-28 20:17     ` Yann E. MORIN
2021-06-09 14:28       ` [Buildroot] [EXTERNAL] " Ian Merin
2021-06-12 11:54         ` Arnout Vandecappelle
2021-05-28 20:29   ` [Buildroot] " Alexander Dahl
2021-05-28 20:49     ` Yann E. MORIN
2021-05-28 19:59 ` Arnout Vandecappelle [this message]

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=7e2d0cc4-892e-177e-0e9c-935dfbea0c46@mind.be \
    --to=arnout@mind.be \
    --cc=buildroot@busybox.net \
    /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.