From: Yaakov Selkowitz <yselkowitz@cygwin.com>
To: cygwin-apps@cygwin.com
Subject: Re: [SECURITY] gnutls
Date: Fri, 24 Mar 2017 19:00:00 -0000 [thread overview]
Message-ID: <1c5f0c00-aaa0-e6ad-4861-52780414dbd1@cygwin.com> (raw)
In-Reply-To: <2a005d15-9f33-46e9-bd12-484702e15a52@cygwin.com>
On 2017-03-10 16:01, Yaakov Selkowitz wrote:
> On 2017-02-22 12:46, Yaakov Selkowitz wrote:
>> On 2016-09-26 14:13, Yaakov Selkowitz wrote:
>>> On 2016-09-26 02:00, Yaakov Selkowitz wrote:
>>>> Dr. Volker,
>>>>
>>>> Two security issues have been reported in GnuTLS:
>>>>
>>>> https://www.gnutls.org/security.html#GNUTLS-SA-2016-2
>>>> https://www.gnutls.org/security.html#GNUTLS-SA-2016-3
>>>>
>>>> At this point, I think the best way to proceed would be to:
>>>>
>>>> 1) release 3.3.24 with the patch for the latter, then;
>>>> 2) update to 3.4.15, which involves an ABI break.
>>>
>>> nettle is also overdue for an update (it's also blocking an update to
>>> filezilla); getting that in after 3.3.24 and prior to 3.4 would be best.
>>
>> Ping? More vulnerabilities have been announced, so we need to revise
>> the above to 3.3.26 and 3.5.9.
>
> Ping 2?
Ping 3?
--
Yaakov
next prev parent reply other threads:[~2017-03-24 19:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-26 7:00 Yaakov Selkowitz
2016-09-26 19:13 ` Yaakov Selkowitz
2017-02-22 18:46 ` Yaakov Selkowitz
2017-03-10 22:01 ` Yaakov Selkowitz
2017-03-24 19:00 ` Yaakov Selkowitz [this message]
2017-05-03 21:37 ` Yaakov Selkowitz
-- strict thread matches above, loose matches on Subject: below --
2012-03-25 2:54 Yaakov (Cygwin/X)
2012-03-26 9:30 ` Dr. Volker Zell
2012-05-02 6:01 ` Yaakov (Cygwin/X)
2012-06-27 3:34 ` Yaakov (Cygwin/X)
2009-09-15 3:59 Yaakov (Cygwin/X)
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=1c5f0c00-aaa0-e6ad-4861-52780414dbd1@cygwin.com \
--to=yselkowitz@cygwin.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).