[ 
https://issues.apache.org/jira/browse/SOLR-9068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hoss Man updated SOLR-9068:
---------------------------
    Attachment: SOLR-9068.patch

on the theory that the Solaris SSL impl has bugs when the SecureRandom returns 
nothing but NUL bytes, I drafted this patch to always fill any byte[] with 
Byte.MAX_VALUE.

I'm not seeing any measurably slowdown when using this patch, but obviously it 
isn'

[~thetaphi]: I'd love to know if you can (semi-)reliably reproduce the failures 
your jenkins machines were getting on your Solaris box, and if this patch fixes 
those bugs.

(I'm not seeing any measurably slowdown when using this patch, but it obviously 
involves some extra cycles, so it's not really worth committing unless it 
solves the problem)



> Solaris SSL test failures when using NullSecureRandom?
> ------------------------------------------------------
>
>                 Key: SOLR-9068
>                 URL: https://issues.apache.org/jira/browse/SOLR-9068
>             Project: Solr
>          Issue Type: Sub-task
>            Reporter: Hoss Man
>             Fix For: 4.9, master
>
>         Attachments: SOLR-9068.Lucene-Solr-6.x-Solaris_110.log, 
> SOLR-9068.Lucene-Solr-master-Solaris_558.log, SOLR-9068.patch
>
>
> In parent issue SOLR-5776, NullSecureRandom was introduced and SSLTestConfig 
> was refactored so that both client & server would use it to prevent blocked 
> threads waiting for entropy.
> Since those commits to master & branch_6x, both Solaris jenkins builds have 
> seen failures at the same spots in 
> TestMiniSolrCloudClusterSSL.testSslAndNoClientAuth - and looking at the logs 
> the root cause appears to be intranode communication failures due to 
> "javax.crypto.BadPaddingException"
> Perhaps the Solaris SSL impl has bugs in it's padding code that are tickeled 
> when the SecureRandom instance returns long strings of null bytes?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to