[
https://issues.apache.org/jira/browse/CASSANDRA-13325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15930654#comment-15930654
]
Nachiket Patil commented on CASSANDRA-13325:
--------------------------------------------
bq. My understand of poodle with TLS was that this is a product specific attack
You said it. Then lets deal with it in the application and not modify the java
settings.
If we consider modifying JRE settings, we have to maintain another file and
some settings which is not a part of the package being deployed. This is not a
problem for smaller clusters but when cluster size is thousand nodes, this
becomes operational pain.
If we add the `accepted_protocols` as configurable property and make is so that
if not specified, let java decide what protocol to negotiate, there shouldn't
be any difference on yaml or other settings unless you need to restrict the
protocols.
> 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)
