Maintainer?

19 views
Skip to first unread message

Joseph S. Testa II

unread,
Apr 7, 2009, 11:28:24 AM4/7/09
to memcached
Hi,

I am interested in contacting the maintainer(s) of memcached. A
week ago, I sent e-mail to Brad Fitzpatrick, Anatoly Vorobey, and
Steven Grimm (as they are listed in the packaged AUTHORS /
CONTRIBUTORS files), but I have not received a response. Are they
still the maintainers, or did the responsibility pass to someone else?

Thanks,
- Joe

Dustin

unread,
Apr 7, 2009, 11:59:38 AM4/7/09
to memcached

On Apr 7, 8:28 am, "Joseph S. Testa II" <jte...@positronsecurity.com>
wrote:
Do you have a particular issue you need resolved?

David Stanek

unread,
Apr 7, 2009, 12:05:39 PM4/7/09
to memc...@googlegroups.com
Why not just use this list?

--
Sent from my mobile device

David
blog: http://www.traceback.org
twitter: http://twitter.com/dstanek

Joseph S. Testa II

unread,
Apr 7, 2009, 12:52:11 PM4/7/09
to memcached
> Do you have a particular issue you need resolved?

> Why not just use this list?

There is a minor security-related issue in the latest stable version
of memcached. It wouldn't be appropriate to discuss it in a public
forum until the maintainers have released a fix.

I'll wait a little longer for a response from them.

Thanks,
- Joe

Dustin

unread,
Apr 7, 2009, 1:22:30 PM4/7/09
to memcached

On Apr 7, 9:52 am, "Joseph S. Testa II" <jte...@positronsecurity.com>
wrote:

> There is a minor security-related issue in the latest stable version
> of memcached.  It wouldn't be appropriate to discuss it in a public
> forum until the maintainers have released a fix.
>
> I'll wait a little longer for a response from them.

This is an openly developed project. We need you to file a bug:

http://code.google.com/p/memcached/issues/list

The distribution is out. If you actually tell me what the bug is, I
can fix it and have it ready for the next release, but people will
have to do heavy evaluation before pushing it into their production
environments.

If there's any security issue that actually affects a production
deployment, someone is not deploying memcached correctly.
Reply all
Reply to author
Forward
0 new messages