[issue40482] _hashlib: register Python names as OpenSSL aliases

Christian Heimes added the comment: I decided against the approach. -- resolution: -> rejected stage: patch review -> resolved status: open -> closed ___ Python tracker ___ _

[issue40482] _hashlib: register Python names as OpenSSL aliases

Christian Heimes added the comment: Yes, it changes the global state of libcrypto. I consider the risk to other application slim to non-existing. Two cases are problematic: 1) an application relies on the fact that EVP_get_digestbyname("sha3_256") fails. 2) an application also uses EVP_add_

[issue40482] _hashlib: register Python names as OpenSSL aliases

Gregory P. Smith added the comment: Adding aliases in openssl is presumably process global right? Is that wise given it'd mean other openssl using c/c++ code in the process would now see the same aliases and could behave differently when used with python vs without? On Sun, May 3, 2020, 3:55 A

[issue40482] _hashlib: register Python names as OpenSSL aliases

Change by Christian Heimes : -- keywords: +patch pull_requests: +19193 pull_request: https://github.com/python/cpython/pull/19880 ___ Python tracker ___ ___

[issue40482] _hashlib: register Python names as OpenSSL aliases

New submission from Christian Heimes : Python uses valid Python identifiers for hashing algorithms while OpenSSL uses slightly different default names. For example OpenSSL uses "SHA3-256" while Python has "sha3_256". The function py_digest_by_name() in _hashopenssl.c maps from Python names to