all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: 34145@debbugs.gnu.org
Subject: bug#34145: 27.0.50; Writing .authinfo needs better confirmation
Date: Thu, 10 Oct 2019 00:21:14 +0200	[thread overview]
Message-ID: <87mue9zhk5.fsf@gnus.org> (raw)
In-Reply-To: <8736pn8uw0.fsf@gmx.de> (Michael Albinus's message of "Sun, 20 Jan 2019 11:51:11 +0100")

Michael Albinus <michael.albinus@gmx.de> writes:

> A Tramp user has reported recently, that writing a password into
> .authinfo happened too easily, without proper confirmation
> request. Granted, there was a `y-or-no-p' style question, but obviously
> he has accepted w/o thinking too much. See
> <http://lists.gnu.org/archive/html/help-gnu-emacs/2019-01/msg00054.html>.
>
> Since this is sensible data, he proposes to make it harder to
> confirm. `auth-source-netrc-saver' should offer an alternative
> confirmation prompt, more like `yes-or-no-p'. Which prompt to apply
> should be configurable.

It's a multiple-choice thing:

                       (concat "(y)es, save\n"
                               "(n)o but use the info\n"
                               "(N)o and don't ask to save again\n"
                               "(e)dit the line\n"
                               "(?) for help as you can see.\n"))

So I don't think a yes-or-no-p-like action here is practical.

Anybody got an opinion?

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





  reply	other threads:[~2019-10-09 22:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-20 10:51 bug#34145: 27.0.50; Writing .authinfo needs better confirmation Michael Albinus
2019-10-09 22:21 ` Lars Ingebrigtsen [this message]
2019-10-10  5:26   ` Michael Albinus
2019-10-11  7:37     ` Lars Ingebrigtsen
2019-10-11 10:02       ` Michael Albinus
2019-10-13 18:07         ` Lars Ingebrigtsen

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=87mue9zhk5.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=34145@debbugs.gnu.org \
    --cc=michael.albinus@gmx.de \
    /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.