Re: remote crash in dkim-milter currently in lenny
On Mon, Feb 09, 2009 at 03:40:21PM +0100, Marc 'HE' Brockschmidt <he@ftwca.de> wrote:
> Please upload just a fixed version of 2.6.0.dfsg-1 to unstable, then
> ping us again. A few days before the release, switching to a major new
> upstream version is not an option.
2.6.0.dfsg-2 has been uploaded; I've attached an interdiff output
between it and -1.
--
Mike Markley <mike@markley.org>
I don't believe in God because I don't believe in Mother Goose.
- Clarence Darrow
diff -u dkim-milter-2.6.0.dfsg/debian/changelog dkim-milter-2.6.0.dfsg/debian/changelog
--- dkim-milter-2.6.0.dfsg/debian/changelog
+++ dkim-milter-2.6.0.dfsg/debian/changelog
@@ -1,3 +1,11 @@
+dkim-milter (2.6.0.dfsg-2) unstable; urgency=high
+
+ * Fix SF bug #2508602, which causes a failed assertion (and therefore a
+ filter crash) when libdkim attempts to verify a message signed with a
+ revoked key.
+
+ -- Mike Markley <mike@markley.org> Thu, 12 Feb 2009 21:13:23 -0800
+
dkim-milter (2.6.0.dfsg-1) unstable; urgency=low
* New upstream version.
only in patch2:
unchanged:
--- dkim-milter-2.6.0.dfsg.orig/libdkim/dkim-tables.c
+++ dkim-milter-2.6.0.dfsg/libdkim/dkim-tables.c
@@ -218,6 +218,7 @@
{ "key granularity mismatch", DKIM_SIGERROR_GRANULARITY },
{ "key type missing", DKIM_SIGERROR_KEYTYPEMISSING },
{ "unknown key type", DKIM_SIGERROR_KEYTYPEUNKNOWN },
+ { "key revoked", DKIM_SIGERROR_KEYREVOKED },
{ NULL, -1 },
};
struct nametable *sigerrors = prv_sigerrors;
Reply to: