Skip to content

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

@pinwhell

Description

@pinwhell

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).

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions