Andreas Metzler writes:
> On 2021-05-05 Andreas Metzler wrote: [...]
>> The breakage is caused by the relevant change in -18/-19 (Pull
>> patches to temporarily add an option to turn taint errors
>> into warnings.)
>
> Could you give 4.94.2-2 a spin? It should hit the mirrors in
> a couple of hour
Also 4.94.2-1 crashes, e.g. calling "exim4 -qff":
(gdb) bt
#0 0x55ebf469d87c in log_open_already_exim (name=0x7ffcc589d560 "")
at log.c:288
#1 0x55ebf469dadf in log_open_as_exim (name=name@entry=0x7ffcc589d560 "")
at log.c:416
#2 0x55ebf469de8d in open_log (fd=fd@entry=0x55e
Adam D. Barratt writes:
> On Wed, 2021-05-05 at 11:07 +0000, halfdog wrote:
>> This is weird: I have only bullseye/bullseye-updates/bullseye-
>> security
>> in my sources list. I applied all updates on 2nd of May with
>> no Exim package available. Then after the 21na
This is weird: I have only bullseye/bullseye-updates/bullseye-security
in my sources list. I applied all updates on 2nd of May with
no Exim package available. Then after the 21nails disclosure
I run the updates (timestamps in UTC):
2021-05-02 07:05:31 status installed initramfs-tools:all 0.140
...
Salvatore Bonaccorso writes:
> Hi,
>
> On Wed, May 05, 2021 at 06:58:02AM +, halfdog wrote:
>> Package: exim4-daemon-light
>> Version: 4.94-19
>> Severity: grave
>>
>> Yesterdays 21nails update causes Exim to fail delivery of any
>> messages. T
Package: exim4-daemon-light
Version: 4.94-19
Severity: grave
Yesterdays 21nails update causes Exim to fail delivery of any
messages. This might be related to using syslogging only without
any file logging configured:
Core was generated by `/usr/sbin/exim4 -Mc 1ldzSC-0001yw-RY'.
Program terminated
Package: iptables
Version: 1.8.4-2
Severity: grave
Tags: security
After upgrading from "1.8.3-2", iptables-restore handles empty
lines differently and does not restore the rules. Thus old rulesets
stored with save and then annotated for better readability (to
avoid loads of "iptables -A" calls), d
Package: nmh
Version: 1.7.1-2+deb8u1
Severity: serious
No matter which password is entered, inc will always send the
password string "(null)" to the server, thus failing authentication.
It is easily reproducible on fresh installs: First emulate a POP3
server using socat:
$ socat TCP4-LISTEN:
Package: ulogd2
Version: 2.0.4-2+deb8u1
Severity: serious
Tags: security
After a fresh install of ulogd2, logging directory has following
permissions:
# ls -al /var/log/ulog
total 8
drwxr-xr-x 2 root root 4096 Dec 3 16:22 .
drwxr-xr-x 10 root root 4096 Dec 3 16:22 ..
-rw-r--r-- 1 root root
9 matches
Mail list logo
