[jira] [Comment Edited] (CASSANDRA-13325) Bring back the accepted encryption protocols list as configurable option

["Jason Brown (JIRA)" <ji...@apache.org>]

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

Jason Brown edited comment on CASSANDRA-13325 at 2/5/18 9:30 PM:
-----------------------------------------------------------------

Raising this back up again. I think there's a valid argument here for reintroducing the accepted encryption protocols list. We can, and certainly should, default to the JVM or netty defaults, but if an operator has specific requirements, and knows what they are doing, should we stop them?

Note that after CASSANDRA-8457/CASSANDRA-10404 we cannot rely on jvm system properties nor a {{java.security}} file as they are not recognized by netty.


was (Author: jasobrown):
Raising this back up again. I think there's a valid argument here for reintroducing the accepted encryption protocols list. We can, and certainly should, default to the JVM or netty defaults, but if an operator has specific requirements, and knows what they are doing, should we stop them?

Note that after CASSANDRA-8457/CASSANDRA-10404 we cannot rely on jvm system properties nor a {{java.security}} file.

> 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
>            Assignee: Nachiket Patil
>            Priority: Minor
>             Fix For: 4.x
>
>         Attachments: trunk.diff
>
>
> 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
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org