Your message dated Wed, 14 Aug 2019 09:15:22 +0200
with message-id <20190814071522.gf1...@argenau.bebt.de>
and subject line Re: Bug#617812: exim4 security update trusted_configs silently 
ignored
has caused the Debian Bug report #617812,
regarding exim4 security update trusted_configs silently ignored
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
617812: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=617812
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: exim4-base
Version: 4.69-9+lenny4

I just did the exim4 security update and it broke my mail system
because of the new restrictions on the config file which can be used.

I tried to fix this by adding an /etc/exim4/trusted_configs file as
documented in the Debian changelog but this was not effective.

I had to obtain the source and start debugging it, at which point I
noticed the code which silently ignores the trusted_configs file if it
has the "wrong" owner or mode.

As in my previous bug report, I think the restriction is unreasonable
and should be turned off in Debian.

However, if the restriction remains in the source code for exim4 (as
it probably will) then arrangements should be made to log the fact
that the trusted_configs is being ignored and why.

Ian.



--- End Message ---
--- Begin Message ---
On 2011-03-12 Ian Jackson <ijack...@chiark.greenend.org.uk> wrote:
> Andreas Metzler writes ("Re: Bug#617812: exim4 security update 
> trusted_configs silently ignored"):
> > Silenty, quietly? I get an error in paniclog. Please provide exact
> > steps on how to reproduce.

> I'll try to do so although I'll have to set up a different test
> environment as I'd rather not break my production mail system again ...

Closing ancient report, there does not seem to be a point to keep this
open.

cu Andreas

--- End Message ---

Reply via email to