Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom de Vries <tdevries@suse.de>
To: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Cc: Joel Brobecker <brobecker@adacore.com>
Subject: Re: md5.sum contains outdated checksum for sha512.sum
Date: Sat, 05 Oct 2019 07:36:00 -0000	[thread overview]
Message-ID: <c8ad8ed8-dd22-eb19-680a-02e03e20c7f6@suse.de> (raw)
In-Reply-To: <789f21e3-f00a-afc7-924c-f89686947c45@suse.de>

On 02-10-19 16:53, Tom de Vries wrote:
> Hi,
> 
> I noticed these files:
> ...
> https://sourceware.org/ftp/gdb/releases/md5.sum
> https://sourceware.org/ftp/gdb/releases/sha512.sum
> ...
> 
> and the fact that they have each other in the checksum list:
> ...
> $ grep sum *.sum
> md5.sum:d302bd90c757261f7a869a7a933ae096  sha512.sum
> sha512.sum:302d3ee680099da76381af62dc8326bc73bd0f72e31733611458213b582fba4f7596b8892676a530dbd95f4fe2257b3f487048ed0815cceefb81c199a8a92662
>  md5.sum
> ...
> 
> Only one matches:
> ...
> $ md5sum sha512.sum
> cbf4a5e7311db1d101038a3411a2cf9b  sha512.sum
> $ sha512sum md5.sum
> 302d3ee680099da76381af62dc8326bc73bd0f72e31733611458213b582fba4f7596b8892676a530dbd95f4fe2257b3f487048ed0815cceefb81c199a8a92662
>  md5.sum
> ...
> 
> So, AFAICT, md5.sum contains an outdated checksum for sha512.sum (and
> AFAIU, as long as the files reference each other, that will be the case).

Using shell access, I found that sha512.sum is generated by root (so I
guess that's some site automation):
...
$ ls -la *sum
-rw-rw-r--. 1 gdbadmin gdb  3386 jun  4  2017 md5.sum
-rw-r--r--. 1 root     gdb 11715 sep 20 22:44 sha512.sum
...

So, we should exclude sha512.sum from md5.sum. But sofar, I was not able
to find how this is generated.

Thanks,
- Tom


  reply	other threads:[~2019-10-05  7:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-02 14:53 Tom de Vries
2019-10-05  7:36 ` Tom de Vries [this message]
2019-10-05 10:08   ` Andreas Schwab
2019-10-06 15:21     ` Joel Brobecker

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=c8ad8ed8-dd22-eb19-680a-02e03e20c7f6@suse.de \
    --to=tdevries@suse.de \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox