From: Robert Pluim <rpluim@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: darael@dracon.is, tzz@lifelogs.com, 33780@debbugs.gnu.org
Subject: bug#33780: network-stream.el: network-stream-certificate always returns nil
Date: Tue, 15 Jan 2019 21:31:35 +0100 [thread overview]
Message-ID: <m2d0oxzmqg.fsf@gmail.com> (raw)
In-Reply-To: <36f7918ec93135504092dc856a4490c846f6e947.camel@dracon.is>
Eli Zaretskii <eliz@gnu.org> writes:
>> so loading nsm.el causes nsm-verify-connection to get called in the
>> ':nowait t' case. Presumably in the ':nowait nil' case gnutls-boot has
>> already completed the tls connection, and finish_after_tls_connection
>> never gets called (thatʼs speculation on my part). I donʼt know the
>> GnuTLS code well enough to know if this is a bug. Ted?
>
I can confirm this is what happens: finish_after_tls_connection only
gets called when ':nowait t'.
> Ah, okay. No, I don't think this is a bug. So use some way to get
> nsm to approve the connection.
I do find it unexpected that the low level GnuTLS code only invokes
the nsm for ':nowait t' connections. OTOH 'open-network-stream' works
fine, and uses the nsm, so itʼs not a big deal.
Overriding nsm-query appears not to be enough (itʼs enough when
running the tests interactively, but not in batch mode), I had to
override 'nsm-verify-connection'.
Robert
next prev parent reply other threads:[~2019-01-15 20:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-17 19:02 bug#33780: network-stream.el: network-stream-certificate always returns nil Vinothan Shankar
2018-12-19 17:19 ` Robert Pluim
2018-12-20 11:24 ` Vinothan Shankar
2018-12-20 18:45 ` Robert Pluim
2018-12-21 13:16 ` Robert Pluim
2019-01-09 10:48 ` Robert Pluim
2019-01-12 11:13 ` Eli Zaretskii
2019-01-14 13:27 ` Robert Pluim
2019-01-14 16:00 ` Eli Zaretskii
2019-01-14 16:25 ` Robert Pluim
2019-01-14 16:45 ` Eli Zaretskii
2019-01-14 17:40 ` Robert Pluim
2019-01-14 18:51 ` Eli Zaretskii
2019-01-15 20:31 ` Robert Pluim [this message]
2019-01-24 10:40 ` 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=m2d0oxzmqg.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=33780@debbugs.gnu.org \
--cc=darael@dracon.is \
--cc=eliz@gnu.org \
--cc=tzz@lifelogs.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.