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 Mon, 18 Jul 2016 14:58:20 GMT

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

ASF GitHub Bot commented on PIRK-2:

Github user eawiliams commented on the issue:

    +1 -- looks really good :)
    The (effective) option (pallier.secureRandom.provider) should also be added to the QuerierDriverCLI
-- I am happy to do this once this pull request is merged and closed.

> 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