RE: OpenDKIM Segmentation when using MySQL

From: Adam M. Jacques <adam_at_adamjacques.com>
Date: Mon, 29 Oct 2012 21:13:12 -0700

I used the example from the README.SQL file to create the DB table and
configuration file, is it not actually correct? I just applied this new
patch to a clean working copy and OpenDKIM now works again. I will do more
testing tonight, but I'm able to sign and verify emails again (including
this one, if it makes it through). Thanks.

CREATE TABLE IF NOT EXISTS `SigningKeys` (
  `id` int(10) unsigned NOT NULL AUTO_INCREMENT,
  `domain_name` varchar(255) NOT NULL,
  `selector` varchar(63) NOT NULL,
  `private_key` text NOT NULL,
  `public_key` text NOT NULL,
  `active` tinyint(1) NOT NULL DEFAULT '1',
  PRIMARY KEY (`id`),
  KEY `domain_name` (`domain_name`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8 AUTO_INCREMENT=7;

-----Original Message-----
From: Murray S. Kucherawy [mailto:msk_at_blackops.org]
Sent: Monday, October 29, 2012 8:36 PM
To: Adam M. Jacques
Cc: opendkim-users_at_lists.opendkim.org
Subject: RE: OpenDKIM Segmentation when using MySQL

On Mon, 29 Oct 2012, Adam M. Jacques wrote:
> I am mostly familiar with gdb, I'll see what kind of data I can get
> you. I have attached a copy of my gdb debugging session showing the
> application stepping through the code until the null reference in
> dkimf_db_walk(). My C skills are a bit rusty, but hopefully this will
> contain a little bit more information for you.

I think I've spotted it. Does the attached patch also fix the problem?
It does here.

(The real problem is that your KeyTable specification needs to return three
columns, but you're providing only one "keycol" value. That's now caught at
runtime rather than crashing.)

-MSK
Received on Tue Oct 30 2012 - 04:13:30 PST