From user-return-23869-apmail-cassandra-user-archive=cassandra.apache.org@cassandra.apache.org Wed Feb 1 00:38:19 2012 Return-Path: X-Original-To: apmail-cassandra-user-archive@www.apache.org Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 9257F967E for ; Wed, 1 Feb 2012 00:38:19 +0000 (UTC) Received: (qmail 20618 invoked by uid 500); 1 Feb 2012 00:38:16 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 20535 invoked by uid 500); 1 Feb 2012 00:38:16 -0000 Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@cassandra.apache.org Delivered-To: mailing list user@cassandra.apache.org Received: (qmail 20527 invoked by uid 99); 1 Feb 2012 00:38:15 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Feb 2012 00:38:15 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [208.113.200.5] (HELO homiemail-a59.g.dreamhost.com) (208.113.200.5) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Feb 2012 00:38:10 +0000 Received: from homiemail-a59.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a59.g.dreamhost.com (Postfix) with ESMTP id 044B0564059 for ; Tue, 31 Jan 2012 16:37:49 -0800 (PST) DomainKey-Signature: a=rsa-sha1; c=nofws; d=thelastpickle.com; h=from :mime-version:content-type:subject:date:in-reply-to:to :references:message-id; q=dns; s=thelastpickle.com; b=xLcsZ+h6PB J8/11f/Zmw68sniy9cE8cSP9Q4qnFqfna8wO1eEZf7aqF3XBwXlS7Oo8rv3zQ+9s CM8A+NL+UHeHaobIGiSwmuUYu1Bl6yYWah3gMDBHmhjeHXguzAZbbF7FdHH8LSTX 1aWLj9jy+vGQJUZICu26MnUApvN+pLqTU= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=thelastpickle.com; h=from :mime-version:content-type:subject:date:in-reply-to:to :references:message-id; s=thelastpickle.com; bh=9GmpkHeaQgd76e8X d6mHeLO8iTQ=; b=zbj/VFkGzjmjzI2OW4dx3IfudaK8QjKecljs2EA28u/3jC0A nF2wKYN05BbuoyI/oLdzC0JVbfPnbWDaFqZKL5YV6bWPp0PNZlP7WcGi0wgJnypC 1N12aHGnAnjozBqYAz0tPOs0ep6Nn/VjwvVB7QIWtaB15FWl3C45nCcDPko= Received: from [172.16.1.3] (125-236-193-159.adsl.xtra.co.nz [125.236.193.159]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: aaron@thelastpickle.com) by homiemail-a59.g.dreamhost.com (Postfix) with ESMTPSA id 51E1A564057 for ; Tue, 31 Jan 2012 16:37:48 -0800 (PST) From: aaron morton Mime-Version: 1.0 (Apple Message framework v1251.1) Content-Type: multipart/alternative; boundary="Apple-Mail=_1AE11741-1B98-4976-8E71-CC637900C9A6" Subject: Re: Encrypting traffic between Hector client and Cassandra server Date: Wed, 1 Feb 2012 13:37:44 +1300 In-Reply-To: <4F287A41.60203@bnl.gov> To: user@cassandra.apache.org References: <4F287A41.60203@bnl.gov> Message-Id: X-Mailer: Apple Mail (2.1251.1) --Apple-Mail=_1AE11741-1B98-4976-8E71-CC637900C9A6 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=iso-8859-1 There was a recent post about performance that also talked about using = Open VPN to encrypt traffic from clients to server http://www.mail-archive.com/user@cassandra.apache.org/msg20058.html I've not looked at thrift encryption.=20 Cheers ----------------- Aaron Morton Freelance Developer @aaronmorton http://www.thelastpickle.com On 1/02/2012, at 12:33 PM, Maxim Potekhin wrote: > Hello, >=20 > do you see any value in having a web service over cassandra, with = actual client-clients talking to it via https/ssl? > This way the cluster can be firewalled and therefore protected, plus = you get decent auth/auth right there. >=20 > Maxim >=20 >=20 > On 1/31/2012 5:21 PM, Xaero S wrote: >>=20 >> I have been trying to figure out how to secure/encrypt the traffic = between the client (Hector) and the Cassandra Server. I looked at this = link https://issues.apache.org/jira/browse/THRIFT-106 But since thrift = sits on a layer after Hector, i am wondering how i can get Hector to use = the right Thrift calls to have the encryption happen? Also where can i = get the instructions for the any required setup for encrypting the = traffic between the Hector client and the Cassandra Server? >>=20 >> Would appreciate any help in this regard. Below are the setup = versions >>=20 >> Cassandra Version - 0.8.7 >> Hector - 0.8.0-2 >> libthrift jar - 0.6.1 >>=20 >>=20 >> On a side note, we have setup internode encryption on the Cassandra = server side and found the documentation for that easily. >>=20 >>=20 >>=20 >=20 --Apple-Mail=_1AE11741-1B98-4976-8E71-CC637900C9A6 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=iso-8859-1 There = was a recent post about performance that also talked about using Open = VPN to encrypt traffic from clients to server



I've not looked at thrift = encryption. 

Cheers
http://www.thelastpickle.com

On 1/02/2012, at 12:33 PM, Maxim Potekhin wrote:

Hello,

do you see any value in having a web = service over cassandra, with actual client-clients talking to it via = https/ssl?
This way the cluster can be firewalled and therefore = protected, plus you get decent auth/auth right = there.

Maxim


On 1/31/2012 5:21 PM, Xaero S = wrote:

I have been trying to figure out how to secure/encrypt the = traffic between the client (Hector) and the Cassandra Server. I looked = at this link https://issues.a= pache.org/jira/browse/THRIFT-106 But since thrift sits on a layer = after Hector, i am wondering how i can get Hector to use the right = Thrift calls to have the encryption happen? Also where can i get the = instructions for the any required setup for encrypting the traffic = between the Hector client and the Cassandra = Server?

Would = appreciate any help in this regard. Below are the setup = versions

Cassandra = Version - 0.8.7
Hector - = 0.8.0-2
libthrift jar - = 0.6.1


On a side note, = we have setup internode encryption on the Cassandra server side and = found the documentation for that easily.





= --Apple-Mail=_1AE11741-1B98-4976-8E71-CC637900C9A6--