GNU bug report logs - #34937
[PATCH] update user docs for emacs-gnutls; tofu and program vs built-in

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 34937 in the body.
You can then email your comments to 34937 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Tara Sawyer <tara <at> anne.cat>
To: bug-gnu-emacs <at> gnu.org
Cc: Tara Sawyer <tara <at> anne.cat>
Subject: [PATCH] update user docs for emacs-gnutls;
 tofu and program vs built-in
Date: Thu, 21 Mar 2019 09:26:20 -0700

---
 doc/misc/emacs-gnutls.texi | 18 ++++++++++++++++++
 1 file changed, 18 insertions(+)

diff --git a/doc/misc/emacs-gnutls.texi b/doc/misc/emacs-gnutls.texi
index add79d12e4..e79174d784 100644
--- a/doc/misc/emacs-gnutls.texi
+++ b/doc/misc/emacs-gnutls.texi
@@ -93,6 +93,24 @@ There's one way to find out if GnuTLS is available, by calling
 @url{http://sourceforge.net/projects/ezwinports/files/} thanks to Eli
 Zaretskii) in the same directory as Emacs, you should be OK.
 
+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.
+
+
+
+@section Functions and Variables
+
 @defun gnutls-available-p
 This function returns non-@code{nil} if GnuTLS is available in this
 instance of Emacs, @code{nil} otherwise.  If GnuTLS is available, the
-- 
2.21.0

Message #8 received at 34937 <at> debbugs.gnu.org (full text, mbox):

From: Noam Postavsky <npostavs <at> gmail.com>
To: Tara Sawyer <tara <at> anne.cat>
Cc: 34937 <at> debbugs.gnu.org
Subject: Re: bug#34937: [PATCH] update user docs for emacs-gnutls;
 tofu and program vs built-in
Date: Tue, 16 Apr 2019 20:23:28 -0400

Tara Sawyer <tara <at> 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.

Message #11 received at 34937 <at> debbugs.gnu.org (full text, mbox):

From: Noam Postavsky <npostavs <at> gmail.com>
To: 34937 <at> debbugs.gnu.org
Cc: Tara Anne <tara <at> anne.cat>
Subject: Re: bug#34937: [PATCH] update user docs for emacs-gnutls;
 tofu and program vs built-in
Date: Wed, 17 Apr 2019 07:06:12 -0400

[Message part 1 (text/plain, inline)]

[forwarding to list, please use "Reply All" to keep 34937 <at> debbugs.gnu.org on Cc]

[Message part 2 (message/rfc822, inline)]

From: Tara Anne <tara <at> anne.cat>
To: Noam Postavsky <npostavs <at> gmail.com>
Subject: Re: bug#34937: [PATCH] update user docs for emacs-gnutls; tofu and program vs built-in
Date: Tue, 16 Apr 2019 19:06:25 -0700

Well I have no idea what I’m doing, and was forced to learn it.
But if it’s getting obsoleted, then I agree with you.

Thanks for responding!

Message #14 received at 34937 <at> debbugs.gnu.org (full text, mbox):

From: Noam Postavsky <npostavs <at> gmail.com>
To: 34937 <at> debbugs.gnu.org
Cc: Tara Anne <tara <at> anne.cat>
Subject: Re: bug#34937: [PATCH] update user docs for emacs-gnutls;
 tofu and program vs built-in
Date: Wed, 17 Apr 2019 07:47:08 -0400

> From: Tara Anne <tara <at> anne.cat>
> Well I have no idea what I’m doing, and was forced to learn it.

Do you mean the builtin gnutls-based functions aren't working for you?

Message #17 received at 34937 <at> debbugs.gnu.org (full text, mbox):

From: Tara Anne <tara <at> anne.cat>
To: Noam Postavsky <npostavs <at> gmail.com>
Cc: 34937 <at> debbugs.gnu.org
Subject: Re: bug#34937: [PATCH] update user docs for emacs-gnutls;
 tofu and program vs built-in
Date: Wed, 17 Apr 2019 13:22:57 -0700

They were not compiled in to my binary release of emacs. No idea why.
Rather than re-compile I opted to just call out,
Hence this patch.


On Apr 17, 2019, at 4:47 AM, Noam Postavsky <npostavs <at> gmail.com> wrote:

>> From: Tara Anne <tara <at> anne.cat>
>> Well I have no idea what I’m doing, and was forced to learn it.
> 
> Do you mean the builtin gnutls-based functions aren't working for you?
> 

Message #20 received at 34937 <at> debbugs.gnu.org (full text, mbox):

From: Noam Postavsky <npostavs <at> gmail.com>
To: Tara Anne <tara <at> anne.cat>
Cc: 34937 <at> debbugs.gnu.org
Subject: Re: bug#34937: [PATCH] update user docs for emacs-gnutls;
 tofu and program vs built-in
Date: Wed, 17 Apr 2019 18:32:24 -0400

tags 34937 wontfix
close 34937
quit

Tara Anne <tara <at> anne.cat> writes:

> They were not compiled in to my binary release of emacs. No idea why.
> Rather than re-compile I opted to just call out,

Ah, well, you might want to look into getting gnutls working,
considering using the external binary can hit bugs like #15905
"url-copy-file sometimes silently downloads garbage or incomplete file"

Anyway, I'm closing this bug report as wontfix, for reasons mentioned
upthread.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.