From: Glenn Morris <rgm@gnu.org>
To: emacs-devel@gnu.org
Subject: Re: proposal: require GnuTLS 3.1.x (previous stable)
Date: Sat, 29 Nov 2014 15:02:53 -0500 [thread overview]
Message-ID: <ofppc5srki.fsf@fencepost.gnu.org> (raw)
In-Reply-To: 87bnnr40qo.fsf@lifelogs.com
Ted Zlatanov wrote:
> "Whether you need to support gnutls 2.12.x is up to you. However, I note
> that this version is totally unsupported, if it is broken or has a
> critical bug you are on your own."
Unsupported by _upstream_ gnutls.
However, it is part of the function of LTS distributions to backport
security patches to the versions that they include (or if that is
impossible to update to newer versions). Eg I can assure you that this
is what Red Hat will do for RHEL6 (it was in the context of RHEL6 that
this issue first came up). Debian security, Ubuntu LTS, they all do the
same kind of thing.
It's not Emacs's problem, and not your problem, to worry about these things.
Emacs should just (generally speaking) support whatever library versions
the commonly used distributions support, and let the distributions worry
about security issues in those libraries.
next prev parent reply other threads:[~2014-11-29 20:02 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-23 18:38 Build failure (master; MS-Windows) Dani Moncayo
2014-11-23 21:41 ` Dani Moncayo
2014-11-23 22:07 ` Lars Magne Ingebrigtsen
2014-11-23 22:52 ` Dani Moncayo
2014-11-23 22:57 ` Lars Magne Ingebrigtsen
2014-11-23 23:09 ` Dani Moncayo
2014-11-25 9:32 ` proposal: require GnuTLS 3.1.x (previous stable) (was: Build failure (master; MS-Windows)) Ted Zlatanov
2014-11-25 15:57 ` proposal: require GnuTLS 3.1.x (previous stable) Lars Magne Ingebrigtsen
2014-11-25 16:28 ` Ted Zlatanov
2014-11-25 16:38 ` Buildbot for Emacs? (was: proposal: require GnuTLS 3.1.x (previous stable)) Lars Magne Ingebrigtsen
2014-11-25 16:50 ` Buildbot for Emacs? Glenn Morris
2014-11-25 16:55 ` Ted Zlatanov
2014-11-25 22:15 ` Glenn Morris
2014-11-25 23:12 ` Ted Zlatanov
2014-11-26 9:52 ` Tom
2014-11-25 17:05 ` Lars Magne Ingebrigtsen
2014-11-25 22:14 ` Glenn Morris
2014-11-25 17:34 ` proposal: require GnuTLS 3.1.x (previous stable) Stefan Monnier
2014-11-25 18:55 ` Ivan Shmakov
2014-11-26 9:14 ` Peder O. Klingenberg
2014-11-26 12:57 ` Ivan Shmakov
2014-11-26 13:47 ` Peder O. Klingenberg
2014-11-26 13:08 ` Ted Zlatanov
2014-11-26 14:12 ` Peder O. Klingenberg
2014-11-26 15:42 ` Stefan Monnier
2014-11-26 16:52 ` Ted Zlatanov
2014-11-26 21:18 ` Ted Zlatanov
2014-11-26 21:37 ` Lars Magne Ingebrigtsen
2014-11-27 2:13 ` Stefan Monnier
2014-11-27 2:33 ` Ted Zlatanov
2014-11-28 18:51 ` Ted Zlatanov
2014-11-28 19:31 ` Stefan Monnier
2014-11-29 20:02 ` Glenn Morris [this message]
2014-11-26 13:46 ` Michael Welsh Duggan
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ofppc5srki.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=emacs-devel@gnu.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).