unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: nljlistbox2@gmail.com (N. Jackson)
To: Eli Zaretskii <eliz@gnu.org>
Cc: jwiegley@gmail.com, Robert Pluim <rpluim@gmail.com>,
	eggert@cs.ucla.edu, 28597@debbugs.gnu.org
Subject: bug#28597: 26.0.60; [Security] Configure should use --without-pop by default
Date: Mon, 02 Oct 2017 13:22:01 -0400	[thread overview]
Message-ID: <87fub131om.fsf@moondust.localdomain> (raw)
In-Reply-To: <83mv5d5ngv.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 29 Sep 2017 22:11:44 +0300")

At 22:11 +0300 on Friday 2017-09-29, Eli Zaretskii wrote:
>
>> From: nljlistbox2@gmail.com (N. Jackson)
>> Date: Fri, 29 Sep 2017 14:14:29 -0400
>> 
>> I don't think that makes sense, does it?
>
> I hope it does, as this is what I asked for at the time, for
> reasons that did make sense to me.

Indeed. You considered broader factors than I was aware of
previously.

>> There's nothing terribly odd about my system and if the warning
>> message from config is true, then _by default_ I'm going to get
>> built an insecure Emacs.
>
> Only if you use POP3 to fetch your mail.

This raised a question in my mind (which has probably already
been considered and dealt with). When a user has an Emacs that's
configured to use an insecure movemail for POP3, when they issue a
command in Emacs that invokes it, do they get a warning from
Emacs?

Given that many users don't build their own Emacs, they'll not see
a warning from configure, so it would seem sensible for them to be
warned at run time. (Given that they won't want to be plagued with
a warning every time they check their mail, I'm thinking of a
warning that appears when a relevant command it used for the first
time, similar to the way disabled commands work.)

N.





  reply	other threads:[~2017-10-02 17:22 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
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 [this message]
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=87fub131om.fsf@moondust.localdomain \
    --to=nljlistbox2@gmail.com \
    --cc=28597@debbugs.gnu.org \
    --cc=eggert@cs.ucla.edu \
    --cc=eliz@gnu.org \
    --cc=jwiegley@gmail.com \
    --cc=rpluim@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).