unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: emacs-devel@gnu.org
Subject: Re: GnuTLS/TLS proposals for after the release
Date: Tue, 12 Jul 2016 09:52:27 -0400	[thread overview]
Message-ID: <87wpkr6k10.fsf@lifelogs.com> (raw)
In-Reply-To: m2zipuk6es.fsf@newartisans.com

On Wed, 06 Jul 2016 10:44:43 -0700 John Wiegley <jwiegley@gmail.com> wrote: 

>>>>>> Ted Zlatanov <tzz@lifelogs.com> writes:
>> They have different purposes: (1) is to make tls.el, which uses command-line
>> tunnels, more noisy by default, so users are led to the C bindings to GnuTLS
>> (gnutls.el). (2) is to disable SSLv3 in tls.el. (3) is to change the
>> variables in gnutls.el a bit to make customization and future work easier.
>> (3) is the only risky one because it affects user customizations, but I
>> think we have to bite that buller sooner or later.

JW> OK. Does anyone else have a reason to object to these changes?

We seem to have aceptance of this for the next release.

Should we enact (2) now, before the upcoming RC?

I understand the risk to the release, but OTOH there's a significant
risk to our users from shipping with an insecure setting by default.

I'm neutral on this, sorry...

Thanks
Ted




  parent reply	other threads:[~2016-07-12 13:52 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-05 21:26 GnuTLS/TLS proposals for after the release Ted Zlatanov
2016-07-06  0:32 ` John Wiegley
2016-07-06 12:21   ` Ted Zlatanov
2016-07-06 14:25     ` Ted Zlatanov
2016-07-06 17:44     ` John Wiegley
2016-07-07  8:10       ` Robert Pluim
2016-07-12 13:52       ` Ted Zlatanov [this message]
2016-07-12 22:03         ` John Wiegley
2016-07-13 14:26           ` Eli Zaretskii
2016-07-13 14:43             ` Ted Zlatanov
2016-07-20 12:04 ` Lars Ingebrigtsen
2016-07-20 12:52   ` Stefan Monnier
2016-07-20 13:00     ` Compressing ELPA (was: GnuTLS/TLS proposals for after the release) Stefan Monnier
2016-08-02 20:58       ` Compressing ELPA John Wiegley
2016-08-02 22:04         ` Rostislav Svoboda
2016-08-02 22:25           ` Robert Weiner
2016-08-03 16:08       ` Clément Pit--Claudel
2016-08-03 16:29         ` Stefan Monnier
2016-07-20 13:14     ` GnuTLS/TLS proposals for after the release Ted Zlatanov
2016-07-20 14:21       ` Paul Eggert
2016-07-25 12:48         ` Ted Zlatanov
2016-07-25 13:01           ` Ted Zlatanov
2016-07-21 14:52       ` Eli Zaretskii
2016-07-21 15:22         ` Ted Zlatanov
2016-07-21 16:00           ` Eli Zaretskii
2016-07-21 16:35             ` Ted Zlatanov
2016-07-21 17:25               ` Lars Ingebrigtsen
2016-07-21 18:46                 ` Eli Zaretskii
2016-07-22 14:38                   ` Ted Zlatanov
2016-07-22 15:23                     ` Eli Zaretskii
2016-07-23  7:44                       ` Paul Eggert
2016-07-23  7:56                         ` Eli Zaretskii
2016-07-22 14:38             ` Stefan Monnier
2016-07-22 15:22               ` Eli Zaretskii

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=87wpkr6k10.fsf@lifelogs.com \
    --to=tzz@lifelogs.com \
    --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).