Bug#922854: libemail-address-perl: Package is vulnerable to a DoS attack via pathological input

Package: libemail-address-perl Version: 1.908-1 Severity: normal Tags: upstream,security Dear Maintainer, the version of libemail-address-perl shipped in Stretch suffers from a DoS vulnerability that is already fixed in upstream release 1.912 (already in Buster/sid). The upstream bug is

Bug#882493: stretch-pu: package liblog-log4perl-perl/1.48-1+deb9u1

Hi, I tested the Version from Sid (liblog-log4perl-perl-1.49-1) on the QA system, where I first spotted the original issue, running current Stretch. I did not observe any problems with the fixed version. The applications used are the same as currently running in production under Jessie. Regards,

Bug#863477: redis-server: Systemd unit namespace setup can fail on ancient/strange kernels

Am 28.05.2017 um 11:13 schrieb Chris Lamb: Urgh. This makes it very difficult for me to justify this change, alas. :( It sounds like you want to get out of this old container to be honest and not spend your time and effort trying to work around all its problems and issues. (You also *want* the

Bug#863477: redis-server: Systemd unit namespace setup can fail on ancient/strange kernels

Am 27.05.2017 um 20:13 schrieb Chris Lamb: Can you elaborate more on exactly what this kernel is? eg. what version, what makes Virtuozzo special here, etc. etc. Trying to work out the scope of the problem. Unfortunately, this is a provider kernel. I don't know anything about its patches or

Bug#863477: redis-server: Systemd unit namespace setup can fail on ancient/strange kernels

Package: redis-server Version: 3:3.2.9-1 Severity: normal Dear Maintainer, I upgraded a hosted Virtuozzo container from Jessie to Stretch. After the upgrade, redis-server fails to start: May 27 12:47:44 run-parts[3349]: redis-server.service: Failed at step NAMESPACE spawning /bin/run-parts: Too

Bug#855894: liblog-log4perl-perl: Warnings with Perl 5.24 and newer when "syswrite" and "utf8" are used together

Package: liblog-log4perl-perl Version: 1.48-1 Severity: normal Tags: patch upstream Dear Maintainer, Perl 5.24 warns when syswrite is used on file handles with enabled utf8 layer. This is intentional, see https://rt.perl.org/Public/Bug/Display.html?id=125760 This affects

Bug#612402: similar issue affects /usr in Jessie

Hi, since Jessie will attempt to mount /usr in initramfs when using Systemd, this issue has somewhat broadened in scope. See the merged bug 781661. While I agree with the reasoning that UUID and LABEL are not correct for LVM volumes, and had in fact all our systems changed, this issue will still

Bug#781661: initramfs-tools: Split /usr on LVM fails when using LABEL or UUID in fstab

Package: initramfs-tools Version: 0.119 Severity: grave Justification: causes non-serious data loss Dear Maintainer, * What led up to the situation? Upgrading a system from Wheezy to Jessie. The system uses a split /usr on LVM and uses LABEL in fstab to mount this. * What exactly

Bug#776409: —Bug#767832— not fixed in cryptsetup 2:1.6.6-4 nor 2:1.6.6-5

Hi, we have most likely observed the same, or a very similar, bug when upgrading two test systems from Wheezy to Jessie. Important: We use LVM for everything but / and /boot. The default fstab looks like this: LABEL=boot /boot ext3 defaults,errors=remount-ro,noatime

Bug#762598: libswitch-perl: use Switch tries to call a method on an unblessed reference

Package: libswitch-perl Version: 2.17-1 Severity: important Hi, using Switch leads to: Can't call method filter on unblessed reference at - line 1. The test case is trivial: $ perl -MSwitch A patch seems to be available in FreeBSD: