[SOLR-9068] BadPaddingException when running SSL test using NullSecureRandom

• Type: Sub-task
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 6.1, 7.0
• Assignee: Unassigned
• Reporter: Chris M. Hostetter
• Created: 04/May/16 18:16
• Updated: 17/Jun/16 13:11
• Resolved: 11/May/16 00:25

Description

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, all Solaris jenkins builds got 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"

Initial speculation was that perhaps the Solaris SSL impl has bugs in it's padding code that are tickled when the SecureRandom instance returns long strings of null bytes, but subsequently we got reports of similar, less frequently occuring, bugs on other OSs (see SOLR-9082).

Issue Links

• is related to: SOLR-9082 TestMiniSolrCloudClusterSSL.testSslAndNoClientAuth() failure