[
https://issues.apache.org/jira/browse/PIRK-2?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15376609#comment-15376609
]
ASF GitHub Bot commented on PIRK-2:
-----------------------------------
GitHub user tellison opened a pull request:
https://github.com/apache/incubator-pirk/pull/2
[PIRK-2] Load Pallier's PRNG statically and from any provider.
Tested with Oracle jdk180_91 and IBM 8.0.3.0.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/tellison/incubator-pirk pirk-2
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-pirk/pull/2.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #2
----
commit 15f98ec9da94d3780b6cd9e4e9093a3f6e2f2972
Author: Tim Ellison <[email protected]>
Date: 2016-07-14T08:57:14Z
[PIRK-2] Load Pallier's PRNG statically and from any provider.
----
> 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)
