pirk-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PIRK-2) Enhance Pallier acquisition of PRNG provider
Date Fri, 15 Jul 2016 13:44:20 GMT

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

ASF GitHub Bot commented on PIRK-2:

Github user eawiliams commented on the issue:

    As different providers of NativePRNG may have different implementations, we want to give
users the ability to specify their provider. Thus, we need to add config option(s) to specify
the the provider or default to 'SUN' and fail over to grab the system-default NativePRNG.

> 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

View raw message