From: Noam Postavsky <npostavs@gmail.com>
To: Tara Sawyer <tara@anne.cat>
Cc: 34937@debbugs.gnu.org
Subject: bug#34937: [PATCH] update user docs for emacs-gnutls; tofu and program vs built-in
Date: Tue, 16 Apr 2019 20:23:28 -0400 [thread overview]
Message-ID: <87bm15xywv.fsf@gmail.com> (raw)
In-Reply-To: <20190321162620.85383-1-tara@anne.cat> (Tara Sawyer's message of "Thu, 21 Mar 2019 09:26:20 -0700")
Tara Sawyer <tara@anne.cat> writes:
> +To debug GnuTLS problems, first check the messages buffer, and then
> +check the function below @code{gnutls-log-level}
> +
> +If GnuTLS is not available as a built-in (@code{gnutls-available-p}
> +returns an empty list (), emacs will call out to the @code{gnutls-cli}
> +program to perform TLS connections. If you need to modify
> +the command it calls you can do this with the variable
> +@code{tls-program}.
> +For example, if you want to pin a certificate and use Trust On First
> +Use(TOFU), then something like this:
> + @code{(add-to-list 'tls-program "gnutls-cli --tofu --x509cafile %t -p
> + %p %h ")}
> + will probably serve you well.
tls.el is getting obsoleted in Emacs 27 (see Bug#31457), so I don't
think we want to add documentation about it. Basically, you should only
be using it if you really know what you're doing already.
next prev parent reply other threads:[~2019-04-17 0:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-21 16:26 bug#34937: [PATCH] update user docs for emacs-gnutls; tofu and program vs built-in Tara Sawyer
2019-04-17 0:23 ` Noam Postavsky [this message]
2019-04-17 11:06 ` Noam Postavsky
2019-04-17 11:47 ` Noam Postavsky
2019-04-17 20:22 ` Tara Anne
2019-04-17 22:32 ` Noam Postavsky
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=87bm15xywv.fsf@gmail.com \
--to=npostavs@gmail.com \
--cc=34937@debbugs.gnu.org \
--cc=tara@anne.cat \
/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.