Hi Dormando,
Don't worry about it. I figured it out. I had to make some changes in the
cyrus-sasl config files and re-configure and then make memcached again.
Also had to re-configure libmemcached with --enable-sasl option.
Looking forward to your token based implementation.
Regards,
Om Kale
On
Well, being extremely thorough; read from file on startup and then use
online commands for modifications is perfectly doable too (and how some
things work) but I feel like that will be hard for people to use.
On Tue, 17 Apr 2018, dormando wrote:
> Right; I'm saying there needs to be a mechanism
Right; I'm saying there needs to be a mechanism of loading what the
current tokens are :) Which are probably going to be from a file on disk.
A rotation would be staged modifications to this file + reload commands or
auto reloading.
Pulling from file would be necessary to avoid losing tokens
Reload would be handy to have but not absolutely necessary.
For rotation, one would just set up their second token (the new one) at
some point in time. Any time after that clients can transition to the new
token. Once all clients are transitioned to the new token, the original
token would then
oh; you might need to `sudo ldconfig` before that works, too
On Tue, 17 Apr 2018, Om Kale wrote:
> Hey Dormando,
> I was trying to play around with memcached sasl a bit more on Ubuntu.
> I tried to use the cyrus sasl libraries.
> However, when I try to run the memcached server it gives the
Did you recompile memcached on there or copy the binary?
On Tue, 17 Apr 2018, Om Kale wrote:
> Hey Dormando,
> I was trying to play around with memcached sasl a bit more on Ubuntu.
> I tried to use the cyrus sasl libraries.
> However, when I try to run the memcached server it gives the following
