Wheezy update of lame?

2017-07-11 Thread Raphael Hertzog
Dear Fabian and other maintainer(s), The Debian LTS team would like to fix the security issues which are currently open in the Wheezy version of lame: https://security-tracker.debian.org/tracker/CVE-2017-9872 https://security-tracker.debian.org/tracker/CVE-2017-9871 https://security-tracker.debian

Bug#873718: Multiple security issues (CVE-2017-12950 to CVE-2017-12954)

2017-08-30 Thread Raphael Hertzog
Source: libgig X-Debbugs-CC: t...@security.debian.org secure-testing-t...@lists.alioth.debian.org Severity: grave Tags: security Hi, the following vulnerabilities were published for libgig. See http://seclists.org/fulldisclosure/2017/Aug/39 for the initial report with reproducer files. CVE-2017

Bug#873718: Fixes for security vulnerabilities on libgig?

2017-08-30 Thread Raphael Hertzog
[ Copy to the Debian bugtracker ] Hello Christian, a few security issues have been reported against libgig: http://seclists.org/fulldisclosure/2017/Aug/39 The reproducer files are attached too: http://seclists.org/fulldisclosure/2017/Aug/att-39/poc_zip.bin I wanted to check that you were aware

About the security issues affecting mpg123 in Wheezy

2017-08-30 Thread Raphael Hertzog
Hello Sebastian, The Debian LTS team recently reviewed the security issue(s) affecting your package in Wheezy: https://security-tracker.debian.org/tracker/CVE-2017-12797 (and there are few other older issues that have been also ignored up to now) We decided that we would not prepare a wheezy secu

Bug#781806: squeeze update of das-watchdog?

2015-04-10 Thread Raphael Hertzog
Hello dear maintainer(s), the Debian LTS team would like to fix the security issues which are currently open in the Squeeze version of das-watchdog: https://security-tracker.debian.org/tracker/CVE-2015-2831 Would you like to take care of this yourself? We are still understaffed so any help is alw

The trigger in your Debian packages

2011-06-03 Thread Raphael Hertzog
Hello, you're maintaining a Debian package which provides a trigger file. Currently a package that "activates" a trigger is put in the "triggers-awaited" status where it doesn't fulfill dependencies. The trigger must first be processed and only then is the package considered as "installed". I bel