[
https://issues.apache.org/jira/browse/SOLR-10338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15944277#comment-15944277
]
Shawn Heisey commented on SOLR-10338:
-------------------------------------
If we are using a non-blocking source for the random number generator, I don't
think we need to check entropy or warn about it. It seems that people who
really understand what's going on say that the non-blocking source is preferred
over the blocking source for all production usage, and only hardcore crypto
researchers are likely to need the blocking source.
In my own development efforts outside of Solr, I have seen that when a Tomcat
server starts up, configuring "/dev/./urandom" for the java random source can
reduce the startup by ten to fifteen seconds.
> Configure SecureRandom non blocking
> -----------------------------------
>
> Key: SOLR-10338
> URL: https://issues.apache.org/jira/browse/SOLR-10338
> Project: Solr
> Issue Type: Sub-task
> Reporter: Mihaly Toth
> Assignee: Mark Miller
> Fix For: 4.9, 6.0
>
> Attachments: 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
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
