[exim-dev] [Bug 2733] log_file_path=syslog null-pointer dere…

Top Page
Delete this message
Reply to this message
Author: admin
Date:  
To: exim-dev
Old-Topics: [exim-dev] [Bug 2733] New: log_file_path=syslog null-pointeer dereference breakage on local delivery with allow_insecure_taint_data patch
Subject: [exim-dev] [Bug 2733] log_file_path=syslog null-pointer dereference breakage on local delivery with allow_insecure_taint_data patch
https://bugs.exim.org/show_bug.cgi?id=2733

--- Comment #9 from Andreas Metzler <eximusers@???> ---
(In reply to Jeremy Harris from comment #8)
> There's nothing obviously wrong in the debug output. Unfortunately, it
> doesn't show the logging files configuration.
>
> With a minimally hacked source, taking the testsuite-specific diverts out
> of the write_syslog() routine in src/log.c I get reasonable-looking lines
> appearing in /var/log/maillog which don't appear without that hacking, for
> the same testcase, I can only assume that your config is not what you think
> or you're not running the same patch I am.
>
> The output from "exim -bP log_file_path" should show what the binary thinks
> the config is telling it.


Good evening

/usr/sbin/exim4 -bP log_file_path
log_file_path = :syslog

I am running the current debian package 4.94.2-2 , that is. 4.94.2 with these
patches:

https://salsa.debian.org/exim-team/exim4/-/tree/master/debian/patches

i.e. 4.94.2 + fixes + taintwarn + this patch (donot get mislead by the
filename, it is v2) + localscan-dlopen + minor changes

cu Andreas

--
You are receiving this mail because:
You are on the CC list for the bug.