Re: How to close open security issues

To: debian-mentors@lists.debian.org
Subject: Re: How to close open security issues
From: Alexander Reichle-Schmehl <tolimar@debian.org>
Date: Tue, 24 May 2011 12:46:06 +0200
Message-id: <[🔎] 4DDB8C6E.8080601@debian.org>
In-reply-to: <[🔎] 4DDA8AD1.3030806@powered-by-linux.com>
References: <[🔎] 87aaeds9y6.fsf@inspiron.ap.columbia.edu> <[🔎] BANLkTikzftkKHkAnR0+Sz1mu5QQ8pDohCg@mail.gmail.com> <[🔎] 4DDA8AD1.3030806@powered-by-linux.com>

Hi!

Am 23.05.2011 18:26, schrieb sils:

> There are a bug in BTS related with 3 of these CVEs
[..]
> I found out that It would be needed to add, also, in debian/changelog
> the mention of this bug number.

Please also contact the security team, to coordinate a securty update
for them, as it seems that the versions in oldstable and stable are
affected by those CVEs, too.


Best regards,
  Alexander

Reply to:

References:
- How to close open security issues
  - From: Nikolaus Rath <Nikolaus@rath.org>
- Re: How to close open security issues
  - From: Paul Wise <pabs@debian.org>
- Re: How to close open security issues
  - From: sils <sils@powered-by-linux.com>

Prev by Date: Re: Cannot push changes to git repo
Next by Date: Re: svn.debian.org commit: path problems
Previous by thread: Re: How to close open security issues
Next by thread: RFS: Jampal (2nd try)
Index(es):
- Date
- Thread