gnutls-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: GnuTLS CVE-2009-2730 Patches


From: Simon Josefsson
Subject: Re: GnuTLS CVE-2009-2730 Patches
Date: Sat, 15 Aug 2009 10:14:48 +0200
User-agent: Gnus/5.110011 (No Gnus v0.11) Emacs/23.1 (gnu/linux)

Jamie Strandboge <address@hidden> writes:

> On Fri, 14 Aug 2009, Simon Josefsson wrote:
>
>> I don't have time/resources to produce releases for older branches.  If
>> someone else wants to volunteer to work on fixing older releases, that
>> would be appreciated.
>> 
>
> Attached are preliminary patches for 2.4.1, 2.0.4 and 1.2.9 backported
> from the advisory[1].

Thank you!

I have applied the 2.4.x patch on the gnutls_2_4_x branch, so it will be
built and tested by the daily autobuilder from now on.  I've tested that
the nul-in-x509-names self-test works as expected with the 2.4 library.
So in theory, it should be easy for me to make a v2.4.4 release from
that branch.  I wonder if this would helps anyone, though?  I'd imagine
that most people concerned with older releases are distributions that
have to support older GnuTLS releases.  And you aren't likely to use a
new upstream release anyway, since you just apply the patches to your
version.

I'm also concerned that there have been plenty of _other_ serious
problems in these old GnuTLS releases (check the security vulnerability
page), and I haven't back-ported the fixes to those problems to these
old branches.  So if I make a release on that branch, I'd have to check
what other serious problems would needs to be fixed for that branch to
be secure -- which sounds like real work (for little gain).

For these two reasons, I'd prefer to help you establish trust in the
patches you developed rather than make releases on old branches.

I also added a link to your post on
<http://www.gnu.org/software/gnutls/security.html> so others can find it
easily.

/Simon




reply via email to

[Prev in Thread] Current Thread [Next in Thread]