From: Eli Zaretskii <eliz@gnu.org>
To: Robert Pluim <rpluim@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: open-{gnutls,network}-stream backwards compatibility
Date: Sat, 05 Jan 2019 08:58:18 +0200 [thread overview]
Message-ID: <83wonj1th1.fsf@gnu.org> (raw)
In-Reply-To: <m2y380hxaa.fsf@gmail.com> (message from Robert Pluim on Fri, 04 Jan 2019 23:29:17 +0100)
> From: Robert Pluim <rpluim@gmail.com>
> Cc: emacs-devel@gnu.org
> Date: Fri, 04 Jan 2019 23:29:17 +0100
>
> (defcustom network-stream-use-client-certificates
> "Whether to use client certificates for network connections.
>
> If set to the default value t, `open-network-stream' will
> automatically look for matching client certificates (via
> 'auth-source') for a destination server, but only if it is called
> without a :client-certificate keyword.
That "only if" is inaccurate, right? In particular, using non-nil
:client-certificate attribute will still use client certificates as
directed, right?
> Set to nil to disable this lookup globally. To disable on a
> per-connection basis specify ':client-certificate nil' when
> calling `open-network-stream'.
Sounds OK to me, provided we announce this in NEWS.
> (Now to find which custom group this goes in...)
You could make a new group, say, 'network'.
Thanks.
next prev parent reply other threads:[~2019-01-05 6:58 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-02 16:49 open-{gnutls,network}-stream backwards compatibility Robert Pluim
2019-01-02 17:04 ` Eli Zaretskii
2019-01-02 17:47 ` Robert Pluim
2019-01-02 18:07 ` Eli Zaretskii
2019-01-02 18:56 ` Robert Pluim
2019-01-04 14:06 ` Eli Zaretskii
2019-01-04 22:29 ` Robert Pluim
2019-01-05 6:58 ` Eli Zaretskii [this message]
2019-01-05 7:36 ` Robert Pluim
2019-01-05 8:40 ` Eli Zaretskii
2019-01-09 21:50 ` Robert Pluim
2019-01-10 15:53 ` Ted Zlatanov
2019-01-10 16:05 ` Eli Zaretskii
2019-01-12 11:16 ` Eli Zaretskii
2019-01-02 18:12 ` Ted Zlatanov
2019-01-02 18:30 ` Eli Zaretskii
2019-01-02 19:18 ` Ted Zlatanov
2019-01-02 19:49 ` Eli Zaretskii
2019-01-02 20:01 ` Robert Pluim
2019-01-02 20:25 ` Ted Zlatanov
2019-01-04 11:15 ` Robert Pluim
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=83wonj1th1.fsf@gnu.org \
--to=eliz@gnu.org \
--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 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.