dkimpy should detect bad version

Bug #1763815 reported by Scott Kitterman
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
dkimpy
Fix Released
Medium
Scott Kitterman

Bug Description

Message verification got this result:

Authentication-Results: relay02; dkim=pass (Good 2048 bit rsa-sha256
   signature) header.d=kitterman.com <email address hidden>
   header.a=rsa-sha256

At a time when the DKIM record contained:

v=DKIM1: k=rsa; h=sha256; p= ...
(note colon vice semi-colon)

Google gets this correct:

Authentication-Results: mx.google.com;
       dkim=neutral (bad version) <email address hidden> header.s=201803r header.b=ceCoNqw0;

Changed in dkimpy:
importance: Undecided → Medium
status: New → Triaged
milestone: none → 0.8.0
Changed in dkimpy:
assignee: nobody → Scott Kitterman (kitterman)
status: Triaged → Fix Committed
Revision history for this message
Scott Kitterman (kitterman) wrote :

2018-05-18 Version 0.8.0
    - Change from distutils to setuptools with entry points because it's the
      future
    - Use install_requires and extras_requires to document external
      dependencies for dkimpy (LP: #1227526)
    - Fix typo in dknewky(1) for k= tag (Thanks to Andreas Schulze for
      reporting)
    - Detect incorrect version in DKIM public key record (LP: #1763815)
    - Detect unknown algorithm in k= tag and raise an appropriate error, vice
      failing with a traceback
    - Indicate that ed25519-sha256 is no longer experimental

Changed in dkimpy:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.