From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] package infra: add mirror support
Date: Thu, 20 Oct 2011 00:10:51 +0200 [thread overview]
Message-ID: <201110200010.52396.arnout@mind.be> (raw)
In-Reply-To: <20111019145934.68b77389@skate>
On Wednesday 19 October 2011 14:59:34, Thomas Petazzoni wrote:
> Le Wed, 19 Oct 2011 11:35:52 +0200,
> Arnout Vandecappelle <arnout@mind.be> a ?crit :
>
> > The recent kernel.org horror has convinced me that some form of
> > verification is needed, though.
>
> Having hashes in Buildroot will not necessarily provide an additional
> security. Consider the following scenario:
>
> 1. The world exists.
> 2. Project foo releases foo-2.1.tar.bz2
> 3. A BR packager bumps package foo to 2.1. He downloads the new
> tarball, generates locally its hash and adds this hash to the
> foo.mk.
> 4. The BR packager patch is merged in Buildroot.
>
> Having hashes in the foo.mk will warn you if the foo website has been
> cracked after step 3. But if it has been cracked between 2) and 3),
> then you're doomed: the BR packager will assume foo-2.1.tar.bz2 is
> correct.
If the upstream source is cracked, then of course you're doomed. What it does protect again is man-in-the-middle attacks (same as https is supposed to protect against but doesn't because of unreliable CAs). If the packager generates a hash of a non-authorized tar, then most users will download packages with a different hash and will (hopefully) report this.
Clearly there is still a vulnerability window, but it is much smaller than in the current situation.
> This packager will quite probably never check a GPG signature
> or do any kind of additional security check when bumping foo to 2.1.
>
> Therefore, I fear that this mechanism would give an *impression* of
> higher security, but would in fact provide no additional security
> compared to not verifying the hashes.
It does give higher security. Perhaps not yet high security, though.
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286540
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: 31BB CF53 8660 6F88 345D 54CC A836 5879 20D7 CF43
next prev parent reply other threads:[~2011-10-19 22:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-18 14:14 [Buildroot] [PATCH 1/2] package infra: add mirror support Gustavo Zacarias
2011-10-18 14:14 ` [Buildroot] [PATCH 2/2] stunnel: add mirror site Gustavo Zacarias
2011-10-18 14:22 ` [Buildroot] [PATCH 1/2] package infra: add mirror support Thomas Petazzoni
2011-10-18 14:32 ` Thomas Petazzoni
2011-10-18 15:55 ` Michael S. Zick
2011-10-18 16:00 ` Gustavo Zacarias
2011-10-18 17:27 ` Thomas Petazzoni
2011-10-18 18:01 ` Gustavo Zacarias
2011-10-18 21:38 ` Arnout Vandecappelle
2011-10-19 8:11 ` [Buildroot] Adding hashes to package recipes Thomas Petazzoni
2011-10-19 8:12 ` [Buildroot] [PATCH 1/2] package infra: add mirror support Sven Neumann
2011-10-19 9:35 ` Arnout Vandecappelle
2011-10-19 12:59 ` Thomas Petazzoni
2011-10-19 16:37 ` Michael S. Zick
2011-10-19 16:59 ` Eric Bénard
2011-10-19 22:10 ` Arnout Vandecappelle [this message]
2011-10-18 16:02 ` Yann E. MORIN
2011-10-18 19:05 ` 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=201110200010.52396.arnout@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