unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: "Stephen J. Turnbull" <stephen@xemacs.org>,
	rms@gnu.org, emacs-devel@gnu.org
Subject: Re: POP3 password in plaintext?
Date: Wed, 01 Oct 2014 16:02:12 +0200	[thread overview]
Message-ID: <m3tx3nzy57.fsf@stories.gnus.org> (raw)
In-Reply-To: <jwv4mvnzyt4.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Wed, 01 Oct 2014 09:48:48 -0400")

Stefan Monnier <monnier@iro.umontreal.ca> writes:

>> I liked Ted's suggestion about providing modeline indicators.
>
> I'd much rather just signal an error if a password is sent in the clear.
> And then provide some configuration option to indicate when it's OK to
> send the password in the clear on this connection.

Yes, sort of.

What I had planned on implementing was a way to make the user manage the
security more explicitly.  Here are the main options we need:

1) The connection is TLS, and the certificate is valid.  Everything OK;
don't ask the user for anything.

2) The connection is TLS, but the certificate can't be validated (i.e.,
self-signed certificate, which is very common on pop3/imap/smtp/nntp/etcp
connections), or it is invalid.

We then notify the user of this, display bits of the certificate, and
ask how to proceed.  The user will typically say "no, get me out of
here", "OK for this session only" or "OK always".  Emacs will then store
the choice, and store a fingerprint of the certificate, so that we can
verify that we're still making the same choice later on.

3) The connection is not TLS: Ask the user whether she really wants to
send anything unencrypted to this server, and store the choice.


It can all be done on the `open-network-stream' level. 

Somebody just has to write this thing.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no



  reply	other threads:[~2014-10-01 14:02 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-29 20:49 POP3 password in plaintext? Richard Stallman
2014-09-30  1:46 ` Stephen J. Turnbull
2014-09-30 13:31   ` Ted Zlatanov
2014-09-30 19:23   ` Richard Stallman
2014-10-01  4:00     ` Stephen J. Turnbull
2014-10-01  5:33       ` David Kastrup
2014-10-01 12:54         ` Richard Stallman
2014-10-01 13:15           ` David Kastrup
2014-10-01 17:56         ` David Caldwell
2014-10-01  5:42       ` David Caldwell
2014-10-01 13:22       ` Ted Zlatanov
2014-10-02  1:58         ` Stephen J. Turnbull
2014-10-02 17:04           ` Ted Zlatanov
2014-10-03 10:54             ` Stephen J. Turnbull
2014-10-01 13:48       ` Stefan Monnier
2014-10-01 14:02         ` Lars Magne Ingebrigtsen [this message]
2014-10-01 14:37           ` Stefan Monnier
2014-10-01 23:29           ` Ted Zlatanov
2014-09-30 14:17 ` Lars Magne Ingebrigtsen
2014-09-30 19:25   ` Richard Stallman

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=m3tx3nzy57.fsf@stories.gnus.org \
    --to=larsi@gnus.org \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=rms@gnu.org \
    --cc=stephen@xemacs.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).