-
-
Notifications
You must be signed in to change notification settings - Fork 32k
OPENSSL_Applink error on Python 3.11.5 Windows 10 2022H2 #108687
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Because the applink table is kept in You'll find the patch in prepare_ssl.py (though we actually patch it somewhere else, as we don't build using this script anymore). |
Thank you, I understand. I have patched the source code per your instruction and rebuilt OpenSSL 3.0.9 and have new DLL files. However, I still get the same error. The _ssl.pyd file comes from the python 3.11.5 environment via PYinstaller, I added some print statements in uplink.c (confirming that the EXE is reading from the new DDLs) and have found that the output from is still NULL. This means to me that _ssl.pyd is getting read but that it does not contain the OPENSSL Applink table. It was my understanding from the linked questions and from your answer that _ssl.pyd does contain the Applink table. Is this incorrect? Thank you for your help! |
That surprises me. If the standard Are you sure you aren't overwriting the value of |
Thank you for your response. It seems that when I use the _ssl.pyd file packaged in conda it does not work, but when I download the latest python 3.11.5 from the official website it does work. May be interesting for someone to take note. The file sizes are different (the conda one is 166KB while the official python one is 173KB) suggesting that there is indeed an addition in the "official" version of _ssl.pyd. Now, I am no longer getting the Applink error. However, when I run the executable I make using pyinstaller, (where I replaced the 2 DLLs with the two new ones) and I replace _ssl.pyd as explained, I get a urllib3 error: I turned off my antivirus for this just in case, but that does not change the situation. I am making an HTTPS request which works from windows CURL and works from the python interpreter of that conda environment. I am doing this on a clean install of miniconda in an environment setup with all the packages needed for this project and nothing else. Do you have any ideas what could cause urllib3 to fail like this? Thank you very much! |
They build in a different way, so you'll need to check in with either conda-forge or Anaconda to see what they're doing.
Usually it means that |
Thank you very much for all your help, I got it to work based on your comments! |
At first, I only used the official _ssl.pyd replacing _ssl.pyd in conda DLL,but still reports an error. The content in my Python 3.11.5 official DLL covered the content of the conda DLL, and ultimately resolved this issue |
Bug report
Checklist
and am confident this bug has not been reported before
CPython versions tested on:
3.11
Operating systems tested on:
Windows
Output from running 'python -VV' on the command line:
Python 3.11.5 | packaged by conda-forge | (main, Aug 27 2023, 03:23:48) [MSC v.1936 64 bit (AMD64)]
A clear and concise description of the bug:
I am following up on the issue described here
#99079
also described here
#101401
I compile using Cython 3.0.2 on Windows 10 22H2 (Version 10.0.19045.3324) and have installed three different versions of OpenSSL
1.1.1i
1.1.1v
3.0.10
and compile against each version yet I continue to get the same error
OPENSSL_Uplink{00007FFE7BF17068,08}: no OPENSSL_Applink
message when the executable makes an HTTP request using the requests library to an HTTPS endpoint.
I did get this to work with the 3.12.0rc1 version but I need a conda environment around it for all the other package we depend on which is not yet available. This 3.11.5 version works fine on a different Windows machine Version 10.0.18363.657 (older).
In the comment that closed out the issue I am referencing above they stated that 3.11.5 works on the newer version of Windows with OpenSSL 3.X.X. Can you provide detail as to how you got this to work?
The text was updated successfully, but these errors were encountered: