hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karthik Kambatla (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HADOOP-11217) Disable SSLv3 in KMS
Date Wed, 29 Oct 2014 00:17:34 GMT

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

Karthik Kambatla updated HADOOP-11217:
    Summary: Disable SSLv3 in KMS  (was: Disable SSLv3 (POODLEbleed vulnerability) in KMS)

> Disable SSLv3 in KMS
> --------------------
>                 Key: HADOOP-11217
>                 URL: https://issues.apache.org/jira/browse/HADOOP-11217
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: kms
>    Affects Versions: 2.6.0
>            Reporter: Robert Kanter
>            Assignee: Robert Kanter
>            Priority: Blocker
>         Attachments: HADOOP-11217.patch, HADOOP-11217.patch
> We should disable SSLv3 in KMS to protect against the POODLEbleed vulnerability.
> See [CVE-2014-3566|http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2014-3566]
> We have {{sslProtocol="TLS"}} set to only allow TLS in ssl-server.xml, but when I checked,
I could still connect with SSLv3.  There documentation is somewhat unclear in the tomcat configs
between {{sslProtocol}}, {{sslProtocols}}, and {{sslEnabledProtocols}} and what each value
they take does exactly.  From what I can gather, {{sslProtocol="TLS"}} actually includes SSLv3
and the only way to fix this is to explicitly list which TLS versions we support.

This message was sent by Atlassian JIRA

View raw message