ramikg added the comment:
As a side note, while the ideal solution would be for Python to expose the
appropriate API, there exists a hacky solution using ctypes:
https://github.com/ramikg/ssl-context-configurator
--
nosy: +ramikg
___
Python
Change by ramikg :
--
keywords: +patch
pull_requests: +27075
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/28728
___
Python tracker
<https://bugs.python.org/issu
New submission from ramikg :
Python 3.10 drops support for LibreSSL (as per PEP 644), but there are still a
few workarounds & mentions of LibreSSL in the source code.
The related PR cleans the code of any LibreSSL workarounds or mentions.
--
assignee: christian.heimes
components:
Change by ramikg :
--
nosy: +ramikg
nosy_count: 4.0 -> 5.0
pull_requests: +27115
pull_request: https://github.com/python/cpython/pull/28602
___
Python tracker
<https://bugs.python.org/issu
Change by ramikg :
--
nosy: +ramikg
nosy_count: 4.0 -> 5.0
pull_requests: +27116
pull_request: https://github.com/python/cpython/pull/28602
___
Python tracker
<https://bugs.python.org/issu
New submission from ramikg :
The PySSLContext struct mentions that "OpenSSL has no API to get hostflags from
X509_VERIFY_PARAM* struct. We have to maintain our own copy".
Since OpenSSL 1.1.0i added the function X509_VERIFY_PARAM_get_hostflags, this
statement is no longer true.
Beca
ramikg added the comment:
In addition to https://github.com/python/cpython/pull/28602?
What would the PR include?
--
___
Python tracker
<https://bugs.python.org/issue45
ramikg added the comment:
@komugi The same code written independently by multiple people is probably the
most effective and least cost-efficient form of code review.
@christian.heimes Of course, there is no hurry.
--
___
Python tracker
<ht
