Return-Path: X-Original-To: apmail-cassandra-commits-archive@www.apache.org Delivered-To: apmail-cassandra-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 95C6B10B54 for ; Thu, 17 Apr 2014 14:27:20 +0000 (UTC) Received: (qmail 78267 invoked by uid 500); 17 Apr 2014 14:27:17 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 78158 invoked by uid 500); 17 Apr 2014 14:27:16 -0000 Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cassandra.apache.org Delivered-To: mailing list commits@cassandra.apache.org Received: (qmail 78043 invoked by uid 99); 17 Apr 2014 14:27:15 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 17 Apr 2014 14:27:15 +0000 Date: Thu, 17 Apr 2014 14:27:15 +0000 (UTC) From: "Jeremiah Jordan (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CASSANDRA-6847) The binary transport doesn't load truststore file MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CASSANDRA-6847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13972980#comment-13972980 ] Jeremiah Jordan commented on CASSANDRA-6847: -------------------------------------------- Can we put a line in changes.txt for this? I spent 2 days pulling my hair out from this one, and yes I probably should have done a full JIRA search, but I would expect "require_client_auth" being completely broken to show up in changes.txt :/ > The binary transport doesn't load truststore file > ------------------------------------------------- > > Key: CASSANDRA-6847 > URL: https://issues.apache.org/jira/browse/CASSANDRA-6847 > Project: Cassandra > Issue Type: Bug > Reporter: Mikhail Stepura > Assignee: Mikhail Stepura > Priority: Minor > Labels: ssl > Fix For: 1.2.16, 2.0.7, 2.1 beta2 > > Attachments: cassandra-2.0-6847.patch > > > {code:title=org.apache.cassandra.transport.Server.SecurePipelineFactory} > this.sslContext = SSLFactory.createSSLContext(encryptionOptions, false); > {code} > {{false}} there means that {{truststore}} file won't be loaded in any case. > And that means that the file will not be used to validate clients when {{require_client_auth==true}}, making http://www.datastax.com/documentation/cassandra/2.0/cassandra/security/secureNewTrustedUsers_t.html meaningless. > The only way to workaround that currently is to start C* with {{-Djavax.net.ssl.trustStore=conf/.truststore}} > I believe we should load {{truststore}} when {{require_client_auth==true}}, -- This message was sent by Atlassian JIRA (v6.2#6252)