[
https://issues.apache.org/jira/browse/SOLR-10338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16412163#comment-16412163
]
Hoss Man commented on SOLR-10338:
---------------------------------
I'm not sure i follow your concern David: Even if you _think_ your plugin
doesn't care about encryption, the test baseclass still randomizes it and wants
to ensure that it's going to work -- so that when your custom plugin tests are
run you can _verify_ that your plugin doesn't fail if the user enables
encryption.
And besides: doesn't the assertion failure message make it very clear what you
can do if you *really* don't care about testing this?
> Configure SecureRandom non blocking for tests.
> ----------------------------------------------
>
> Key: SOLR-10338
> URL: https://issues.apache.org/jira/browse/SOLR-10338
> Project: Solr
> Issue Type: Sub-task
> Reporter: Mihaly Toth
> Assignee: Mark Miller
> Priority: Major
> Fix For: 7.1, master (8.0)
>
> Attachments: SOLR-10338.patch, SOLR-10338.patch, SOLR-10338.patch,
> SOLR-10338.patch, SOLR-10338.patch, SOLR-10338.patch, SOLR-10338.patch,
> SOLR-10338.patch
>
>
> It would be best if SecureRandom could be made non blocking. In that case we
> could get rid of random entropy exhaustion issue related to all usages of
> SecureRandom.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
