cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefan Podkowinski (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-13325) Bring back the accepted encryption protocols list as configurable option
Date Tue, 14 Mar 2017 19:41:41 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-13325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15924871#comment-15924871
] 

Stefan Podkowinski commented on CASSANDRA-13325:
------------------------------------------------

My understand of poodle with TLS was that this is a product specific attack and I haven't
found any references to the JVM in this regard. But I'm not an expert on this and the linked
recommendations still stands, therefor we should not stand in the way for the user to follow
them.

The good news is that you can disable TLSv1.0 right away by setting [jdk.tls.disabledAlgorithms|https://docs.oracle.com/javase/8/docs/technotes/guides/security/jsse/JSSERefGuide.html#DisabledAlgorithms]
in your security properties. Why would doing that be considered a vulnerability? The java.security
file needs to exist anyways for the JRE, so why not provision it with the settings you'd consider
reasonable safe?




> Bring back the accepted encryption protocols list as configurable option
> ------------------------------------------------------------------------
>
>                 Key: CASSANDRA-13325
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-13325
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Configuration
>            Reporter: Nachiket Patil
>            Priority: Minor
>
> With CASSANDRA-10508, the hard coded list of accepted encryption protocols was eliminated.
For some use cases, it is necessary to restrict the encryption protocols used for communication
between client and server. Default JVM way of negotiations allows the best encryption protocol
that client can use. 
> e.g. I have set Cassandra to use encryption. Ideally client and server negotiate to use
best protocol (TLSv1.2). But a malicious client might force TLSv1.0 which is susceptible to
POODLE attacks.
> At the moment only way to restrict the encryption protocol is using the {{jdk.tls.client.protocols}}
systems property. If I dont have enough access to modify this property, I dont have any way
of restricting the encryption protocols.
> I am proposing bring back the accepted_protocols property but make it configurable. If
not specified, let the JVM take care of the TLS negotiations.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message