You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cassandra.apache.org by Ben Bromhead <be...@instaclustr.com> on 2013/12/18 00:30:51 UTC

Best avenue for reporting security issues

Hi guys

We’ve come across a bug with potential security implications and in the spirit of responsible disclosure whats the best path for reporting it / submitting patches without making the issue public until a fixed version of Cassandra is released?

As a follow up I would propose that the Cassandra project should have security@cassandra.apache.org mailing address, where sensitive issues can be reported to the core dev team without it being made public.

Regards

Ben Bromhead
Instaclustr | www.instaclustr.com | @instaclustr | +61 415 936 359


Re: Best avenue for reporting security issues

Posted by Paul Querna <pa...@querna.org>.
http://www.apache.org/security/

email security@apache.org since there isn't a Cassandra specific
security list.  This will also help with getting things like CVEs
assigned and making sure balls are not dropped.

On Tue, Dec 17, 2013 at 3:30 PM, Ben Bromhead <be...@instaclustr.com> wrote:
> Hi guys
>
> We’ve come across a bug with potential security implications and in the spirit of responsible disclosure whats the best path for reporting it / submitting patches without making the issue public until a fixed version of Cassandra is released?
>
> As a follow up I would propose that the Cassandra project should have security@cassandra.apache.org mailing address, where sensitive issues can be reported to the core dev team without it being made public.
>
> Regards
>
> Ben Bromhead
> Instaclustr | www.instaclustr.com | @instaclustr | +61 415 936 359
>

Re: Best avenue for reporting security issues

Posted by Ben Bromhead <be...@instaclustr.com>.
No worries, message sent

Ben Bromhead
Instaclustr | www.instaclustr.com | @instaclustr | +61 415 936 359

On 18 Dec 2013, at 10:35 am, Aleksey Yeschenko <al...@apache.org> wrote:

> Hi Ben,
> 
> Send it to me, I'll handle it.
> 
> Thanks
> 
> 
> On Wed, Dec 18, 2013 at 2:30 AM, Ben Bromhead <be...@instaclustr.com> wrote:
> 
>> Hi guys
>> 
>> We’ve come across a bug with potential security implications and in the
>> spirit of responsible disclosure whats the best path for reporting it /
>> submitting patches without making the issue public until a fixed version of
>> Cassandra is released?
>> 
>> As a follow up I would propose that the Cassandra project should have
>> security@cassandra.apache.org mailing address, where sensitive issues can
>> be reported to the core dev team without it being made public.
>> 
>> Regards
>> 
>> Ben Bromhead
>> Instaclustr | www.instaclustr.com | @instaclustr | +61 415 936 359
>> 
>> 


Re: Best avenue for reporting security issues

Posted by Aleksey Yeschenko <al...@apache.org>.
Hi Ben,

Send it to me, I'll handle it.

Thanks


On Wed, Dec 18, 2013 at 2:30 AM, Ben Bromhead <be...@instaclustr.com> wrote:

> Hi guys
>
> We’ve come across a bug with potential security implications and in the
> spirit of responsible disclosure whats the best path for reporting it /
> submitting patches without making the issue public until a fixed version of
> Cassandra is released?
>
> As a follow up I would propose that the Cassandra project should have
> security@cassandra.apache.org mailing address, where sensitive issues can
> be reported to the core dev team without it being made public.
>
> Regards
>
> Ben Bromhead
> Instaclustr | www.instaclustr.com | @instaclustr | +61 415 936 359
>
>