infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Henk Penning (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-14611) sha-512 checksum go into .sha512 files (in /dist/)
Date Mon, 31 Jul 2017 09:23:00 GMT

    [ https://issues.apache.org/jira/browse/INFRA-14611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16107016#comment-16107016
] 

Henk Penning commented on INFRA-14611:
--------------------------------------

Ok ; done ; should be good.

http://www.apache.org/dev/release-distribution#sigs-and-sums

Also fixed :

http://www.apache.org/dev/release-signing.html

> sha-512 checksum go into .sha512 files (in /dist/)
> --------------------------------------------------
>
>                 Key: INFRA-14611
>                 URL: https://issues.apache.org/jira/browse/INFRA-14611
>             Project: Infrastructure
>          Issue Type: Improvement
>          Components: Documentation
>            Reporter: Henk Penning
>
> Policy document
> http://www.apache.org/dev/release-distribution#sigs-and-sums
> says :
> "An SHA checksum SHOULD also be created and MUST be suffixed .sha. The checksum SHOULD
be generated using SHA512".
> Putting all kinds of SHA checksums is a .sha file is not handy if/when you want to verify
that the checksum is correct.
> -- SHA-1 sums must go into a .sha1 file
> -- SHA-256 sums must go into a .sha256 file
> -- SHA-512 sums must go ino a .sha512 file
> -- a .sha file must contain a SHA-1 sum
> The last point because in the old days, in /dist/, .sha meant SHA-1.
> If there are no objections, I'll fix the doc in a couple of days.
> There are now some 1000 .sha files ; half of them contain SHA-1 sums ; many TLP's have
them. The other half contain SHA-512 sums ; only a few TLP's have those.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message