unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: John Wiegley <jwiegley@gmail.com>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: "N. Jackson" <nljlistbox2@gmail.com>, 28597@debbugs.gnu.org
Subject: bug#28597: 26.0.60; [Security] Configure should use --without-pop by default
Date: Tue, 26 Sep 2017 11:51:59 -0700	[thread overview]
Message-ID: <m2r2ut2sz4.fsf@newartisans.com> (raw)
In-Reply-To: <acbc4442-5045-6ecf-e17c-2e007dba0f85@cs.ucla.edu> (Paul Eggert's message of "Tue, 26 Sep 2017 10:22:04 -0700")

>>>>> Paul Eggert <eggert@cs.ucla.edu> writes:

> As Glenn noted, the 'configure' message N. mentions came from an uneasy
> compromise between worry about the default lack-of-security in Emacs, and
> worry about backward compatibility (see Bug#26102). Although I favor making
> --without-pop the default, at this point it's really an issue for the two
> maintainers to decide.

I'm OK making it the default. Let's wait until Eli's back from his trip and he
can add his thoughts.

-- 
John Wiegley                  GPG fingerprint = 4710 CF98 AF9B 327B B80F
http://newartisans.com                          60E1 46C4 BD1A 7AC1 4BA2





  reply	other threads:[~2017-09-26 18:51 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-25 15:11 bug#28597: 26.0.60; [Security] Configure should use --without-pop by default N. Jackson
2017-09-25 15:21 ` John Wiegley
2017-09-26  9:13   ` Robert Pluim
2017-09-26 15:39 ` Glenn Morris
2017-09-26 17:22 ` Paul Eggert
2017-09-26 18:51   ` John Wiegley [this message]
2017-09-29 13:14     ` Eli Zaretskii
2017-09-29 14:05       ` Robert Pluim
2017-09-29 17:42         ` Eli Zaretskii
2017-09-29 20:04           ` Robert Pluim
2017-10-02 16:29             ` Robert Pluim
2017-10-02 18:23               ` Paul Eggert
2017-10-03  8:09                 ` Robert Pluim
2017-10-03 14:34                   ` Eli Zaretskii
2017-10-03 15:03                     ` Robert Pluim
2017-10-03 15:42                       ` Eli Zaretskii
2017-10-03 22:47                   ` Paul Eggert
2017-10-04  7:14                     ` Robert Pluim
2017-10-16  2:34                       ` Noam Postavsky
2017-09-29 16:07       ` N. Jackson
2017-09-29 17:53         ` Eli Zaretskii
2017-09-29 18:14           ` N. Jackson
2017-09-29 19:11             ` Eli Zaretskii
2017-10-02 17:22               ` N. Jackson
2017-10-02 17:32                 ` Eli Zaretskii
2017-10-02 18:00                   ` Paul Eggert
2017-10-02 18:47                     ` Eli Zaretskii
2017-10-02 23:20                       ` Paul Eggert
2017-10-03  2:29                         ` Eli Zaretskii
2017-10-03 14:29                         ` N. Jackson
2017-10-03 14:55                           ` Robert Pluim
2017-10-03 15:43                           ` Eli Zaretskii
2017-10-02 18:00                 ` Paul Eggert

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=m2r2ut2sz4.fsf@newartisans.com \
    --to=jwiegley@gmail.com \
    --cc=28597@debbugs.gnu.org \
    --cc=eggert@cs.ucla.edu \
    --cc=nljlistbox2@gmail.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).