Wheezy update of python2.6, python2.7?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer(s), The Debian LTS team would like to fix the security issues which are currently open in the Wheezy version of python2.6, python2.7: https://security-tracker.debian.org/tracker/CVE-2018-130 Would you like to take care of this

Wheezy update of simplesamlphp ?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer(s), The Debian LTS team would like to fix the security issues which are currently open in the Wheezy version of simplesamlphp: https://security-tracker.debian.org/tracker/CVE-2017-18121

bind9: CVE-2017-3139 affects debian too

Hello LTS team, please have a look at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889285 I think it is the same bug as CVE-2017-3139 which was considered to affect only RedHat, but it seems to affect debian wheezy too. Please check if it is possible to apply the same fixes as RedHat

Wheezy update of python-crypto?

Dear maintainer, The Debian LTS team would like to fix the security issues which are currently open in the Wheezy version of python-crypto: https://security-tracker.debian.org/tracker/CVE-2018-6594 Would you like to take care of this yourself? If yes, please follow the workflow we have defined

Wheezy update of dokuwiki?

Dear maintainers, The Debian LTS team would like to fix the security issues which are currently open in the Wheezy version of dokuwiki: https://security-tracker.debian.org/tracker/CVE-2017-18123 Would you like to take care of this yourself? If yes, please follow the workflow we have defined

Re: Wheezy update of simplesamlphp?

Hi Sorry for the duplicate. I did not realize that someone else had sent this message already. // Ola On 3 February 2018 at 21:14, Ola Lundqvist wrote: > Dear maintainer, > > The Debian LTS team would like to fix the security issues which are > currently open in the Wheezy

Wheezy update of dojo?

Dear maintainers, The Debian LTS team would like to fix the security issues which are currently open in the Wheezy version of dojo: https://security-tracker.debian.org/tracker/CVE-2018-6561 Would you like to take care of this yourself? If yes, please follow the workflow we have defined here: