Anybody else got this issue with dkimpy and null body?
When I receive a message signed with sha256, using relaxed/relaxed
canonicalization over a null body, the verify method comes back with:
frcCV1k9oG9oKj3dpUqdJg1PxRT2RSN/XKdLCPjaYaY (per RFC6376 3.4.3 page 16,
the result for 'simple')
though it should be:
47DEQpj8HBSa+/TImW+5JCeuQeRkm5NMpJWZG3hSuFU (per RFC6376 3.4.4 Page 17,
the result for 'relaxed').
It would trace to the dkim/canonicalization.py module. Is it a known
problem and is there a known fix?
Cheers,
Stephen Nightingale.
DKIM Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=spokenphotoapp.com; s=90273B94-8B72-11E2-ABFF-8D7FA7E411B1;
t=1363219049; bh=47DEQpj8HBSa+/TImW+5JCeuQeRkm5NMpJWZG3hSuFU=;
h=Message-ID:Date:From:MIME-Version:To:Subject:Content-Type:
Content-Transfer-Encoding;
b=y/xEunz+KOXo70Ujt8yQO0AMO/6+XTgE9mAUTRL3gHudaMkYWJh05ukJngSxfzgZu
1I8DTfBLv+AqYmrRys793jLM2/O3rswXhC2QiMJcoHJRnObPfIPtA0F/jUKUI5AtqA
YIMhNSdVet6Gpr10akChUR5oG2veuXeHVimQpcaI=
Subject: register
Reported: 1
SPFReason: sender SPF authorized
DKIMReason: body hash mismatch (got
frcCV1k9oG9oKj3dpUqdJg1PxRT2RSN/XKdLCPjaYaY=, expected
47DEQpj8HBSa+/TImW+5JCeuQeRkm5NMpJWZG3hSuFU=)
_______________________________________________
dkim-dev mailing list
dkim-dev(_at_)mipassoc(_dot_)org
http://mipassoc.org/mailman/listinfo/dkim-dev