Bug#892272: libopenmpt0: segfaults with memcopy if loaded from external application

The issue can be fixed using 2 upstream patches: https://github.com/OpenMPT/openmpt/commit/6f8f7be5848be8c4487b1779c332b802674f6747.patch https://github.com/OpenMPT/openmpt/commit/133007530cbe737f4b56db907aa6baee0ea5b17d.patch applied to sources in this order, after recompile no segmentation

Bug#892272: libopenmpt0: segfaults with memcopy if loaded from external application

Attached full bt log of gdb and valgrind log with debug-symbols package installed Unfortunately can't test this with other applications (ffmpeg ...) bt.tar.gz Description: application/gzip

Bug#892272: libopenmpt0: segfaults with memcopy if loaded from external application

Unfortunately freeswitch (the actual application) is not available in deb archive. How can I provide addition info on this issue?

Bug#826646: Incorrect handling with initial_cwd variable

I would like to point out that this bug also affects current debian stable exim package. To verify one would need to examine exim source package for debian jessie apt-get source exim4 grep -A 8 "To be safe: change the working directory to" ./exim4-4.84.2/src/exim.c """ /* To be safe: change the

Bug#826646: Incorrect handling with initial_cwd variable

Our friends at Ubuntu released initial_cwd security patch correctly from the start. Here is a relevant change log: http://changelogs.ubuntu.com/changelogs/pool/main/e/exim4 /exim4_4.82-3ubuntu2.1/changelog "debian/patches/CVE-2016-1531-4.patch: delay chdir(/) until we opened the main config."

Bug#826646: Incorrect handling with initial_cwd variable

Package: exim4 Priority: standard Version: 4.80 Currently exim4 debian package handles CWD parameter not correctly. This fix introduced security patch to store CWD into additional variable named initial_cwd and it was applied in debian exim packages. https://bugs.exim.org/show_bug.cgi?id=1805

Bug#818897: Exim4 change CWD string to /

On Thu, 21 Apr 2016 19:30:15 +0200 Andreas Metzler wrote: > On 2016-04-20 Roman Bulakh wrote: > > On 2016-03-27 Andreas Metzler wrote: > >> On 2016-03-21 Roman Bulakh wrote: > >>> Package: exim4 > >>> Version:

Bug#819203: xinetd init script does not contain status option

Package: xinetd Version: 1:2.3.14-7.1+deb7u1 In debian 7, xinetd init script does not contain status option this is mandatory for saltstack for example, it fails to get status of service for a fix init script should be updated with following lines: status) status_of_proc -p $PIDFILE $DAEMON