From: Jan Ypma <jan@ypmania.net>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 47321@debbugs.gnu.org
Subject: bug#47321: 27.1; gnutls.c does not handle TLS rehandshake from server
Date: Thu, 07 Jul 2022 10:48:15 +0200 [thread overview]
Message-ID: <87edyxcnm6.fsf@ypmania.net> (raw)
In-Reply-To: <871qvbb7pa.fsf@gnus.org>
Unfortunately, I don't have access to the related Azure
infrastructure directly. And, with this being a closed-source 3rd
party cloud service, they could have upgraded/changed their server
behavior and nobody would know :).
I suggest we leave the discussion open, perhaps others on Azure
that /are/ able to use GnuTLS could chime in.
Lars Ingebrigtsen <larsi@gnus.org> writes:
> Jan Ypma <jan@ypmania.nl> writes:
>
>> I'm using gnutls with a client x509 certificate to talk to an
>> https
>> server. The server is a Microsoft "Azure API Management"
>> instance,
>> which has a particular way of handling client certificates. It
>> accepts
>> an initial handshake without requesting a certificate. It then
>> awaits
>> the http "Host: " header. Only after that, it requests a
>> rehandshake
>> on the TLS layer, expecting the client to send a certificate.
>
> (I'm going through old bug reports that unfortunately weren't
> resolved
> at the time.)
>
> Would it be possible to create a complete test case for this, by
> any
> chance? Without a test case, it's difficult to start fixing
> this issue,
> but I realise that it may be difficult to set one up, since it
> requires
> certificates etc...
next prev parent reply other threads:[~2022-07-07 8:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-22 9:13 bug#47321: 27.1; gnutls.c does not handle TLS rehandshake from server Jan Ypma
2022-06-26 18:28 ` Lars Ingebrigtsen
2022-07-07 8:48 ` Jan Ypma [this message]
2022-07-07 14:44 ` 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=87edyxcnm6.fsf@ypmania.net \
--to=jan@ypmania.net \
--cc=47321@debbugs.gnu.org \
--cc=larsi@gnus.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.