[
https://issues.apache.org/jira/browse/SOLR-10338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15945251#comment-15945251
]
Mihaly Toth commented on SOLR-10338:
------------------------------------
[~elyograg], I tend to agree with this approach. Your comment seems to be more
related to SOLR-10352. That one is already closed, so I am a bit unsure how to
continue (new Jira, mailing list discussion ?). [~markrmil...@gmail.com],
[~hossman], [~ichattopadhyaya] can you please advise here? Actually, I see 3
alternatives on the startup:
# Warning in case of shortage of entropy
# Fixed /dev/urandom, no warning
# Overwritable default /dev/urandom with warning if configured source is short
of entropy (in case some user disagree with our thinking and would like to use
/dev/random)
Anyway, no matter what the startup script does the unit tests are not started
with it. So the changes in the patch are required here... Actually I forgot to
explicitly mention in my previous comment that I have uploaded a new patch with
the changes mentioned.
> 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
