From: Robert Pluim <rpluim@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 74193@debbugs.gnu.org, arstoffel@gmail.com
Subject: bug#74193: 30.0.92; noquery argument ignored when creating a TLS connection
Date: Mon, 04 Nov 2024 18:18:06 +0100 [thread overview]
Message-ID: <87bjyuor3l.fsf@gmail.com> (raw)
In-Reply-To: <86zfmfszea.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 04 Nov 2024 19:05:17 +0200")
>>>>> On Mon, 04 Nov 2024 19:05:17 +0200, Eli Zaretskii <eliz@gnu.org> said:
>> From: Robert Pluim <rpluim@gmail.com>
>> Cc: Augusto Stoffel <arstoffel@gmail.com>, 74193@debbugs.gnu.org
>> Date: Mon, 04 Nov 2024 17:38:47 +0100
>>
Eli> Robert, do you know if GnuTLS, as we use it in Emacs, supports this on
Eli> all platforms? With both :nowait and non-:nowait? More generally, I
Eli> wonder why we don't pass all the parameters to open-network-stream?
>>
>> I donʼt know if itʼs supported everywhere, I suspect the interactions
>> with :nowait could get interesting. As far as I remember,
>> `open-gnutls-stream' is supposed to be a 'simple' wrapper, which is
>> why it doesnʼt support all the keywords.
Eli> Yes. But we are going to allow more keywords, it would be good to
Eli> test them in at least the more popular configurations.
Iʼve re-read the many-headed hydra that is `open-network-stream', and
':noquery' is the only keyword that appears to be missing for
`open-gnutls-stream'. The others are only used when opening plain
connections or when upgrading plain connections to TLS (which should
be avoided if at all possible).
Iʼll see if I can find time to test. I have GNU/Linux, macOS, and if
really needed, MSWindows (I need to test the ALPN changes in any case).
Eli> In any case, the doc string should be fixed to mention :noquery.
>>
>> Which doc string? `open-gnutls-stream', after this patch?
Eli> Yes.
OK
Robert
--
next prev parent reply other threads:[~2024-11-04 17:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-03 16:27 bug#74193: 30.0.92; noquery argument ignored when creating a TLS connection Augusto Stoffel
2024-11-03 17:44 ` Eli Zaretskii
2024-11-03 18:13 ` Augusto Stoffel
2024-11-04 12:01 ` Eli Zaretskii
2024-11-04 16:38 ` Robert Pluim
2024-11-04 17:05 ` Eli Zaretskii
2024-11-04 17:18 ` Robert Pluim [this message]
2024-11-05 14:04 ` Robert Pluim
2024-11-04 16:35 ` 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
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=87bjyuor3l.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=74193@debbugs.gnu.org \
--cc=arstoffel@gmail.com \
--cc=eliz@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).