Re: 2.7.0 broken with LDAP

From: Quanah Gibson-Mount <quanah_at_zimbra.com>
Date: Mon, 29 Oct 2012 11:34:21 -0700

--On Monday, October 29, 2012 11:02 AM -0700 Quanah Gibson-Mount
<quanah_at_zimbra.com> wrote:

> --On Monday, October 29, 2012 10:52 AM -0700 "Murray S. Kucherawy"
> <msk_at_blackops.org> wrote:
>
>> On Mon, 29 Oct 2012, Quanah Gibson-Mount wrote:
>>> Just FYI, OpenDKIM 2.7.0 won't even start when used with LDAP as the
>>> backend.
>>>
>>> I've filed
>>>
>>> <https://sourceforge.net/tracker/?group_id=269812&atid=1147701>
>>>
>>> And will update it with further information as I obtain it.
>>
>> I think this is probably related to a similar problem that was reported
>> with respect to SQL. 2.7.0 makes an attempt to catch cases where a
>> SigningTable entry is either malformed (e.g., missing fields) or includes
>> a reference to a missing or malformed KeyTable entry. That involves
>> walking the SigningTable and querying the KeyTable for matching entries.
>> In the case of SQL, an errant NULL in the table wasn't anticipated, which
>> caused a NULL dereference and a crash. A patch has already been applied
>> that fixes the SQL case, but it looks like we probably need something
>> similar for LDAP.
>>
>> I don't have an LDAP server configured locally to test this theory. Are
>> you able to at least get a complete stack trace from your crash?
>
> Yep, working on it. :)
>
> I think your guess makes sense, because by default, there is no OpenDKIM
> data in the LDAP server at all in an initial installation, so all the
> searches would come back with no results.

Hi Murray,

I'm not able to get opendkim to start w/o forking. I set Background False,
and it still forks.

(gdb) set args -x /opt/zimbra/conf/opendkim.conf -u zimbra
(gdb) run
Starting program: /opt/zimbra/opendkim-2.7.0/sbin/opendkim -x
/opt/zimbra/conf/opendkim.conf -u zimbra
[Thread debugging using libthread_db enabled]
opendkim: /opt/zimbra/conf/opendkim.conf:
ldap://zre-ldap002.eng.vmware.com:389/?DKIMSelector?sub?(DKIMIdentity=$d):
dkimf_db_open(): Connect error

Program exited with code 0116.
(gdb) bt
No stack.


--Quanah


--
Quanah Gibson-Mount
Sr. Member of Technical Staff
Zimbra, Inc
A Division of VMware, Inc.
--------------------
Zimbra ::  the leader in open source messaging and collaboration
Received on Mon Oct 29 2012 - 18:38:06 PST

This archive was generated by hypermail 2.3.0 : Mon Oct 29 2012 - 23:20:44 PST