code in README.Debian incorrect, generates bad key
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
dkimproxy (Debian) |
Fix Released
|
Unknown
|
|||
dkimproxy (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: dkimproxy
At the bottom of README.Debian there is some code that suggests it will generate the DKIM DNS entry. This code needs an additionl backslash before the n on the first line. Either that, or just single-quote the \n like '\n'. Without this change, the resulting key is messed up.
ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 8.10
Package: dkimproxy 1.0.1-6
PackageArchitec
ProcEnviron:
SHELL=/bin/zsh
LANG=en_US.UTF-8
PATH=/
SourcePackage: dkimproxy
Uname: Linux 2.6.27-14-generic i686
Changed in dkimproxy (Debian): | |
status: | Unknown → New |
Changed in dkimproxy (Debian): | |
status: | New → Fix Released |
Fixed in lucid
dkimproxy (1.2-3) unstable; urgency=low
* v1.2-1: dkimproxy where you can decide which proxy to example. com holding the key entry.
- 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/
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.
-- Thomas Goirand <email address hidden> Thu, 17 Dec 2009 14:01:29 +0800