unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Christoph Scholtes <cschol2112@googlemail.com>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: Ted Zlatanov <tzz@lifelogs.com>, Eli Zaretskii <eliz@gnu.org>,
	Emacs-Devel devel <emacs-devel@gnu.org>
Subject: Re: bug#10612: GnuTLS bundled with the windows Emacs binaries
Date: Sun, 29 Jan 2012 10:08:47 -0700	[thread overview]
Message-ID: <4F257D1F.5050105@gmail.com> (raw)
In-Reply-To: <CAAeL0SRz0qWZKEW4y05Kp1V2swDSY1HkwQ_XjQWV5GHPaYnMfQ@mail.gmail.com>

On 1/29/2012 9:47 AM, Juanma Barranquero wrote:

>> I agree with
>> Juanma who IIRC said that we are providing an _Emacs binary distribution_.
>
> Yes, and only because we're sort of forced to do it.

Why is that?

> Apart from politics, the other reason against (whether other people
> finds it compelling or not, I don't know), is that including the
> binary means taking responsibility. For example, to release security
> upgrades as soon as possible, at least for serious bugs. That also
> means monitoring the GnuTLS lists (or security bulletins). Which is
> currently done, I think, but what if the people doing it suddently
> lacks time or just moves to other pursuits? It's easy to start
> distributing the GnuTLS DLLs, harder to stop doing it.

I agree, but doesn't that also start with compiling support for GnuTLS 
into the prebuilt Emacs? Don't we start taking responsibility at that 
point? If there is a security update for GnuTLS that requires the user 
to use the latest certain version, don't we have to provide support for 
the latest version in the binary? Assuming that you can't use the fixed 
binary with the previous versions headers, that is.

Christoph



  reply	other threads:[~2012-01-29 17:08 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <84boromyob.fsf@tum.de>
     [not found] ` <m3lipk5scv.fsf@stories.gnus.org>
     [not found]   ` <84ipknew07.fsf@tum.de>
     [not found]     ` <87ipjzs512.fsf@gnus.org>
2012-01-26 15:44       ` bug#10612: GnuTLS bundled with the windows Emacs binaries (was: bug#10215: 24.0.92; Can't contact nnimap (gnutls-cli not found)) Ted Zlatanov
2012-01-26 15:15         ` Juanma Barranquero
2012-01-26 19:32           ` bug#10612: GnuTLS bundled with the windows Emacs binaries Ted Zlatanov
2012-01-26 19:36             ` [h-e-w] " Eli Zaretskii
2012-01-26 21:07               ` Ted Zlatanov
2012-01-26 21:39                 ` Eli Zaretskii
2012-01-27 15:59                   ` Ted Zlatanov
2012-01-27 15:30                     ` Juanma Barranquero
2012-01-30 12:59                       ` Ted Zlatanov
2012-01-27 15:45                     ` Eli Zaretskii
2012-01-26 22:53                 ` Juanma Barranquero
2012-03-17 15:41           ` Uday S Reddy
2012-03-17 18:11             ` Eli Zaretskii
2012-03-22 18:38             ` Lars Magne Ingebrigtsen
2014-12-08 20:05           ` Lars Magne Ingebrigtsen
2014-12-08 20:31             ` Drew Adams
2014-12-08 20:50             ` Eli Zaretskii
2014-12-08 20:56               ` Lars Magne Ingebrigtsen
2014-12-08 21:10                 ` Óscar Fuentes
2014-12-08 21:24                   ` Lars Magne Ingebrigtsen
2016-02-05  7:28                 ` Lars Ingebrigtsen
2012-01-29 16:00         ` Christoph Scholtes
2012-01-29 16:47           ` Juanma Barranquero
2012-01-29 17:08             ` Christoph Scholtes [this message]
2012-01-29 17:26               ` Juanma Barranquero
2012-01-30  1:00                 ` Chong Yidong
2012-01-30 12:53                   ` Ted Zlatanov
2012-01-29 17:05           ` Eli Zaretskii
2012-01-30 13:07           ` Ted Zlatanov
2012-01-30 13:18             ` Juanma Barranquero

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=4F257D1F.5050105@gmail.com \
    --to=cschol2112@googlemail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=lekktu@gmail.com \
    --cc=tzz@lifelogs.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.
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).