Windows support for OpenSSL 3.0

[jay0lee]

BPO	46570
Nosy	@pfmoore, @tiran, @tjguk, @zware, @zooba

^{Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.}

Show more details

GitHub fields:

assignee = 'https://github.com/zooba'
closed_at = None
created_at = <Date 2022-01-29.13:35:11.638>
labels = ['expert-SSL', 'type-feature', 'OS-windows', 'build', '3.11']
title = 'Windows support for OpenSSL 3.0'
updated_at = <Date 2022-01-29.17:23:26.797>
user = 'https://bugs.python.org/jay0lee'

bugs.python.org fields:

activity = <Date 2022-01-29.17:23:26.797>
actor = 'christian.heimes'
assignee = 'steve.dower'
closed = False
closed_date = None
closer = None
components = ['Build', 'Windows', 'SSL']
creation = <Date 2022-01-29.13:35:11.638>
creator = 'jay0lee'
dependencies = []
files = []
hgrepos = []
issue_num = 46570
keywords = []
message_count = 2.0
messages = ['412072', '412085']
nosy_count = 6.0
nosy_names = ['paul.moore', 'christian.heimes', 'tim.golden', 'zach.ware', 'steve.dower', 'jay0lee']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'needs patch'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue46570'
versions = ['Python 3.11']

[jay0lee]

Steps to reproduce:

1. Compile OpenSSL 3.0 on Windows.
2. use get_externals.bat to download Python external requirements on Windows.
3. Overwrite OpenSSL 1.1.1m in externals with your OpenSSL 3.0 build.

Expected behavior:
Python will build against OpenSSL 3.0

Actual behavior:
Build fails with missing DLLs.

Further information:

• For OpenSSL 3.0 builds, the first suffix for libcrypto and libssl is -3, not -1_1.
• For x86_64 builds, there's also an -x64 suffix to distinguish from x86 builds.

I have a openssl.props modified file at:
https://github.com/GAM-team/actions-hello-world/blob/master/openssl.props

which I've overwritten the existing:
https://github.com/python/cpython/blob/main/PCbuild/openssl.props#L13

file with and then succesfully compiled against OpenSSL 3.0. However I'm not certain if or where the logic should exist to detect OpenSSL 3.0 DLLs instead of 1.1.

[tiran]

OpenSSL 3.0 support is still experimental and incomplete. 3.10 is definitely out of scope. 3.11 might be feasible if somebody puts in the work.

[zware]

This is pretty much done via PRs connected to gh-99079.