Skip to content
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

OpenSSL Initialization Failure Due to Manually Mapped DLLs Not Recognized by GetModuleHandleExA #35

Open
pinwhell opened this issue Sep 29, 2024 · 0 comments

Comments

@pinwhell
Copy link

Say we stop using LoadLibraryA instead we emulate it, for OpenSSL modules, when we attempt to initialize OpenSSL, its failing to robustly initialize on that Context, the reason exaclty becouse of ossl_init_load_crypto_nodelete, who returns false inside Crypto Initialize routine, becouse of the fact that WinApi GetModuleHandleExA is not aware of the manually mapped modules, how to approach this problem? notice that appart from that, when redirecting to another legit module, and forcing the function to return true, everything initialize as expected and OpenSSL works as normal (Sanity Tested Extensively).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant