diff options
| author | Michiel Beijen <mb@x14.nl> | 2022-02-01 22:30:00 +0100 |
|---|---|---|
| committer | ℕicolas ℝ <nicolas@atoomic.org> | 2022-02-01 15:13:19 -0700 |
| commit | 6bd57ce23e81c7d25d818e07caf5d59383c2d945 (patch) | |
| tree | 4c5ecae70f3ec9e6e7a1328191996ed193bfdbdd /Porting/release_announcement_template.txt | |
| parent | a963d6d5acabdd8c78afec507b56f890de6d346a (diff) | |
| download | perl-6bd57ce23e81c7d25d818e07caf5d59383c2d945.tar.gz | |
Use sha256 instead of sha1 in release announcement
The last time perl got released, there was this comment:
https://www.nntp.perl.org/group/perl.perl5.porters/2022/01/msg262480.html
> Why use the old ( and somewhat broken ) SHA1 for message digests?
I decided to look into using SHA256;
I notice that the release managers guide gets the SHA1s from the PAUSE
email. So I've made a PR from PAUSE so that they no longer send SHA1s
(or MD5SUMS for that matter) but just SHA256. That change is live
already, see https://github.com/andk/pause/pull/379
So now the next step is to update the perl release documentation to deal
with the new reality that PAUSE mails no longer incluse sha1s!
Diffstat (limited to 'Porting/release_announcement_template.txt')
| -rw-r--r-- | Porting/release_announcement_template.txt | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/Porting/release_announcement_template.txt b/Porting/release_announcement_template.txt index 9ed30bd6e5..7ec8315704 100644 --- a/Porting/release_announcement_template.txt +++ b/Porting/release_announcement_template.txt @@ -10,10 +10,10 @@ favorite CPAN mirror or find it at: https://metacpan.org/release/[AUTHOR]/perl-5.[VERSION.SUBVERSION]/ -SHA1 digests for this release are: +SHA256 digests for this release are: - [TAR.GZ SHA1] perl-5.[VERSION.SUBVERSION].tar.gz - [TAR.XZ SHA1] perl-5.[VERSION.SUBVERSION].tar.xz + [TAR.GZ SHA256] perl-5.[VERSION.SUBVERSION].tar.gz + [TAR.XZ SHA256] perl-5.[VERSION.SUBVERSION].tar.xz You can find a full list of changes in the file "perldelta.pod" located in the "pod" directory inside the release and on the web at |