From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Holger Freyther <holger@freyther.de>, poky@yoctoproject.org
Subject: Re: uninnative and md5 checksum?
Date: Tue, 29 Mar 2016 23:05:41 +0100 [thread overview]
Message-ID: <1459289141.21672.41.camel@linuxfoundation.org> (raw)
In-Reply-To: <541E63F7-405C-4FB4-A264-074F8BB31E62@freyther.de>
On Wed, 2016-03-23 at 12:23 +0100, Holger Freyther wrote:
> Hi,
>
> our jenkins started to fail with yocto-master and I started to take a
> look. I noticed that uninative binaries are being downloaded from the
> network. It is not great to download binaries from the network and
> execute but fair enough there is a checksum.
>
> But the choice of md5 as checksum is a bit odd (md5 and sha1 are
> effectively broken), can this be moved to sha3 or sha256sum?
We use the fetcher's checksuming support so I guess sha256 would be the
better choice. It can be changed, at the expense of a bit of pain
making sure all the changes work smoothly.
Cheers,
Richard
prev parent reply other threads:[~2016-03-29 22:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-23 11:23 uninnative and md5 checksum? Holger Freyther
2016-03-29 22:05 ` Richard Purdie [this message]
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=1459289141.21672.41.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=holger@freyther.de \
--cc=poky@yoctoproject.org \
/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.