From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 3/3] cargo-bin: bump version to 0.30.0
Date: Sun, 21 Oct 2018 23:24:53 +0200 [thread overview]
Message-ID: <87y3ar3sd6.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20181021174157.GA7056@itchy> (Eric Le Bihan's message of "Sun, 21 Oct 2018 19:41:57 +0200")
>>>>> "Eric" == Eric Le Bihan <eric.le.bihan.dev@free.fr> writes:
Hi,
>> This looks weird and suspicious. Has upstreaming modified their tarball
>> after releasing them ? Has their server been hacked, and the tarballs
>> replaced with some bad thing inside ?
> Void Linux seems to have the same issue [4]. They reverted a commit
> where the initial hash for cargo-0.30.0-i686 was
> 4b828c263283241ad1c99f30e0b5d8554b6dac2737d09cfd466b4c15b0d7296a (just
> like in my patch) to
> 43a5754d13fa0436b33c48b1f562b4198d6930efad3dc36284b88289ff20d74d (the
> new one). Sames goes for x86_64.
Ahh, ok.
> The key is listed among the official ones [5,6].
Thanks!
> Should the new patch with proper hashes mentions something like this?
> ```
> # From https://static.rust-lang.org/dist/cargo-0.30.0-i686-unknown-linux-gnu.tar.xz.sha256
> # Verified using https://static.rust-lang.org/dist/cargo-0.30.0-i686-unknown-linux-gnu.tar.xz.asc
> sha256
> 43a5754d13fa0436b33c48b1f562b4198d6930efad3dc36284b88289ff20d74d
> cargo-0.30.0-i686-unknown-linux-gnu.tar.xz
Looks good to me, please send a patch with that.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2018-10-21 21:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-18 20:58 [Buildroot] [PATCH 0/3] Bump rust to 1.29.2 Eric Le Bihan
2018-10-18 20:58 ` [Buildroot] [PATCH 1/3] rust-bin: bump version " Eric Le Bihan
2018-10-18 20:58 ` [Buildroot] [PATCH 2/3] rust: " Eric Le Bihan
2018-10-18 20:58 ` [Buildroot] [PATCH 3/3] cargo-bin: bump version to 0.30.0 Eric Le Bihan
2018-10-20 22:02 ` Thomas Petazzoni
2018-10-21 17:41 ` Eric Le Bihan
2018-10-21 21:24 ` Peter Korsgaard [this message]
2018-10-20 17:29 ` [Buildroot] [PATCH 0/3] Bump rust to 1.29.2 Thomas Petazzoni
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=87y3ar3sd6.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--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