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

To: Ola Lundqvist <ola@inguza.com>
Cc: Brian May <bam@debian.org>, Antoine Beaupré <anarcat@orangeseeds.org>, Debian LTS <debian-lts@lists.debian.org>, security@debian.org
Subject: Re: libgcrypt11 same issue? Was: Re: [SECURITY] [DLA 1283-1] python-crypto security update
From: Salvatore Bonaccorso <carnil@debian.org>
Date: Mon, 9 Apr 2018 21:06:57 +0200
Message-id: <[🔎] 20180409190657.GA2870@eldamar.local>
Mail-followup-to: Ola Lundqvist <ola@inguza.com>, Brian May <bam@debian.org>, Antoine Beaupré <anarcat@orangeseeds.org>, Debian LTS <debian-lts@lists.debian.org>, security@debian.org
In-reply-to: <[🔎] CABY6=0kOJ88HE2Q8y+46UhYPjwZd3HyVUoZgD_EroQjFahBWAw@mail.gmail.com>
References: <[🔎] CABY6=0kOJ88HE2Q8y+46UhYPjwZd3HyVUoZgD_EroQjFahBWAw@mail.gmail.com>

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 so this has already been marked unimportant with an explanation why
we think so in the notes.

Regards,
Salvatore

Reply to:

Follow-Ups:
- Re: libgcrypt11 same issue? Was: Re: [SECURITY] [DLA 1283-1] python-crypto security update
  - From: Ola Lundqvist <ola@inguza.com>

References:
- libgcrypt11 same issue? Was: Re: [SECURITY] [DLA 1283-1] python-crypto security update
  - From: Ola Lundqvist <ola@inguza.com>

Prev by Date: libgcrypt11 same issue? Was: Re: [SECURITY] [DLA 1283-1] python-crypto security update
Next by Date: calibre / CVE-2018-7889
Previous by thread: libgcrypt11 same issue? Was: Re: [SECURITY] [DLA 1283-1] python-crypto security update
Next by thread: Re: libgcrypt11 same issue? Was: Re: [SECURITY] [DLA 1283-1] python-crypto security update
Index(es):
- Date
- Thread