Ubuntu
dkimpy package

key generated by dknewkey is unparsable (upstream fix released)

  1. Jammy (22.04)
  2. Bug #2012548
Bug #2012548 reported by Tom Hendrikx
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
dkimpy (Ubuntu)
Fix Released
High
Unassigned
Jammy
Confirmed
High
Unassigned
Ubuntu jammy-updates
Kinetic
New
Undecided
Unassigned

Bug Description

In https://bugs.launchpad.net/dkimpy/+bug/1978835 a problem is reported with `dknewkey` generating keys that cannot be parsed. The problem was solved and released, but the fix is not available on ubuntu 22.04. This breaks `dknewkey` and `dkimpy-milter`.

As far as I understand the problem and fix, we need an upgraded `python3-dkim` package that understands the new key format that is generated by openssl, or we need a simple way to generate 'classic' dkim keys, which work with the parsing code of the current packaged version of `python3-dkim`.

Revision history for this message
Scott Kitterman (kitterman) wrote :

That's correct. Lunar has the fixed version, but jammy and kinetic have this issue. I'm no longer involved in Ubuntu development, so I can't help further than that, but this should be addressed in a stable release update for the LTS release (upstream author opinion).

Changed in dkimpy (Ubuntu):
importance: Undecided → High
status: New → Fix Released
Changed in dkimpy (Ubuntu Jammy):
importance: Undecided → High
status: New → Confirmed
milestone: none → jammy-updates
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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