testing bind9 for Wheezy LTS

Hi everybody, I uploaded version 9.8.4.dfsg.P1-6+nmu2+deb7u17 of bind9 to: https://people.debian.org/~alteholz/packages/wheezy-lts/bind9/amd64/ Please give it a try and tell me about any problems you met. It would be nice if you could especially test TSIG. Thanks! Thorsten *

Re: Wheezy update of ncurses?

On 2017-07-11 10:17 -0400, Roberto C. Sánchez wrote: > On Sun, Jul 09, 2017 at 03:14:33PM +0100, Chris Lamb wrote: >> The Debian LTS team would like to fix the security issues which are >> currently open in the Wheezy version of ncurses: >>

[SECURITY] [DLA 1023-1] tiff3 security update

Package: tiff3 Version: 3.9.6-11+deb7u7 CVE ID : CVE-2017-9936 Debian Bug : 866113 A vulnerabilitie has been discovered in the libtiff library and the included tools, which may result in denial of service or the execution of arbitrary code. CVE-2017-9936 A

[SECURITY] [DLA 1022-1] tiff security update

Package: tiff Version: 4.0.2-6+deb7u15 CVE ID : CVE-2017-9936 CVE-2017-10688 Debian Bug : 866113 866611 Two vulnerabilities have been discovered in the libtiff library and the included tools, which may result in denial of service or the execution of arbitrary code.

Re: Wheezy update of ncurses?

On Sun, Jul 09, 2017 at 03:14:33PM +0100, Chris Lamb wrote: > Dear maintainer(s), > > The Debian LTS team would like to fix the security issues which are > currently open in the Wheezy version of ncurses: > https://security-tracker.debian.org/tracker/source-package/ncurses > All the open

Accepted tiff3 3.9.6-11+deb7u7 (source amd64) into oldoldstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 11 Jul 2017 08:52:04 -0400 Source: tiff3 Binary: libtiff4 libtiffxx0c2 libtiff4-dev Architecture: source amd64 Version: 3.9.6-11+deb7u7 Distribution: wheezy-security Urgency: medium Maintainer: Jay Berkenbilt

Wheezy update of lucene-solr?

Dear maintainers, The Debian LTS team would like to fix the security issues which are currently open in the Wheezy version of lucene-solr: https://security-tracker.debian.org/tracker/CVE-2017-3163 Would you like to take care of this yourself? I noticed that lucene-solr is seriously out-of-date

Wheezy update of lame?

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

Re: unattended upgrades don't work in wheezy

On 09.07.17 15:41, Chris Lamb wrote: Is this https://bugs.debian.org/762965 ? I don't think so. That bug is caused by someone making changes to config file ("For extra security i have added the parameter n=wheezy.") Ah okay, thanks. Can you file a new bug against unattended-upgrades with a

Accepted jetty8 8.1.3-4+deb7u1 (source all) into oldoldstable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 10 Jul 2017 21:50:37 +0200 Source: jetty8 Binary: libjetty8-java libjetty8-java-doc libjetty8-extra-java jetty8 Architecture: source all Version: 8.1.3-4+deb7u1 Distribution: wheezy-security Urgency: high Maintainer: Debian

Wheezy update of ipsec-tools?

Hello Christian and other ipsec-tools maintainers, The Debian LTS team would like to fix the security issue which is currently open in the Wheezy version of ipsec-tools: https://security-tracker.debian.org/tracker/CVE-2016-10396 Would you like to take care of this yourself? If yes, please

About the security issues affecting catdoc in Wheezy

Hello Martin, The Debian LTS team recently reviewed the security issue(s) affecting your package in Wheezy: https://security-tracker.debian.org/tracker/CVE-2017-0 We decided that we would not prepare a wheezy security update since the impact is low and unlikely to represent a serious issue

Re: Fwd: phpldapadmin_1.2.2-5+deb7u1_amd64.changes REJECTED

Hi Markus et. al., > > This is probably obvious to someone else, but I am rather confused by > > this rejection from security-master. > > we are currently having a difficult time when we try to upload arch:all > packages to wheezy-security. For instance we receive the following message: […] FYI