From: Hubert Chathi <hubert@uhoreg.ca>
To: help-gnu-emacs@gnu.org
Subject: Re: gnutls-verify-error issues
Date: Tue, 12 Jul 2016 23:08:54 -0400 [thread overview]
Message-ID: <8737ne1bg9.fsf@desiato.home.uhoreg.ca> (raw)
In-Reply-To: 87r3az6jna.fsf@lifelogs.com
On Tue, 12 Jul 2016 10:00:41 -0400, Ted Zlatanov <tzz@lifelogs.com> said:
> I am not aware of any code in Emacs that would modify
> `gnutls-verify-error' and haven't seen this issue. But it could be a
> bug. In particular this line *could* be the cuplrit in gnutls.el:
> (when verify-hostname-error (push :hostname verify-error))
> Are you able to put a debug statement in there and try again?
I changed those lines to:
(when verify-hostname-error
(message "hostname error")
(push :hostname verify-error))
But there was no extra message in *Messages*.
But then I tried modifying the lambda in the (let* ... (verify-error
...)) expression in gnutls-negotiate to read
(lambda (check)
(when (string-match (car check) hostname)
(copy-sequence (cdr check))))
(I added the copy-sequence call), and now it seems to be working as it
should, so it looks like *something* in that function is modifying the
value.
> Or give a recipe to duplicate the issue?
For me, just setting the value of gnutls-verify-error to (("muchlearning\\.org"
(:trustfiles))
("news\\.gmane\\.org" nil
(:trustfiles :hostname))
(".*"
(:trustfiles :hostname))), and then accessing news.gmane.org in Gnus
via NNTP over TLS results in the value of gnutls-verify-error changing.
--
Hubert Chathi - Email/Jabber: hubert@uhoreg.ca - https://www.uhoreg.ca/
PGP/GnuPG key: 4096R/113A1368 (Key available at pool.sks-keyservers.net)
Fingerprint: F24C F749 6C73 DDB8 DCB8 72DE B2DE 88D3 113A 1368
next prev parent reply other threads:[~2016-07-13 3:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1147.1468287386.26859.help-gnu-emacs@gnu.org>
2016-07-12 1:48 ` gnutls-verify-error issues Emanuel Berg
2016-07-12 14:00 ` Ted Zlatanov
2016-07-13 3:08 ` Hubert Chathi [this message]
2016-07-12 1:35 Hubert Chathi
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=8737ne1bg9.fsf@desiato.home.uhoreg.ca \
--to=hubert@uhoreg.ca \
--cc=help-gnu-emacs@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 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.