Do not try to "modernize" by dropping in OpenSSL 3.0. Do not expect Windows to provide it. Instead, treat these two DLLs ( libeay32 and ssleay32 ) as permanent artifacts of your application, ship them in your install folder, and they will continue to work for another decade.
uses IdSSLOpenSSLHeaders, Windows; procedure LoadSSLVerbose; var ErrorCode: Integer; begin if not LoadOpenSSLLibrary then begin ErrorCode := IdSSLOpenSSLHeaders.GetOpenSSLError; ShowMessage('SSL Error Code: ' + IntToStr(ErrorCode) + #13#10 + 'Last OS Error: ' + IntToStr(GetLastError)); // Common codes: // 0: DLL not found // 1: DLL loaded but function mismatch (wrong version) // 126: Module not found (missing VC runtime) end; end; Delphi 7 links to MSVCRT.DLL (the system C runtime). Old OpenSSL 0.9.8 (for VC6) also links to MSVCRT.DLL . That works perfectly. Newer OpenSSL 1.1+ links to MSVCR90.dll or VCRUNTIME140.dll . Indy 9 cannot load these because the function names are decorated differently. Delphi 7 Indy 9 Could Not Load Ssl Library
Explicitly set the DLL path before any SSL call. Do not try to "modernize" by dropping in OpenSSL 3
If you need TLS 1.2 or 1.3 support, note that OpenSSL 1.0.2 supports TLS 1.2 but TLS 1.3. For TLS 1.3, you genuinely have no choice but to migrate to a modern Delphi version (10.x+ with Indy 10). But if your legacy app needs to connect to an old server (TLS 1.0/1.1), the solution above will keep the lights on for years to come. Newer OpenSSL 1
uses IdSSLOpenSSLHeaders; procedure ForceSSLLoad; var ExePath: string; begin // Get the directory where the EXE lives ExePath := ExtractFilePath(ParamStr(0));
Add this to your main form's OnCreate or in a initialization section:
// Manually load the libraries from the EXE path SetDllDirectory(PChar(ExePath));