Hi,

unfortunately the maintainer of the openssl library in Python doesn't
want to take my patch.  He says that he doesn't want the burden of
supporting more functions in the API.  I'm a bit frustrated about the
whole situation, I've redone my patch over and over again for at least
six months just to receive no feedback at all and to finally be told
that it was all in vain.  If you add a comment to the merge request
saying that you also need that functionality it might help to change
his mind, but probably not.  But it would show that it's not only me
that would like to be able to use that function.

I have kept my patch up to date up to a few weeks ago so unless
something major has happened it ought to apply fairly cleanly to the
latest mainline branch of python.

https://github.com/wingel/cpython/tree/export_keying_material-master

Usually there will be conflict due to an automatically generated
checksum at the end of the file _ssl.c.h but to get around that, just
skip that part of the patch and rerun "clinic" to regenerate the
checksum.  Here's what I usually do to build and test my patch:

./configure --prefix=/opt/python-master

python3 Tools/clinic/clinic.py -f Modules/_ssl.c
Modules/clinic/_ssl.c.h
make -j24
make install

Regards,
  Christer

On Sat, 2022-03-19 at 14:32 +0000, Hans-Christoph Steiner wrote:
> 
> Hans-Christoph Steiner <hans@eds.org> added the comment:
> 
> We're working on the HTTP Transport Auth draft
> (https://www.ietf.org/archive/id/draft-schinazi-httpbis-transport-auth-05.html
> ) in the IETF that also needs this method.  I would really love to
> see this land, any advice?  If it is just a matter of updating the
> patch for the current Python, I can probably handle that.
> 
> ----------
> nosy: +eighthave
> 
> _______________________________________
> Python tracker <report@bugs.python.org>
> <https://bugs.python.org/issue37952>
> _______________________________________