dkimpy 0.9.0

Milestone information

Scott Kitterman
Release registered:
No. Drivers cannot target bugs and blueprints to this milestone.  

Download RDF metadata


Assigned to you:
No blueprints or bugs assigned to you.
No users assigned to blueprints and bugs.
No blueprints are targeted to this milestone.
No bugs are targeted to this milestone.

Download files for this release

After you've downloaded a file, you can verify its authenticity using its MD5 sum or signature. (How do I verify a download?)

File Description Downloads
download icon dkimpy-0.9.0.tar.gz (md5, sig) 0.9.0 128
last downloaded 12 weeks ago
Total downloads: 128

Release notes 

This release does not have release notes.


View the full changelog

2018-10-30 Version 0.9.0
    - Update oversigned (frozen) header field list to reduce signature
      fragility (removes 'date' and 'subject' fields from being oversigned by
      default - see usage section of README for information on how to restore
      the previous behavior)
    - Added new add_should_not for DKIM/ARC classes to prevent additional
      header fields from being signed
    - Added 'from' to should sign list (to prevent it from not being signed at
      all in the unusual event that 'from' is locally removed from the frozen
      header field set (LP: #1525048)
    - Updates for experimental ARC support:
      - Limit to rsa-sha256, rsa-sha1 not used by ARC and multi-signature
        design TBD
      - Raise error when ARC signing if i= instance limit value of 50 is
      - Specified that for ARC, Authentication-Results should not be signed
      - Added missing documentation for timestamp function dkim.arc_sign
        (LP: #1800314)
    - Fix DNS lookups to be compatible with EAI addresses in domains and
      selectors (John Levine)
    - Add type Hinting for sign and verify functions (LP: #1782596)
      (Thomas Ward)
    - PEP8 Blank Lines Style Issues (LP: #1782596)
      (Thomas Ward)
    - Python 3.7 compatibility fixup for dkim.canonicalization.
      strip_trailing_lines due to changed RE.sub() processing (LP: #1800313)

0 blueprints and 0 bugs targeted

There are no feature specifications or bug tasks targeted to this milestone. The project's maintainer, driver, or bug supervisor can target specifications and bug tasks to this milestone to track the things that are expected to be completed for the release.

This milestone contains Public information
Everyone can see this information.