Mailing-List: contact commits-help@pirk.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@pirk.incubator.apache.org
Date: Sat, 16 Jul 2016 12:45:20 +0000 (UTC)
From: "ASF GitHub Bot (JIRA)" <jira@apache.org>
To: commits@pirk.incubator.apache.org
Message-ID: <JIRA.12989388.1468486463000.49991.1468673120489@Atlassian.JIRA>
In-Reply-To: <JIRA.12989388.1468486463000@Atlassian.JIRA>
References: <JIRA.12989388.1468486463000@Atlassian.JIRA> <JIRA.12989388.1468486463618@arcas>
Subject: [jira] [Commented] (PIRK-2) Enhance Pallier acquisition of PRNG
 provider
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Sat, 16 Jul 2016 12:45:25 -0000


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

ASF GitHub Bot commented on PIRK-2:
-----------------------------------

Github user eawiliams commented on the issue:

    https://github.com/apache/incubator-pirk/pull/2
  
    For the user that would like to remove the ambiguity of the provider, adding a configuration option to specify the provider seems reasonable. Additionally, as the SecureRandom constructor explicitly provides for this option:
    
    SecureRandom(SecureRandomSpi secureRandomSpi, Provider provider)
    
    it makes sense to extend it outwards to Pirk.


> Enhance Pallier acquisition of PRNG provider
> --------------------------------------------
>
>                 Key: PIRK-2
>                 URL: https://issues.apache.org/jira/browse/PIRK-2
>             Project: PIRK
>          Issue Type: Bug
>            Reporter: Tim Ellison
>            Assignee: Tim Ellison
>
> {{org.apache.pirk.encryption.Pallier}} has a hard coded requirement for the {{NativePRNG}} algorithm to be supplied by the {{SUN}} provider.  This causes the {{test.general.PaillierTest}} to fail on IBM's Java implementation.
> The implementation should allow the provider to be configured by the java.security properties of the runtime to allow for provider optimizations, etc.
> Furthermore, the instantiation of a provider is relatively (CPU) expensive, so reusing the PRNG is preferable to acquiring it each time a value is required.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)