cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefan Podkowinski (JIRA)" <>
Subject [jira] [Assigned] (CASSANDRA-9590) Support for both encrypted and unencrypted native transport connections
Date Mon, 31 Aug 2015 07:56:45 GMT


Stefan Podkowinski reassigned CASSANDRA-9590:

    Assignee: Stefan Podkowinski

> Support for both encrypted and unencrypted native transport connections
> -----------------------------------------------------------------------
>                 Key: CASSANDRA-9590
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Stefan Podkowinski
>            Assignee: Stefan Podkowinski
>             Fix For: 2.1.x
> Enabling encryption for native transport currently turns SSL exclusively on or off for
the opened socket. Migrating from plain to encrypted requires to migrate all native clients
as well and redeploy all of them at the same time after starting the SSL enabled Cassandra
> This patch would allow to start Cassandra with both an unencrypted and ssl enabled native
port. Clients can connect to either, based whether they support ssl or not.
> This has been implemented by introducing a new {{native_transport_port_ssl}} config option.

> There would be three scenarios:
> * client encryption disabled, {{native_transport_port}} unencrypted, {{native_transport_port_ssl}}
not used
> * client encryption enabled, {{native_transport_port_ssl}} not set, {{native_transport_port}}
> * client encryption enabled, {{native_transport_port_ssl}} set, {{native_transport_port}}
unencrypted, {{native_transport_port_ssl}} encrypted
> This approach would keep configuration behavior fully backwards compatible.
> Patch proposal: [Branch|],
[Diff trunk|],
[Patch against trunk|]
> DTest: [Branch|],
[Diff trunk|]

This message was sent by Atlassian JIRA

View raw message