hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Colm O hEigeartaigh (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-14388) Don't set the key password if there is a problem reading SSL configuration
Date Wed, 17 May 2017 12:35:04 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-14388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16013943#comment-16013943

Colm O hEigeartaigh commented on HADOOP-14388:


I'm having trouble reproducing the problem, as the test setup was reasonably complex. I think
it makes sense to merge the patch anyway as it follows what is already done for the other
keystore/truststore parameters, but if not then feel free to close it.



> Don't set the key password if there is a problem reading SSL configuration
> --------------------------------------------------------------------------
>                 Key: HADOOP-14388
>                 URL: https://issues.apache.org/jira/browse/HADOOP-14388
>             Project: Hadoop Common
>          Issue Type: Bug
>    Affects Versions: 2.8.0, 2.7.3
>            Reporter: Colm O hEigeartaigh
>            Assignee: Colm O hEigeartaigh
>            Priority: Minor
>             Fix For: 2.7.4, 2.8.1
>         Attachments: HADOOP-14388.patch
> When launching MiniDFSCluster in a test, with "dfs.data.transfer.protection=integrity"
and without specifying a ssl-server.xml, the code hangs on "builder.build()". 
> This is because in HttpServer2, it is setting a null value on the SslSocketConnector:
> c.setKeyPassword(keyPassword);
> Instead, this call should be inside the "if (keystore != null) {" block. Once this is
done the code exits as expected with an error.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org

View raw message