Package: dkimproxy Version: 1.2-5 Severity: grave Tags: patch I'm sending a bug repport against my own package, so that this wont be forgotten along the way.
Since I have integrated the private/public key-pair of dkimproxy in the ssl-cert system, the private key is owned by root:ssl-cert, with the dkimproxy being on the ssl-cert group. Unfortunately, this doesn't work, and dkimproxy doesn't have access to it's own key. The solution is rather simple: have the private key being owned by the dkimproxy user, which can be easily corrected in the postinst script. As I have a bunch of small fixes to upload in many of my packages, I can't promiss to do this right away now. If anyone with some time to spare sees this, feel free to NMU a fix with chown dkimproxy:ssl-cert instead of chown root:ssl-cert in debian/postinst. However, I really think that I'll be able to fix this pretty soon, since this has been investigated and tested correctly by some users of the package. Thomas -- System Information: Debian Release: 5.0.5 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-4-xen-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
