Re: add sha256 files to releases

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: add sha256 files to releases
Date: 2013-04-15 03:24:20
Message-ID: 15524.1365996260@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> Could we generated sha256 files for the release tarballs, instead of the
> md5 files that are currently generated? The packaging systems that I
> surveyed that verify the checksum of the tarball (FreeBSD ports and the
> like) don't use md5 anymore, so a sha256 file would be much more useful
> for direct verification. For someone doing manual checking of their
> download, it wouldn't make a difference if a different method is used.

md5 is still handy for Fedora/RHEL purposes --- not so much for
verification, as for a crosscheck that the upload into their lookaside
cache happened correctly (the lookaside cache is indexed by md5).

I have no objection to generating sha256 checksums in addition to the
md5 ones, though.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Florian Pflug 2013-04-15 07:32:03 Re: Inconsistent DB data in Streaming Replication
Previous Message Robert Haas 2013-04-15 03:20:18 Re: PROPOSAL: tracking aggregated numbers from pg_stat_database