[issue41556] hostname verification fails if hostname starts with literal IPv4

Amir Mohamadi added the comment: Seems to be solved by https://github.com/openssl/openssl/pull/16201. I guess we can close this issue. -- nosy: +Amir ___ Python tracker ___

[issue41556] hostname verification fails if hostname starts with literal IPv4

Change by Devin Bayer : -- nosy: +akvadrako ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue41556] hostname verification fails if hostname starts with literal IPv4

Christian Heimes added the comment: There is no progress on the OpenSSL bug yet. -- versions: +Python 3.10, Python 3.9 ___ Python tracker ___

[issue41556] hostname verification fails if hostname starts with literal IPv4

Christian Heimes added the comment: I filed https://github.com/openssl/openssl/issues/12649 with OpenSSL. -- ___ Python tracker ___

[issue41556] hostname verification fails if hostname starts with literal IPv4

Christian Heimes added the comment: Python uses OpenSSL's a2i_IPADDRESS() to check if the hostname is actually an IP address. I'm surprised as you that the function considers a hostname like 145.100.57.105.surf-hosted.nl as a valid IP address. --

[issue41556] hostname verification fails if hostname starts with literal IPv4

New submission from Dick Visser : I'm trying to connect to an HTTPS site with ssl.create_default_context, which implies hostname verification is done. This fails when connecting to a hostname that starts with a literal IPv4 address. Reproduce with: #!/usr/bin/env python3 import socket