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

Góra strony
Delete this message
Reply to this message
Autor: admin
Data:  
Dla: exim-dev
Stare tematy: [exim-dev] [Bug 2733] New: log_file_path=syslog null-pointeer dereference breakage on local delivery with allow_insecure_taint_data patch
Temat: [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 #14 from Andreas Metzler <eximusers@???> ---
(In reply to Andreas Metzler from comment #13)
> (In reply to Heiko Schlittermann from comment #11)
> > please can you check if the issue goes away once you remove the call to
> > open_logs() from src/transports/appendfile.c


> > I did so here (based on the latest commit on exim-4.94.2+taintwarn) and now
> > logging appendfile problems to main/panic log as well as to syslog works.
>
>
> If I take taintwarn, without patch2.patch (Attachment 1383 [details] Bug
> 2733) and set
> log_file_path = :syslog
> and simply start the daemon I only get the following message in syslog, but
> not in the file log.
> Mai 13 12:58:00 argenau exim[19370]: 2021-05-13 12:58:00 exim 4.94.2 daemon
> started: pid=19370, -q30m, listening for SMTP on [127.0.0.1]:25 [::1]:25


Heiko, my guess seems to have been correct. My EDITME has
LOG_FILE_PATH=/var/log/exim4/%slog
if I comment this out (i.e. exim logs to spooldir/log unless told otherwise) I
will indeed get the expected duplicate logging with log_file_path = :syslog.

Which fits with my diagnosis in comment #12

748        else if (*log_file_path && LOG_FILE_PATH[0])


is not entered when LOG_FILE_PATH is unset.

cu Andreas

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