Re: libgcrypt11 same issue? Was: Re: [SECURITY] [DLA 1283-1] python-crypto security update

2018-04-09 Thread Salvatore Bonaccorso
Hi Ola, On Mon, Apr 09, 2018 at 08:59:32PM +0200, Ola Lundqvist wrote: > Hi all > > I found another issue that looks very similar. It is > https://security-tracker.debian.org/tracker/CVE-2018-6594 > > Should we treat it the same way, marking it as ignored? I guess you mean CVE-2018-6829? If

libgcrypt11 same issue? Was: Re: [SECURITY] [DLA 1283-1] python-crypto security update

2018-04-09 Thread Ola Lundqvist
Hi all I found another issue that looks very similar. It is https://security-tracker.debian.org/tracker/CVE-2018-6594 Should we treat it the same way, marking it as ignored? Best regards // Ola On 9 April 2018 at 07:26, Salvatore Bonaccorso wrote: > Hi Brian, > > On Fri,

[SECURITY] [DLA 1343-1] ming security update

2018-04-09 Thread Hugo Lefeuvre
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Package: ming Version: 0.4.4-1.1+deb7u8 CVE ID : CVE-2018-6358 CVE-2018-7867 CVE-2018-7868 CVE-2018-7870 CVE-2018-7871 CVE-2018-7872 CVE-2018-7875 CVE-2018-9165 Multiple vulnerabilities have been discovered

[SECURITY] [DLA 1342-1] ldap-account-manager security update

2018-04-09 Thread Brian May
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Package: ldap-account-manager Version: 3.7-2+deb7u1 CVE ID : CVE-2018-8763 Michal Kedzior found two vulnerabilities in LDAP Account Manager, a web front-end for LDAP directories. CVE-2018-8763 The found Reflected Cross

Accepted ldap-account-manager 3.7-2+deb7u1 (source all) into oldoldstable

2018-04-09 Thread Brian May
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 04 Apr 2018 17:46:49 +1000 Source: ldap-account-manager Binary: ldap-account-manager ldap-account-manager-lamdaemon Architecture: source all Version: 3.7-2+deb7u1 Distribution: wheezy-security Urgency: high Maintainer: Roland

[SECURITY] [DLA 1283-2] python-crypto security update

2018-04-09 Thread Brian May
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Package: python-crypto Version: 2.6-4+deb7u8 This is an update to DLA-1283-1. In DLA-1283-1 it is claimed that the issue described in CVE-2018-6594 is fixed. It turns out that the fix is partial and upstream has decided not to fix