Bug#688986: init script of Debian package of dkimproxy do not parse/read /etc/dkimproxy/dkimproxy_out.conf
❦ 28 septembre 2012 12:01 +0800, Thomas Goirand :
> I believe the problem you are facing is that the init script
> uses --conf_file ${DKOUT_CONF} when it should really be using:
> --conf_file=${DKOUT_CONF} (eg = sign instead of space). This has
> already been fixed in the SID version, only the stable version of this
> package doesn't have the fix, but it certainly does not "renders
> package unusable".
I am a bit unsure since I am still using 1.2-6, but some arguments are
overriding the configuration file. For example, in my configuration
file (dkimproxy_out.conf), I have several domains, but since on the
command line, only one domain is used, the other domains are ignored.
Suppose my domain name is X and I have in dkimproxy_out.conf:
domain X,Y,Z
Then, dkimproxy is run with --domain=X
--conf_file=/etc/dkimproxy/dkimproxy_out.conf and when I send an email
From "alfred@Y", dkimproxy will sign with domain=X and not domain=Y.
Removing the --domain from command line fixes the problem for me. I see
the init.d script still do that in 1.4.1-3 but I don't know if dkimproxy
now favors the configuration file or not.
--
Many a writer seems to think he is never profound except when he can't
understand his own meaning.
-- George D. Prentice
signature.asc
Description: PGP signature
Bug#688986: init script of Debian package of dkimproxy do not parse/read /etc/dkimproxy/dkimproxy_out.conf
On 09/28/2012 03:18 PM, Raif Tolga Korkunçkaya wrote: I did not notice that the bug is because of a typo in the init script as you have mentioned, it was not in the debian bug list. This bug makes the package unusable for the ones that did not notice this bug in terms of successful signing of mails, *but i agree, the package is usable if you change cert paths*. No, the package is usable also without the change in the init script, it will then just use it's default ports. Anyway, this is fixed in Wheezy. And if you feel like you have time to fix it in stable proposed-updates, please go ahead and make an upload happen there. Cheers, Thomas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#688986: init script of Debian package of dkimproxy do not parse/read /etc/dkimproxy/dkimproxy_out.conf
Hi Thomas,
if you figure out that dkimproxy is not using the conf files
/etc/dkimproxy/dkimproxy_*.conf than you can change the certificate paths
accordingly. Other than this, it uses the "wrong/default" certificate files
and the signature and dns entry does not match and you always get
dkim=hardfail.
I did not notice that the bug is because of a typo in the init script as
you have mentioned, it was not in the debian bug list. This bug makes the
package unusable for the ones that did not notice this bug in terms of
successful signing of mails, *but i agree, the package is usable if you
change cert paths*.
2012/9/28 Thomas Goirand
>
> Hi,
>
> On 09/28/2012 05:03 AM, R. Tolga Korkunckaya wrote:
>
>> Severity: grave
>> Justification: renders package unusable
>>
>
> I can't agree that this "renders package unusable". I've been using
> dkimproxy in hundreds of servers without problem. I don't think this is an
> RC bug (eg: severity normal would be more appropriate).
>
> init script of Debian package of dkimproxy do not parse/read
>> /etc/dkimproxy/dkimproxy_out.**conf to override default settings,
>> it reads /etc/default/dkimproxy file only. However, this is not
>> written in Debian.README file of the package.
>> In dkimproxy docs these overrides are addressed to the
>> /etc/dkimproxy/dkimproxy_in.**conf and /etc/dkimproxy/dkimproxyoutn.**
>> conf
>>
>
> I believe the problem you are facing is that the init script
> uses --conf_file ${DKOUT_CONF} when it should really be using:
> --conf_file=${DKOUT_CONF} (eg = sign instead of space). This has already
> been fixed in the SID version, only the stable version of this package
> doesn't have the fix, but it certainly does not "renders package unusable".
>
> Cheers,
>
> Thomas
>
Bug#688986: init script of Debian package of dkimproxy do not parse/read /etc/dkimproxy/dkimproxy_out.conf
Hi,
On 09/28/2012 05:03 AM, R. Tolga Korkunckaya wrote:
Severity: grave
Justification: renders package unusable
I can't agree that this "renders package unusable". I've been using
dkimproxy in hundreds of servers without problem. I don't think this is
an RC bug (eg: severity normal would be more appropriate).
init script of Debian package of dkimproxy do not parse/read
/etc/dkimproxy/dkimproxy_out.conf to override default settings,
it reads /etc/default/dkimproxy file only. However, this is not
written in Debian.README file of the package.
In dkimproxy docs these overrides are addressed to the
/etc/dkimproxy/dkimproxy_in.conf and /etc/dkimproxy/dkimproxyoutn.conf
I believe the problem you are facing is that the init script
uses --conf_file ${DKOUT_CONF} when it should really be using:
--conf_file=${DKOUT_CONF} (eg = sign instead of space). This has already
been fixed in the SID version, only the stable version of this package
doesn't have the fix, but it certainly does not "renders package unusable".
Cheers,
Thomas
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#688986: init script of Debian package of dkimproxy do not parse/read /etc/dkimproxy/dkimproxy_out.conf
Package: dkimproxy Version: 1.2-6 Severity: grave Tags: upstream Justification: renders package unusable init script of Debian package of dkimproxy do not parse/read /etc/dkimproxy/dkimproxy_out.conf to override default settings, it reads /etc/default/dkimproxy file only. However, this is not written in Debian.README file of the package. In dkimproxy docs these overrides are addressed to the /etc/dkimproxy/dkimproxy_in.conf and /etc/dkimproxy/dkimproxyoutn.conf -- System Information: Debian Release: 6.0.5 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages dkimproxy depends on: ii adduser3.112+nmu2add and remove users and groups ii liberror-perl 0.17-1Perl module for error/exception ha ii libmail-dkim-perl 0.38-1cryptographically identify the sen ii libnet-server-perl 0.97-1An extensible, general perl server ii libtext-wrapper-perl 1.02-1Simple word wrapping routine ii lsb-base 3.2-23.2squeeze1 Linux Standard Base 3.2 init scrip ii openssl0.9.8o-4squeeze13 Secure Socket Layer (SSL) binary a ii perl 5.10.1-17squeeze3 Larry Wall's Practical Extraction ii ssl-cert 1.0.28simple debconf wrapper for OpenSSL Versions of packages dkimproxy recommends: pn amavisd-new(no description available) dkimproxy suggests no packages. -- Configuration Files: /etc/default/dkimproxy changed [not included] /etc/dkimproxy/dkimproxy_in.conf [Errno 2] No such file or directory: u'/etc/dkimproxy/dkimproxy_in.conf' /etc/dkimproxy/dkimproxy_out.conf changed [not included] -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
