Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Alexandre Belloni <alexandre.belloni@piout.net>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2012-10-09
Date: Wed, 10 Oct 2012 18:56:20 +0200	[thread overview]
Message-ID: <20121010165620.GA21086@piout.net> (raw)
In-Reply-To: <20121010124644.55d52fff@skate>

On Wed, Oct 10, 2012 at 12:46:44PM +0200, Thomas Petazzoni wrote :
> 
> Ok. I am not a security expert, but I am not sure that downloading
> those things from https:// gives any win over a http:// download. What
> would be more interesting is to be able to verify the cryptographic
> signature of those tarballs (or the signature of a hash of those
> tarballs), to actually be able to verify that those tarballs have
> really been emitted by whoever is supposed to emit those tarballs. But
> that's another story, and there are probably many projects that don't
> provide cryptographic signatures to verify the authenticity of
> the tarballs.
> 

Anyway, downloading the cryptographic hash/signature from the same host
would make no sense as it would probably be tempered with at the same
time as the package itself. In the case we want to ensure integrity,
buildroot should come with the cryptographic hash of each package, in
the .mk files for example.


-- 
Alexandre Belloni

  parent reply	other threads:[~2012-10-10 16:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-10  6:34 [Buildroot] [autobuild.buildroot.net] Build results for 2012-10-09 Thomas Petazzoni
2012-10-10 10:07 ` Peter Korsgaard
2012-10-10 10:29   ` Thomas Petazzoni
2012-10-10 10:34     ` Peter Korsgaard
2012-10-10 10:46       ` Thomas Petazzoni
2012-10-10 10:52         ` Gustavo Zacarias
2012-10-10 16:56         ` Alexandre Belloni [this message]
2012-10-10 17:32           ` Michael S. Zick

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=20121010165620.GA21086@piout.net \
    --to=alexandre.belloni@piout.net \
    --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