[
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)
