[
https://issues.apache.org/jira/browse/JCR-4182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16198524#comment-16198524
]
Julian Reschke edited comment on JCR-4182 at 10/10/17 1:42 PM:
---------------------------------------------------------------
trunk: [r1811667|http://svn.apache.org/r1811667]
2.14: [r1811686|http://svn.apache.org/r1811686]
2.12: [r1811690|http://svn.apache.org/r1811690]
2.10: [r1811693|http://svn.apache.org/r1811693]
2.8: [r1811695|http://svn.apache.org/r1811695]
was (Author: reschke):
trunk: [r1811667|http://svn.apache.org/r1811667]
2.14: [r1811686|http://svn.apache.org/r1811686]
2.12: [r1811690|http://svn.apache.org/r1811690]
2.10: [r1811693|http://svn.apache.org/r1811693]
> new release checksum requirements
> ---------------------------------
>
> Key: JCR-4182
> URL: https://issues.apache.org/jira/browse/JCR-4182
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Reporter: Davide Giannella
> Assignee: Julian Reschke
> Labels: candidate_jcr_2_6
> Fix For: 2.16, 2.10.7, 2.6.10, 2.15.7, 2.8.7, 2.12.9
>
>
> As of various SHA algorithm the Apache policies around signatures and
> checksums changed requiring to specify the sha algorithm as part of the file
> extension: sha1, sha256, sha512.
> http://www.apache.org/dev/release-distribution#sigs-and-sums
> currently Jackrabbit signs with sha-1 and we should at least change the file
> extension
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
