all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Robert Pluim <rpluim@gmail.com>
To: John Wiegley <jwiegley@gmail.com>
Cc: "N. Jackson" <nljlistbox2@gmail.com>,
	28597@debbugs.gnu.org, Richard Stallman <rms@gnu.org>
Subject: bug#28597: 26.0.60; [Security] Configure should use --without-pop by default
Date: Tue, 26 Sep 2017 11:13:38 +0200	[thread overview]
Message-ID: <87bmlx4ybh.fsf@gmail.com> (raw)
In-Reply-To: <m2r2uuu7ln.fsf@newartisans.com> (John Wiegley's message of "Mon,  25 Sep 2017 08:21:40 -0700")

John Wiegley <jwiegley@gmail.com> writes:

>>>>>> "NJ" == N Jackson <nljlistbox2@gmail.com> writes:
>
> NJ> Configure issues the following warning:
> NJ>   configure: WARNING: This configuration installs a 'movemail' program
> NJ>   that retrieves POP3 email via only insecure channels.
> NJ>   To omit insecure POP3, you can use './configure --without-pop'.
>
> NJ> If the warning is true, then --without-pop should be the default, and
> NJ> users should have to explicitly request an insecure Emacs with --with-pop.
>
> You are requesting a change in behavior that is exceedingly old, so I would
> like to hear from others what they think about making a change like this.
> Given how much less of a thing POP is becoming over the years, I'd be in favor
> of changing the default here.

I'm sure there are still people stuck with using POP3, but they should
be gently incited to move to POP3S or IMAPS the same way people should
be steered away from http and TLS < 1.2. Making the default be
--without-pop is one way to do that.

Regards

Robert





  reply	other threads:[~2017-09-26  9:13 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 [this message]
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
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87bmlx4ybh.fsf@gmail.com \
    --to=rpluim@gmail.com \
    --cc=28597@debbugs.gnu.org \
    --cc=jwiegley@gmail.com \
    --cc=nljlistbox2@gmail.com \
    --cc=rms@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.