registry team mailing list archive

[Jean-Baptiste Lallement <392369@xxxxxxxxxxxxxxxxxx>]

Fixed in lucid

dkimproxy (1.2-3) unstable; urgency=low

  * v1.2-1:
    - New upstream version.
    - This new version removes dkimverify and dkimsign as they are already in
    the libmail-dkim-perl package in a newer version, also now, man pages of
    dkimproxy are referencing the pages of libmail-dkim-perl (Closes: #539497).
    - Fixes the README.Debian (Closes: #534650)
    - Fixed the watch file according to the new download page.
    - Now there's a /etc/default/dkimproxy where you can decide which proxy to
    start (dkimproxy.in, dkimproxy.out or both), where you store the private
    key for outbound signing, which username to run the daemon under, and
    what domain to use for signing (Closes: #519220, #493816).
  * v1.2-2:
    - Sets the parameters back like where they was in the Lenny version.
  * v1.2-3
    - hostname -d is now the default again for outgoing signing, as it's
    otherwise breaking previous installs and that it really seems to be the
    obvious "normal" setup with _domainkey.example.com holding the key entry.

 -- Thomas Goirand <thomas@xxxxxxxxxx>  Thu, 17 Dec 2009 14:01:29 +0800


** Changed in: dkimproxy (Ubuntu)
       Status: New => Fix Released

-- 
code in README.Debian incorrect, generates bad key
https://bugs.launchpad.net/bugs/392369
You received this bug notification because you are a member of Registry
Administrators, which is the registrant for Debian.