On 6/26/25 16:19, Zinovy Soltsov via curl-library wrote:
> To whom it may concern,
> 
> We have an old C++ application using the old Curl library, probably from year 
> 2007. We use it to communicate with one of our content provider's SFTP 
> servers. The content provider recently switched to sha256 key fingerprint and 
> it broke our application. This is not a surprise since this didn't exist so 
> long ago.
> 
> I downloaded the latest Curl 18.14.1 binaries for Windows 32 bit applications 
> from https://curl.se/windows/ and tried to link it statically to the C++ 
> program. I got a number unresolved external symbol link errors. Most of them 
> (but not all of them) were about __memcpy_chk function. As far as I 
> understand this is a Linux function and Windows doesn't have such an API. 
> Also, although it is not a big deal, the library binaries have .a file name 
> Linux extension not the Windows .lib extension. It just makes me suspect that 
> the library binaries were compiled for Linux applications.
> 
> I also tied to link the Curl library dynamically and didn't get any issues 
> with it but our executable started blowing up when I put it on one of our 
> servers along with libcurl.dll.
> 
> This is pretty urgent for us since we use this application for clients like 
> WellsFargo and Bank of America. Your help would be greatly appreciated.

Given that this is urgent for your business, I recommend paying for commercial 
support
rather than asking the developers of an open source project to help you for 
free.
Commercial support for curl and libcurl is available from WolfSSL:
https://www.wolfssl.com/commercial-curl-support/.  I would not at all be 
surprised if
the cost of the support is more than paid for by being able to resume business 
operations
sooner.
-- 
Sincerely,
Demi Marie Obenour (she/her/hers)

Attachment: OpenPGP_0xB288B55FFF9C22C1.asc
Description: OpenPGP public key

Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature

-- 
Unsubscribe: https://lists.haxx.se/mailman/listinfo/curl-library
Etiquette:   https://curl.se/mail/etiquette.html

Reply via email to