unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Albinus <michael.albinus@gmx.de>
To: emacs-devel@gnu.org
Cc: Amin Bandali <bandali@gnu.org>
Subject: Re: master 344f769: Add support for using a TLS client certificate with 'erc-tls' (bug#47788)
Date: Mon, 10 May 2021 14:04:06 +0200	[thread overview]
Message-ID: <87tunadccp.fsf@gmx.de> (raw)
In-Reply-To: <20210423002349.50D7F20D12@vcs0.savannah.gnu.org> (Amin Bandali's message of "Thu, 22 Apr 2021 20:23:48 -0400 (EDT)")

bandali@gnu.org (Amin Bandali) writes:

Hi,

> diff --git a/doc/misc/erc.texi b/doc/misc/erc.texi
> index d635cac..45a753d 100644
> --- a/doc/misc/erc.texi
> +++ b/doc/misc/erc.texi

> +@example
> +(erc-tls :server "chat.freenode.net" :port 6697
> +         :client-certificate t)
> +@end example
> +
> +In the case of @code{:client-certificate t}, you will need to add a
> +line like the following to your authinfo file
> +(e.g. @file{~/.authinfo.gpg}):
> +
> +@example
> +machine chat.freenode.net key /home/bandali/my-cert.key cert /home/bandali/my-cert.crt
> +@end example
> +@end defun

This explains the .authinfo/.netrc case. But auth-source knows more
backends, how are they supported? I guess, this question must be
answered by the auth Info manual, so I would recommend a reference to
that manual.

> diff --git a/etc/NEWS b/etc/NEWS
> index 6fe4e98..34aeaf0 100644
> --- a/etc/NEWS
> +++ b/etc/NEWS

> +To use a certificate with 'erc-tls', specify the ':client-certificate'
> +optional parameter, whose value should be as described in the
> +documentation of 'open-network-stream': if non-nil, it should either
> +be a list where the first element is the file name of the private key
> +corresponding to a client certificate and the second element is the
> +file name of the client certificate itself to use when connecting over
> +TLS, or t, which means that 'auth-source' will be queried for the
> +private key and the certificate.
> +
> +Examples of use:
> +
> +    (erc-tls :server "chat.freenode.net" :port 6697
> +             :client-certificate
> +             '("/home/bandali/my-cert.key"
> +               "/home/bandali/my-cert.crt"))
> +
> +    (erc-tls :server "chat.freenode.net" :port 6697
> +             :client-certificate
> +             `(,(expand-file-name "~/cert-freenode.key")
> +               ,(expand-file-name "~/cert-freenode.crt")))
> +
> +    (erc-tls :server "chat.freenode.net" :port 6697
> +             :client-certificate t)
> +
> +In the case of ':client-certificate t', you will need to add a line
> +like the following to your authinfo file (e.g. "~/.authinfo.gpg"):
> +
> +    machine chat.freenode.net key /home/bandali/my-cert.key cert /home/bandali/my-cert.crt

I believe, this is too much / too detailed for etc/NEWS. A reference to
the ERC Info manual would be better.

Best regards, Michael.



       reply	other threads:[~2021-05-10 12:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20210423002348.26304.26930@vcs0.savannah.gnu.org>
     [not found] ` <20210423002349.50D7F20D12@vcs0.savannah.gnu.org>
2021-05-10 12:04   ` Michael Albinus [this message]
2021-05-11  1:45     ` master 344f769: Add support for using a TLS client certificate with 'erc-tls' (bug#47788) bandali
2021-05-11  7:19       ` Michael Albinus

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=87tunadccp.fsf@gmx.de \
    --to=michael.albinus@gmx.de \
    --cc=bandali@gnu.org \
    --cc=emacs-devel@gnu.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).