Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jira@apache.org
Date: Sat, 19 Apr 2014 21:13:17 +0000 (UTC)
From: "David Medinets (JIRA)" <jira@apache.org>
To: notifications@accumulo.apache.org
Message-ID: <JIRA.12554729.1336673114743.144145.1397941997788@arcas>
In-Reply-To: <JIRA.12554729.1336673114743@arcas>
References: <JIRA.12554729.1336673114743@arcas>
Subject: [jira] [Updated] (ACCUMULO-586) sign jars when building a release
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/ACCUMULO-586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Medinets updated ACCUMULO-586:
------------------------------------

    Priority: Minor  (was: Major)

> sign jars when building a release
> ---------------------------------
>
>                 Key: ACCUMULO-586
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-586
>             Project: Accumulo
>          Issue Type: Improvement
>            Reporter: Adam Fuchs
>            Priority: Minor
>
> As part of the release process we should include the following steps:
> 1. Generate a new key pair
> 2. Use it to sign the jars
> 3. Generate a java security policy file that includes the public key
> 4. Destroy the private key
> This opens up the possibility of using the java security manager to restrict what code can be loaded and increase the security of Accumulo.


--
This message was sent by Atlassian JIRA
(v6.2#6252)