all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Michael Welsh Duggan <mwd@md5i.com>
Cc: 321942@gmail.com, Robert Pluim <rpluim@gmail.com>,
	Eli Zaretskii <eliz@gnu.org>,
	emacs-devel@gnu.org
Subject: Re: master 91c732f: Always check for client-certificates
Date: Tue, 19 Nov 2019 08:50:12 +0100	[thread overview]
Message-ID: <87d0dopaob.fsf@gnus.org> (raw)
In-Reply-To: <87sgmkgy5b.fsf@md5i.com> (Michael Welsh Duggan's message of "Tue, 19 Nov 2019 01:48:00 -0500")

Michael Welsh Duggan <mwd@md5i.com> writes:

> Would it be difficult (or a bad idea) to make it such that the first
> time someone uses a package that might want to use .authinfo.gpg for
> private information, a separate prompt comes up asking whether people
> want to load their .authinfo.gpg this time, not this time, every time
> (and don't ask again), or never (and don't ask again)?

Yes, it's a usability stumble.  Why would opening https://fsf.org/ ask
to open your password store?  It just sounds suspicious.

Very few people use client certificates, and it's not too much to ask
those people that do to set a variable.

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



      reply	other threads:[~2019-11-19  7:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20191105084339.26687.81756@vcs0.savannah.gnu.org>
     [not found] ` <20191105084341.1496620A3C@vcs0.savannah.gnu.org>
2019-11-16  7:07   ` master 91c732f: Always check for client-certificates Dmitry Alexandrov
2019-11-17 20:32     ` Robert Pluim
2019-11-18  8:32       ` Lars Ingebrigtsen
2019-11-18  9:06         ` Robert Pluim
2019-11-18 15:38           ` Eli Zaretskii
2019-11-18 16:05             ` Robert Pluim
2019-11-18 17:11               ` Eli Zaretskii
2019-11-19  6:48               ` Michael Welsh Duggan
2019-11-19  7:50                 ` Lars Ingebrigtsen [this message]

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=87d0dopaob.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=321942@gmail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=mwd@md5i.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 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.