From: Richard Copley <rcopley@gmail.com>
To: Noam Postavsky <npostavs@users.sourceforge.net>
Cc: 27658@debbugs.gnu.org
Subject: bug#27658: 26.0.50; response parsing hangs when using tls.el and gnutls-cli.exe on Windows
Date: Thu, 13 Jul 2017 03:42:56 +0100 [thread overview]
Message-ID: <CAPM58ogH9c96-+pC0B9Qi+P0JVJgPevk5xo0QG=LyffX1DVF0g@mail.gmail.com> (raw)
In-Reply-To: <87wp7deu0h.fsf@users.sourceforge.net>
On 12 July 2017 at 13:09, <npostavs@users.sourceforge.net> wrote:
> Richard Copley <rcopley@gmail.com> writes:
>
>>>
>>> In https://debbugs.gnu.org/cgi/bugreport.cgi?bug=23759#8 Eli said:
>>>
>>> TLS connections on MS-Windows are supported via the GnuTLS library.
>>> External TLS programs will never work correctly on Windows, since
>>> they use signals to communicate with Emacs. So there's little sense
>>> in fixing this issue, because the result will not work anyway.
>>>
>>
>> I see, thank you.
>> That's a lot of hours I'll never get back. No big deal! But a little comment
>> near the top of "tls.el", or somewhere, to let people know not to bother,
>> would be nice.
>
> Hmm, and I see that #15905 was closed as wontfix too, so it's basically
> unsupported at this point even on GNU/Linux platforms. We should mark
> it as obsolete at least, if not remove it entirely.
That's a shame, because the library-based implementation has some flaws
too. I've been trying to debug where that goes wrong, when it accepts certs
for the wrong host and self-signed certs. (Test case in Glyph's blog post.)
I didn't learn much. Never mind :)
next prev parent reply other threads:[~2017-07-13 2:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-11 22:18 bug#27658: 26.0.50; response parsing hangs when using tls.el and gnutls-cli.exe on Windows Richard Copley
2017-07-12 0:17 ` npostavs
2017-07-12 10:10 ` Richard Copley
2017-07-12 12:09 ` npostavs
2017-07-13 2:42 ` Richard Copley [this message]
2017-07-13 15:48 ` Eli Zaretskii
2017-07-13 17:06 ` Richard Copley
2017-07-14 9:16 ` 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='CAPM58ogH9c96-+pC0B9Qi+P0JVJgPevk5xo0QG=LyffX1DVF0g@mail.gmail.com' \
--to=rcopley@gmail.com \
--cc=27658@debbugs.gnu.org \
--cc=npostavs@users.sourceforge.net \
/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.