You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ranger.apache.org by "Selvamohan Neethiraj (JIRA)" <ji...@apache.org> on 2016/09/07 19:32:21 UTC
[jira] [Resolved] (RANGER-750) Spurious file in
https://dist.apache.org/repos/dist/release/incubator/ranger/
[ https://issues.apache.org/jira/browse/RANGER-750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Selvamohan Neethiraj resolved RANGER-750.
-----------------------------------------
Resolution: Fixed
Removed download-keys.sh file from https://dist.apache.org/repos/dist/release/incubator/ranger
{code}
------------------------------------------------------------------------
r15203 | sneethir | 2016-09-07 12:27:31 -0700 (Wed, 07 Sep 2016) | 1 line
RANGER-750: remove download-keys.sh file from release folder
{code}
> Spurious file in https://dist.apache.org/repos/dist/release/incubator/ranger/
> -----------------------------------------------------------------------------
>
> Key: RANGER-750
> URL: https://issues.apache.org/jira/browse/RANGER-750
> Project: Ranger
> Issue Type: Bug
> Environment: https://dist.apache.org/repos/dist/release/incubator/ranger/
> Reporter: Sebb
> Assignee: Selvamohan Neethiraj
>
> he directory https://dist.apache.org/repos/dist/release/incubator/ranger/ contains the file:
> download-keys.sh
> This does not belong on the ASF mirror system.
> Also the script is not suitable for downloading KEYS.
> The file https://people.apache.org/keys/group/ranger.asc is not guaranteed to contain all the keys needed to validate a signature, because the file only contains the current keys for the current members of the PPMC. However the KEYS file is also used for checking archived releases so must contain all keys that have ever been used to sign a release.
> Please remove the script file, and ensure that the KEYS file contains all the keys for every ASF release that has been made. Entries should never be dropped from KEYS files if they have been used to sign a release.
> Thanks
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)