From: Chris Sutcliffe <ir0nh34d@gmail.com>
To: cygwin-apps@cygwin.com
Subject: Re: SECURITY: gnutls
Date: Tue, 18 Oct 2011 00:45:00 -0000 [thread overview]
Message-ID: <CAGHJv4e_LUHRVkM6_UZMfuTeM=7-xVKm_twRyXjAGt3yz+n_zw@mail.gmail.com> (raw)
In-Reply-To: <1318790948.7624.14.camel@YAAKOV04>
On 16 October 2011 14:49, Yaakov (Cygwin/X) wrote:
> Dr. Volker Zell,
>
> gnutls 2.8.6 is susceptible to CVE-2009-3555. This has been fixed since
> 2.10.0, but the current stable releases are 2.12.11 (ABI-compatible with
> 2.8.6) and 3.0.4 (which breaks ABI compatibility). For now, please
> release 2.12.11 ASAP for all the apps currently dependent on
> libgnutls26.
Is Dr. Volker Zell still active? The last post I can find from him
was from June of last year:
http://sourceware.org/ml/cygwin/2010-06/msg00009.html
Chris
--
Chris Sutcliffe
http://emergedesktop.org
http://www.google.com/profiles/ir0nh34d
next prev parent reply other threads:[~2011-10-18 0:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-16 18:49 Yaakov (Cygwin/X)
2011-10-18 0:45 ` Chris Sutcliffe [this message]
2011-10-18 7:53 ` Corinna Vinschen
2011-10-18 17:00 ` Dr. Volker Zell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAGHJv4e_LUHRVkM6_UZMfuTeM=7-xVKm_twRyXjAGt3yz+n_zw@mail.gmail.com' \
--to=ir0nh34d@gmail.com \
--cc=cygwin-apps@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).