[jira] [Commented] (CASSANDRA-14893) Backport CASSANDRA-10508 to 3.0 branch
[ https://issues.apache.org/jira/browse/CASSANDRA-14893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17373013#comment-17373013 ] Brandon Williams commented on CASSANDRA-14893: -- Actually this isn't a bugfix, so it needs approval on the ML to go into 3.0. > Backport CASSANDRA-10508 to 3.0 branch > -- > > Key: CASSANDRA-14893 > URL: https://issues.apache.org/jira/browse/CASSANDRA-14893 > Project: Cassandra > Issue Type: Improvement > Components: Messaging/Internode >Reporter: Tommy Stendahl >Assignee: Tommy Stendahl >Priority: Normal > > With CASSANDRA-10508 we removed the hard coded SSL protocols and in favor of > the jvm default values in th 3.x branch. When reading through that jira it > looks like it was never considered to do the same change in the 3.0 branch > but the reasoning for the change seams just as valid for 3.0. And the issue > with CASSANDRA-14842 when upgrading 3.0.x->4.0 would not have happened. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-14893) Backport CASSANDRA-10508 to 3.0 branch
[ https://issues.apache.org/jira/browse/CASSANDRA-14893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17370950#comment-17370950 ] Brandon Williams commented on CASSANDRA-14893: -- [Jenkins|https://ci-cassandra.apache.org/job/Cassandra-devbranch/882/] doesn't seem to have any related failures, +1. > Backport CASSANDRA-10508 to 3.0 branch > -- > > Key: CASSANDRA-14893 > URL: https://issues.apache.org/jira/browse/CASSANDRA-14893 > Project: Cassandra > Issue Type: Improvement > Components: Messaging/Internode >Reporter: Tommy Stendahl >Assignee: Tommy Stendahl >Priority: Normal > > With CASSANDRA-10508 we removed the hard coded SSL protocols and in favor of > the jvm default values in th 3.x branch. When reading through that jira it > looks like it was never considered to do the same change in the 3.0 branch > but the reasoning for the change seams just as valid for 3.0. And the issue > with CASSANDRA-14842 when upgrading 3.0.x->4.0 would not have happened. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-14893) Backport CASSANDRA-10508 to 3.0 branch
[ https://issues.apache.org/jira/browse/CASSANDRA-14893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16698722#comment-16698722 ] Tommy Stendahl commented on CASSANDRA-14893: I have back-ported the original patch to 3.0, its available in this branch: [cassandra-14893|https://github.com/tommystendahl/cassandra/tree/cassandra-14893] > Backport CASSANDRA-10508 to 3.0 branch > -- > > Key: CASSANDRA-14893 > URL: https://issues.apache.org/jira/browse/CASSANDRA-14893 > Project: Cassandra > Issue Type: Improvement > Components: Streaming and Messaging >Reporter: Tommy Stendahl >Priority: Major > > With CASSANDRA-10508 we removed the hard coded SSL protocols and in favor of > the jvm default values in th 3.x branch. When reading through that jira it > looks like it was never considered to do the same change in the 3.0 branch > but the reasoning for the change seams just as valid for 3.0. And the issue > with CASSANDRA-14842 when upgrading 3.0.x->4.0 would not have happened. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
