From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/4] pciutils: add hash file
Date: Thu, 16 Oct 2014 11:06:15 -0300 [thread overview]
Message-ID: <543FD0D7.2010307@zacarias.com.ar> (raw)
In-Reply-To: <878ukhotem.fsf@dell.be.48ers.dk>
On 10/15/2014 07:33 PM, Peter Korsgaard wrote:
> While this checksum matches the .asc file, it is different than what
> was on the old server (and on sources.buildroot.org, autobuilders and
> whatnot) - And as pciutils hasn't been bumped since Nov 2013 people are
> quite likely to already have it in their dl/.
>
> As pciutils isn't really such a security sensitive package, I think we
> should wait with this until the version is bumped next time.
That shouldn't be a decisive factor, you're looking for consistency
besides security and it shouldn't reduce the effort in doing so.
I can argue that the security factor is indeed important, if you run
things as root (lspci, setpci) - which is common in embedded targets -
and the tarball installs a nifty backdoor then you probably wouldn't be
too happy about it.
I know it would be odd to use those tools outside development.
So compromise solution: switch to a new tarball format, that one isn't
cached anywhere.
Regards.
next prev parent reply other threads:[~2014-10-16 14:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-14 23:24 [Buildroot] [PATCH 1/4] tftpd: add hash file Gustavo Zacarias
2014-10-14 23:24 ` [Buildroot] [PATCH 2/4] pciutils: " Gustavo Zacarias
2014-10-15 22:33 ` Peter Korsgaard
2014-10-16 14:06 ` Gustavo Zacarias [this message]
2014-10-14 23:24 ` [Buildroot] [PATCH 3/4] crda: " Gustavo Zacarias
2014-10-16 5:09 ` Peter Korsgaard
2014-10-14 23:24 ` [Buildroot] [PATCH 4/4] kmod: " Gustavo Zacarias
2014-10-16 5:11 ` Peter Korsgaard
2014-10-15 13:20 ` [Buildroot] [PATCH 1/4] tftpd: " Peter Korsgaard
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=543FD0D7.2010307@zacarias.com.ar \
--to=gustavo@zacarias.com.ar \
--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.