From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Replace MD5 with SHA256 hashes all at once
Date: Tue, 21 Jul 2015 12:16:33 +0200 [thread overview]
Message-ID: <20150721101633.GB14386@pengutronix.de> (raw)
In-Reply-To: <915054555B5659448ACF8A70E114824D01BD2CDF80@Exchange2010.kamstrup.dk>
On Tue, Jul 21, 2015 at 05:26:20AM +0000, Bruno Thomsen wrote:
> > what do you think about a script to replace all existing MD5 hashes with SHA256 instead of replacing all of them individually?
>
> Okay, so you want to create a script that take all rules; download the source; sha256sum; modify rule.
Enable all Packages (and ALLYES) in a BSP and then run 'ptxdist get' to
download them all.
And the first step must be to support checking md5 or sha256, whichever is
available. We still need md5 so we don't break BSPs with local packages
during the transition.
> Sounds like a good idea, but then I would prefer that 2-3 ppl run the
> script, just to make sure different proxies are used.
While this is a nice idea, this only works for the existing packages. I
can't do the same for new packages or new versions of existing packages.
So far the checksum has only been a protection against broken archives or
stupid upstream. It is not a security feature. If we change that, then we
need a way to verify, that the initial checksums are correct. I don't know
how I can do that for new packages.
Michael
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2015-07-21 8:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-19 12:44 Clemens Gruber
2015-07-21 5:26 ` Bruno Thomsen
2015-07-21 10:16 ` Michael Olbrich [this message]
2015-08-03 8:06 ` Bruno Thomsen
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=20150721101633.GB14386@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/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