Re: memcached broken, was: Re: Crashes with Grsecurity kernel

From: Christian Rößner <c_at_roessner-network-solutions.com>
Date: Mon, 12 Jan 2015 13:59:59 +0100

Hallo Andreas :-)

> Am 12.01.2015 um 12:55 schrieb A. Schulze <sca_at_andreasschulze.de>:
>
>
> Christian Rößner:
>
>> Hope someone will have a look at the memcached-code and find the problem
>
> Christian,
>
> for what reasons did you activate the memcache feature in opendkim?
> What's your usecase?

Well, I would expect that memcache stores some key/value pairs that it earlier retrieved from a database or whatever. In my case LDAP.

At least this is, what I always program in Python, when it comes to database connections:

This is from Python:

       key = derive_key(obj)
       obj = mc.get(key)
       if not obj:
           obj = backend_api.get(...)
           mc.set(key, obj)

What I find interesting in conjunction to OpenDKIM is that I never configured anything memcache related. So the pure binding to memcached makes OpenDKIM unstable.

I think I did what I could to point to a bug and it’s now up to the developers to fix it or not ;-)

Best wishes

Christian
--
Bachelor of Science Informatik
Erlenwiese 14, 36304 Alsfeld
T: +49 6631 78823400, F: +49 6631 78823409, M: +49 171 9905345
USt-IdNr.: DE225643613, http://www.roessner-network-solutions.com
Received on Mon Jan 12 2015 - 13:00:13 PST

This archive was generated by hypermail 2.3.0 : Mon Jan 12 2015 - 13:09:00 PST