cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nachiket Patil (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-13325) Bring back the accepted encryption protocols list as configurable option
Date Tue, 14 Mar 2017 18:51:41 GMT


Nachiket Patil commented on CASSANDRA-13325:

References Inline:
Yes, I was talking about downgrade attacks. [SSLv3 vulnerability|]
which is taken care of in java8. But [TLSv1 vulnerability|]
which has no solution yet.

Many security communities including [PCI council|]
and [NIST|]
guidelines recommend minimum TLS v1.1.

There is a way to set protocol in Cassandra yaml `server_encryption_options` and `client_encryption_options`
but by definition, it is a preferred protocol not restricting protocol (may support other

To restrict TLS protocols to we need to set `jdk.tls.client.protocols` which is not JVM property
it is a JDK setting in `<JRE_HOME>/lib/security/`. Overriding jdk security
settings is also considered a vulnerability.

> Bring back the accepted encryption protocols list as configurable option
> ------------------------------------------------------------------------
>                 Key: CASSANDRA-13325
>                 URL:
>             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

View raw message