Hey Dormando,
As of now only binary protocol supports SASL.
Correct me if I am wrong but to ensure compatibility with SASL and
libmemcached clients we would need binary protocol support right?
Thanks and Regards,
Om Kale
On Thu, May 9, 2019 at 2:58 PM dormando wrote:
> Yo,
>
> A
Alright...cool.
Let me know if you ever successfully get DIGEST-MD5 working.
Have a great weekend!
Thanks and Regards,
Om Kale
Master of Science in Electrical and Computer Engineering
Georgia Institute of Technology
On Fri, Mar 22, 2019 at 3:23 PM Jiuming Shao
wrote:
> Hi Om,
>
> N
Hi Jiuming,
Were you able to make it work with DIGEST-MD5 instead of just PLAIN auth?
Regards,
Om Kale
Master of Science in Electrical and Computer Engineering
Georgia Institute of Technology
On Fri, Mar 22, 2019 at 2:40 PM Jiuming Shao
wrote:
> Thanks! I figured it out by postfix
ot;, r_server->hostname());
^
Also, I observe that the common.h file does not get added in the usual
compilation path under /usr/include/lib/
Any help with this will be highly appreciated. Would I need to change
libmemcached code to view this?
Thanks and Regards,
Om Kale
On Thu, Aug 2, 2018
belongs to,
it will be easy to check the state as well during run time. So whenever,
some value fetch would give me an error, I could quickly use the key to get
the servers its stored on and go on from there.
Thanks and Regards,
Om Kale
On Thu, Aug 2, 2018 at 4:43 PM, dormando wrote:
> You h
and Regards,
Om Kale
On Thu, Aug 2, 2018 at 4:27 PM, dormando wrote:
> Why are you trying to do this? That's generally a bad sign, the
> replication is for redundancy. if you're just trying to confirm it works,
> you can do a brute force search for the key
>
> On Thu, 2 Aug 2018, Om Kale
print the hostname from the returned structure
using server->hostnamein a .c file. Can this info not be printed?Thanks and
Regards,
Om Kale
--
---
You received this message because you are subscribed to the Google Groups
"memcached" group.
To unsubscribe from this group and stop
Hi All,
I have sorted the initial problems I had with encryption and SASL auth in
memcached and things work seamlessly. I also fixed an existing issue in
libmemcached where set_encryption key was failing when we used binary
protocol. Thanks for the support.
Now, I have enabled replication (using
coding_key.html#memcached_set_encoding_key>
When I use the above with binary protocol, the value set using memcached
set and received with memcached get do not match.
Is there a specific reason why only binary protocol can be used for sasl
auth in memcached?
Thanks and Regards,
Om Kale
On Mon
, when you say 'you can modify libmemcached to use OpenSSL
directly', you mean setting up the socket connections in client to support
SSL/TLS, corect?
Thanks and Regards,
Om Kale
On Mon, May 7, 2018 at 1:11 PM, dormando <dorma...@rydia.net> wrote:
> hmm. I guess so...
>
> re
The problem with libsasl2 was regarding license. Also, I am unsure if
libsasl2 will give me an ability to perform some sort of certificate based
authentication.
One more question I had was, would the use of stunnel need any code change
with memached codebase?
Thanks and Regards,
Om Kale
On Mon
used sasl (using libsasl2) directly but because of the GPLV3
license requirements that is a problem.
I will keep you updated with my progress.
Thanks and Regards,
Om Kale
On Sat, May 5, 2018 at 4:53 PM, dormando <dorma...@rydia.net> wrote:
> > On Fri, May 4, 2018 at 10:46 PM dor
00 0x00 0x21
>28 0x00 0x00 0x00 0x7b
>28 0x00 0x02 0x00 0x00
>28 0x00 0x00 0x00 0x00
>28 0x00 0x00 0x00 0x00
<28 connection closed.
SASL (severity 5): DIGEST-MD5 common mech dispose
Thanks and Regards,
Om Kale
On Tue, Apr 17, 2018 at 7:25 PM, Om Kale <omkal...@gmail.com
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
re is a specific
reason to it and will I be able to perform the authentication without
saving the username in this format in my sasl db file.
Appreciate all the help!
Thanks and Regards,
Om Kale
On Tue, Apr 10, 2018 at 10:07 PM, Om Kale <omkal...@gmail.com> wrote:
> Hi Dormando,
>
doesnt seem to be
doing it in this case.
https://groups.google.com/d/msg/memcached/mtzcFVYahZo/ZGrX6i5FWsUJ
Regards,
Om Kale
On Tuesday, April 10, 2018 at 7:07:58 PM UTC-7, Om Kale wrote:
>
> Yes, that is correct. But if this change is done, then the entry in
> memcached.conf for sa
localhost
Set failed: AUTHENTICATION FAILURE
OKALE-M-33H5:mycode okale$
Any idea why?
Thanks and Regards,
Om Kale
On Tue, Apr 10, 2018 at 4:38 PM, dormando <dorma...@rydia.net> wrote:
> yes and yes.
>
> mkdir sasl
> cd sasl
> then created memcached.conf
> I did not c
Hi Dormando,
Thanks for the update. I will try this out now. But before this I had one
more quick question.
Did you create the sasl folder and memcached.conf manually inside
/home/dormando/ ?
Thanks and Regards,
Om Kale
On Tue, Apr 10, 2018 at 3:38 PM, dormando <dorma...@rydia.net>
/12919032/can-i-set-username-and-password-on-memcached-like-mysql
Thanks and Regards,
Om Kale
On Mon, Apr 9, 2018 at 11:58 PM, dormando <dorma...@rydia.net> wrote:
> Sorry, ran out of time today. will try for earlier tomorrow
>
> On Mon, 9 Apr 2018, Om Kale wrote:
>
> > Hi Dor
Hi Dormando,
I was just curious to know whether you were able to reproduce the above
mentioned issue?
Thanks and Regards,
Om Kale
On Mon, Apr 9, 2018 at 12:53 PM, Om Kale <omkal...@gmail.com> wrote:
> Yes, that will be very helpful Dormando. I agree, might be missing
> something.
and populated on its own.
Please do let me know the outcome once you try to reproduce it. I am
cuurently using MAC-OS high Sierra.
Thanks and Regards,
Om Kale
On Mon, Apr 9, 2018 at 12:28 PM, dormando <dorma...@rydia.net> wrote:
> Hey,
>
> I'll try to reproduce this today. I have a
code: -4
Unknown sasl response: -4
Also on client side, I still see:
OKALE-M-33H5:mycode okale$ ./testsasl ok hello localhost
Set failed: AUTHENTICATION FAILURE
One more question is:
Is there any additional info to be provided while starting the memcached
server itself?
Thanks and Regards,
Om Kal
the
memcached.conf is located at t/sasl/memcached.conf, do I need to make the
modification in this file to point to sasl db or can I create my own
memcached.conf at another location?
Thanks and Regards,
Om Kale
On Fri, Apr 6, 2018 at 5:53 PM, dormando <dorma...@rydia.net> wrote:
memcached-sasl-pwdb, need to be put?
Thanks and Regards,
Om Kale
On Fri, Apr 6, 2018 at 3:54 PM, dormando <dorma...@rydia.net> wrote:
> Read the 30 lines around where I said, not just that line.
>
> though I guess it's just:
>
> system("echo testpass | $saslpas
sasldb_path: /tmp/test-memcached.sasldb
Now, let me know what I need to doa bit confused.
Do I need to change any of the above or do I create test-memcached.sasldb
under tmp on my machine, add a username:password to it and then run
./configure followed by make?
Thanks and Regards,
Om Kale
side.
Regards,
Om Kale
On Friday, April 6, 2018 at 12:45:26 PM UTC-7, Dormando wrote:
>
> No secret in database means it thinks the pwdb is empty (or it can't
> load/find the pwdb).
>
> I'm not sure why offhand.. I can try to reproduce it but won't have time
> until later tod
't
understand why it says 'no secret in database'.
Thanks and Regards,
Om Kale
On Friday, April 6, 2018 at 12:19:17 PM UTC-7, Dormando wrote:
>
>
>
> On Fri, 6 Apr 2018, Om Kale wrote:
>
> > and then try to run my client, I get the following error on the server:
&
username:password details. If yes, what should be the location of this file
3. Do I need to install/point to any additional ssl libraries during server
bring up?
Please refer attachment for the verbose memcached server log.
Help will be much appreciated.
Thanks and Regards,
Om Kale
--
---
Y
28 matches
Mail list logo