Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

Build memcached with SASL support #31

Closed
michaelklishin opened this Issue Feb 28, 2012 · 3 comments

Comments

Projects
None yet
2 participants
Contributor

michaelklishin commented Feb 28, 2012

Originally reported by @jaysonsantos in travis-ci/travis-ci#434:

As I talked with @michaelklishin on IRC it would be great if memached is build with sasl support.
We have talked about how ugly is build it with sources and maybe apt-get source should be a better approach as it is the same package as in production.
Here is a simple how to http://code.google.com/p/memcached/wiki/SASLHowto
Thank you for this great project

@ghost ghost assigned michaelklishin Feb 28, 2012

Contributor

michaelklishin commented Feb 28, 2012

Another useful guide on the subject.

@michaelklishin michaelklishin referenced this issue in travis-ci/travis-ci Feb 28, 2012

Closed

Build memcached with sasl support #434

Contributor

Mezzle commented Sep 17, 2012

https://launchpad.net/~travis-ci/+archive/memcached-sasl

Built for i386/amd64 ... please test :)

michaelklishin added a commit that referenced this issue Sep 17, 2012

Introduce memcached::ppa. Kudos to @mezzle.
The PPA provides our own package with SASL enabled. References #31.

michaelklishin added a commit to travis-ci/travis-boxes that referenced this issue Sep 17, 2012

michaelklishin added a commit that referenced this issue Oct 16, 2012

Disable SASL for Memcached, references #31
It was a good idea in theory but does not work out
well in practice. Many Memcached clients do not
support SASL or it is not assumed to be enabled
by default. In addition, most developers do not
even realize Memcached has authentication support
at all. In the end, lots of test suites fail for
no obvious reason.

In addition, authentication is not optional, so
we have to either double down or go back to
running Memcached w/o authentication. The latter
is the only realistic option.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment