[
https://issues.apache.org/jira/browse/SOLR-10338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15945420#comment-15945420
]
Mark Miller commented on SOLR-10338:
------------------------------------
bq. so I am a bit unsure how to continue
If you already have support from someone for an idea, I'd just create a new
JIRA issue and link it to the old one. Unless the old JIRA has not been
released, in those cases you will generally reopen it. If you have no one
discussing with you, and you question what you want to do, perhaps a dev list
discussion, but I don't think that is needed here.
bq. say that the non-blocking source is preferred over the blocking source for
all production usage
Is that true? Don't we want the real deal for production SSL?
> 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
