Mailing-List: contact cassandra-user-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cassandra-user@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of jakers@gmail.com designates
 209.85.212.182 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:from:to:in-reply-to:content-type
         :content-transfer-encoding:x-mailer:mime-version:subject:date
         :references;
        b=OLjAy+7AvVJEVUW0vPaQvWlpDuInXBOnu5B+oAQ6WZdjje9jjJ0xf8XoiZmoZ7EV4Y
         gr25tR6zxfbwodYoPl7wHgFJhj210Hjb3dNnk7pITn9lg5viF8D4WtLNNcjz5KqBG9JM
         uquC1TdhhGWbZKf1w1FpgjvicB1hPHjonbLFo=
Message-Id: <28E305A6-9C8C-4016-BC1B-07FD9C9C0C06@gmail.com>
From: Jake Luciani <jakers@gmail.com>
To: "cassandra-user@incubator.apache.org"
 <cassandra-user@incubator.apache.org>
In-Reply-To: <e06563880912021342j5fd576dh6286ea06a1a99039@mail.gmail.com>
Content-Type: text/plain;
	charset=us-ascii;
	format=flowed;
	delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (iPhone Mail 7C144)
Subject: Re: Cassandra access control
Date: Wed, 2 Dec 2009 16:53:04 -0500
References: <87eio6p7pb.fsf@lifelogs.com>
 <ff1a07b80912020713n2485e001x6a9df005d905b62f@mail.gmail.com>
 <87ljhljhv2.fsf@lifelogs.com> <1259784893.10676.32.camel@achilles>
 <87zl61i0kn.fsf@lifelogs.com> <1259786109.10676.35.camel@achilles>
 <ff1a07b80912021254v30d524qeafd3c3222e1b4d7@mail.gmail.com>
 <48011D13-469E-4D19-83CF-DE9292210B88@gmail.com>
 <764B352CF55C514F816B4B14BD2450D804114C45@bcs-mail04.internal.cacheflow.com>
 <C1DD281C-F5C2-4622-8FA7-EE9B2C4FE0AB@gmail.com>
 <e06563880912021342j5fd576dh6286ea06a1a99039@mail.gmail.com>

Got it.

On Dec 2, 2009, at 4:42 PM, Jonathan Ellis <jbellis@gmail.com> wrote:

> It doesn't have to be the outside world, just apps from different
> groups.  Which is the whole (or at least, a major) reason we added
> multiple keyspaces.
>
> On Wed, Dec 2, 2009 at 3:38 PM, Jake Luciani <jakers@gmail.com> wrote:
>> If there is a use case to open a Cassandra cluster to the world  
>> then I
>> agree.
>>
>> Sent from my iPhone
>>
>> On Dec 2, 2009, at 4:24 PM, "Coe, Robin" <robin.coe@bluecoat.com>  
>> wrote:
>>
>>> NoSQL doesn't mean no security.  A production database engine has to
>>> protect its data.  The trick is to make the auth framework fast  
>>> enough
>>> that it doesn't adversely affect performance and robust enough  
>>> that an
>>> application requesting data doesn't have to jump through hoops to  
>>> get
>>> it.
>>>
>>> -----Original Message-----
>>> From: Jake Luciani [mailto:jakers@gmail.com]
>>> Sent: December 2, 2009 4:00 PM
>>> To: cassandra-user@incubator.apache.org
>>> Subject: Re: Cassandra access control
>>>
>>> +1 this is nosql afterall.
>>>
>>> Sent from my iPhone
>>>
>>> On Dec 2, 2009, at 3:54 PM, Mark Robson <markxr@gmail.com> wrote:
>>>
>>>> How about we make authentication optional, and have the protocol
>>>> being stateful only if you want to authenticate?
>>>>
>>>> That way we don't break backwards compatibility or introduce extra
>>>> complexity for people who don't need it.
>>>>
>>>> Mark
>>