Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 3/7] boot/uboot: do not check hash for custom versions
Date: Fri, 01 May 2015 17:48:20 +0200	[thread overview]
Message-ID: <5543A044.30604@mind.be> (raw)
In-Reply-To: <20150501153117.GB4206@free.fr>

On 01/05/15 17:31, Yann E. MORIN wrote:
> Arnout, All,
> 
> On 2015-05-01 15:14 +0200, Arnout Vandecappelle spake thusly:
>> On 29/04/15 00:40, Yann E. MORIN wrote:
>>> For custom tarballs, it's quite obvious we can not check hashes.
>>>
>>> For custom versions, that's not so obvious. One might think we could
>>> have hashes for all the official releases, but that's not possible: if
>>> the user uses a released version of Buildroot (say 2015.05) much later
>>> in the future, and wants to use the then-released 2038.02 U-Boot. It now
>>> seems pretty obvious that Buildroot 2015.02 can't know the hash for
>>> U-Boot 2038.02.
>>>
>>> So, disable checking the hash for custom tarballs and custom versions.
>>>
>>> Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
>>> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
>>> Cc: Vincent Stehle <vincent.stehle@laposte.net>
>>> ---
>>>  boot/uboot/uboot.mk | 4 ++++
>>>  1 file changed, 4 insertions(+)
>>>
>>> diff --git a/boot/uboot/uboot.mk b/boot/uboot/uboot.mk
>>> index 01aaf2c..410d8d8 100644
>>> --- a/boot/uboot/uboot.mk
>>> +++ b/boot/uboot/uboot.mk
>>> @@ -17,6 +17,7 @@ ifeq ($(UBOOT_VERSION),custom)
>>>  UBOOT_TARBALL = $(call qstrip,$(BR2_TARGET_UBOOT_CUSTOM_TARBALL_LOCATION))
>>>  UBOOT_SITE = $(patsubst %/,%,$(dir $(UBOOT_TARBALL)))
>>>  UBOOT_SOURCE = $(notdir $(UBOOT_TARBALL))
>>> +BR_NO_CHECK_HASH_FOR += $(UBOOT_SOURCE)
>>>  else ifeq ($(BR2_TARGET_UBOOT_CUSTOM_GIT),y)
>>>  UBOOT_SITE = $(call qstrip,$(BR2_TARGET_UBOOT_CUSTOM_REPO_URL))
>>>  UBOOT_SITE_METHOD = git
>>> @@ -27,6 +28,9 @@ else
>>>  # Handle stable official U-Boot versions
>>>  UBOOT_SITE = ftp://ftp.denx.de/pub/u-boot
>>>  UBOOT_SOURCE = u-boot-$(UBOOT_VERSION).tar.bz2
>>> +ifeq ($(BR2_TARGET_UBOOT_CUSTOM_VERSION),y)
>>> +BR_NO_CHECK_HASH_FOR += $(UBOOT_SOURCE)
>>> +endif
>>>  endif
>>
>>  Since we really only have a hash for the latest version, I would prefer a
>> simple check after the entire condition:
>>
>> ifeq ($(BR2_TARGET_UBOOT_LATEST_VERSION),)
>> BR_NO_CHECK_HASH_FOR += $(UBOOT_SOURCE)
>> endif
>>
>>  This redundantly handles the VCS cases, but OTOH it doesn't hurt to have these
>> tarballs in there either.
> 
> Acutally, I prefer we explicitly exclude only what we really want to be
> excluded.
> 
> VCS sutff is forcibly excluded, becasue the git/hg/cvs/svn/bzr macros do
> explicitly disable checking hashes by themselves.
> 
> Also, I would ultimately like that it is an error if there is a hash for
> something that is excluded. Granted, it;'s currently not possible, but
> long-term I;d like to revisit this.
> 
> So, in the end, I'd really like to only exckude what really needs to be
> excluded.

 OK. So:

Acked-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>

> 
>> Actually, before patch 2/7, the VCS cases wouldn't
>> even be added because UBOOT_SOURCE is not set yet at that point :-)
> 
> Well, in my patch, it is set a few lines above. And patch 2 is already
> applied! ;-)

 Is it? Or do you mean patch 1?

 Regards,
 Arnout

> 
> Regards,
> Yann E. MORIN.
> 


-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

  reply	other threads:[~2015-05-01 15:48 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-28 22:39 [Buildroot] [PATCH 0/7] hashes: add more custom versions to the exclusion list (branch yem/no-hash-custom) Yann E. MORIN
2015-04-28 22:39 ` [Buildroot] [PATCH 1/7] boot/gummiboot: switch to http for git clone Yann E. MORIN
2015-05-01  8:32   ` Thomas Petazzoni
2015-04-28 22:39 ` [Buildroot] [PATCH 2/7] pkg-infra: assign BR_NO_CHECK_HASH_FOR so it is recursively-expanded Yann E. MORIN
2015-05-01 13:07   ` Arnout Vandecappelle
2015-05-01 15:26     ` Yann E. MORIN
2015-05-01 15:45       ` Arnout Vandecappelle
2015-05-01 16:22         ` Yann E. MORIN
2015-04-28 22:40 ` [Buildroot] [PATCH 3/7] boot/uboot: do not check hash for custom versions Yann E. MORIN
2015-04-29  5:49   ` Vincent Stehlé
2015-05-01 13:14   ` Arnout Vandecappelle
2015-05-01 15:31     ` Yann E. MORIN
2015-05-01 15:48       ` Arnout Vandecappelle [this message]
2015-05-01 16:21         ` Yann E. MORIN
2015-04-28 22:40 ` [Buildroot] [PATCH 4/7] boot/barebox: " Yann E. MORIN
2015-05-01 13:15   ` Arnout Vandecappelle
2015-05-01 15:32     ` Yann E. MORIN
2015-05-01 15:52       ` Arnout Vandecappelle
2015-04-28 22:40 ` [Buildroot] [PATCH 5/7] boot/mxs-bootlets: do not check hash of custom tarball Yann E. MORIN
2015-05-01 13:25   ` Arnout Vandecappelle
2015-04-28 22:40 ` [Buildroot] [PATCH 6/7] linux: do not check hashes for custom versions and tarballs Yann E. MORIN
2015-05-01 13:34   ` Arnout Vandecappelle
2015-05-01 15:38     ` Yann E. MORIN
2015-05-01 15:50       ` Arnout Vandecappelle
2015-05-01 21:35     ` Yann E. MORIN
2015-04-28 22:40 ` [Buildroot] [PATCH 7/7] package/xenomai: ignore custom versions Yann E. MORIN
2015-05-01 13:37   ` Arnout Vandecappelle
2015-04-28 22:46 ` [Buildroot] [PATCH 8/7] package/xenomai: add hash file Yann E. MORIN
2015-04-29  4:16   ` Baruch Siach
2015-04-29  6:33     ` Yann E. MORIN
2015-05-01 13:54   ` Arnout Vandecappelle

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=5543A044.30604@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox