Hi Dormando and Trond,
I think I will first try Dormando's suggestion of stunnel before delving
into changing the memcached code itself. I haven't read much about stunnel,
so will need to look into it in some detail.
Again, thanks a lot for the support. It would have been very good if I
could have
Hey,
Just to be clear: I'm completely positive you can make this work with just
the libsasl2 that comes with openwrt, you don't need to rebuild it. the
problem is you can't use sasl over an untrusted network: SASL is supposed
to be used underneath TLS or a trusted network.
Either way, try stunnel
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,
hmm. I guess so...
re: stunnel, as I detailed you still have to get the client (libmemcached)
to talk over TLS. For the server, no change.
For the client, you could prototype by having stunnel local to the client
and connect through that. so you have stunnel talking to stunnel. If
that's not some
Okcouple of follow up questions on the same:
1. Inorder to enable/set up stunnel on memcached server, I need to create
certificates using openssl. How do I execute the openssl certificate
generation on memcached server? Also, after this how could I distribute
this to client?
2. Additionally, wh
On Mon, 7 May 2018, Om Kale wrote:
> Okcouple of follow up questions on the same:1. Inorder to enable/set up
> stunnel on memcached server, I need to create certificates using openssl. How
> do I execute the openssl certificate generation on memcached server? Also,
> after this how could I d