From: Dmitry Alexandrov <321942@gmail.com>
To: emacs-devel@gnu.org
Cc: Robert Pluim <rpluim@gmail.com>
Subject: Re: master 91c732f: Always check for client-certificates
Date: Sat, 16 Nov 2019 10:07:52 +0300 [thread overview]
Message-ID: <imnks3hz.321942@gmail.com> (raw)
In-Reply-To: <20191105084341.1496620A3C@vcs0.savannah.gnu.org> (Robert Pluim's message of "Tue, 5 Nov 2019 03:43:40 -0500 (EST)")
[-- Attachment #1: Type: text/plain, Size: 997 bytes --]
rpluim@gmail.com (Robert Pluim) wrote:
> branch: master
> commit 91c732f687a61ba130acf38d5142bec6369ebd68
> Author: Robert Pluim <rpluim@gmail.com>
> Commit: Robert Pluim <rpluim@gmail.com>
>
> Always check for client-certificates
>
> * lisp/net/network-stream.el
> (network-stream-use-client-certificates): New user option.
> (open-network-stream): If 'network-stream-use-client-certificates'
> is t, and the user hasn't specified :client-certificate, do
> certificate lookups via 'auth-source'.
> (network-stream-certificate): Only return key and certificate
> files that exist.
From userʼs point of view it means: M-x eww RET https://gnu.org or M-x list-packages or something else equally anonymous by nature may eventually request a passphrase to decrypt private GPG key (that one, which was used to encrypt ~/.authinfo.gpg), and fail if request is rejected.
Iʼm afraid, this deeply violates the principle of the least astonishment.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 511 bytes --]
next parent reply other threads:[~2019-11-16 7:07 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 ` Dmitry Alexandrov [this message]
2019-11-17 20:32 ` master 91c732f: Always check for client-certificates 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
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=imnks3hz.321942@gmail.com \
--to=321942@gmail.com \
--cc=emacs-devel@gnu.org \
--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).