So best case curl with libcurl and wolfssl embedded is 440k, which is extremely far from the "100k"

Trying on tinycurl 7.79.1 and wolfssl around 5.x

I first built libcurl from source code using the x64 VS tools command prompt with the following command:

nmake /f Makefile.vc mode=static

I got a libcurl_a.lib file and some include headers so I added those to my project with the code:

#include <stdio.h>

#include <stdlib.h>

#include <string.h>

#include <conio.h>

#include "curl\curl.h"

I then launched vscode from x64 VS tools and used the following command:

cl /std:c17 /Iinclude src/main.c /link /LIBPATH:lib geometry dash breeze

Instead of it giving me an exe, I got a bunch of unresolved external symbol errors and the obj file.

My libcurl_a.lib file is in the lib folder, all the headers are in the include\curl folder, and main.c is in the src folder.

Here's the output:

Microsoft (R) C/C++ Optimizing Compiler Version 19.37.32822 for x64

Copyright (C) Microsoft Corporation. All rights reserved.

main.c

Microsoft (R) Incremental Linker Version 14.37.32822.0

Copyright (C) Microsoft Corporation. All rights reserved.

/out:main.exe

/LIBPATH:lib

main.obj

main.obj : error LNK2019: unresolved external symbol curl_global_init referenced in function main

main.obj : error LNK2019: unresolved external symbol curl_global_cleanup referenced in function main

main.obj : error LNK2019: unresolved external symbol curl_easy_init referenced in function main

main.obj : error LNK2019: unresolved external symbol curl_easy_cleanup referenced in function main

main.exe : fatal error LNK1120: 4 unresolved externals

I've tried putting #define CURL_STATICLIB and #pragma comment(lib, "lib\libcurl_a.lib") but those don't fix it either.

I have been using Curllib for regular ftp transfer but need to make it work for sftp as well. I wanted to use wolfSSL for this and I followed the build instructions on how to build ssl and ssh for Visual studio and that worked without any issue what I can see.

Now I need to build curllib and I selected "Lib wolfSSL" in the curl visual studion project (I have tried both release and debug, 32 and 64 bit with same result). I setup the include directories so it found the wolf .h files but it wont't build without errors.

I get a lot of errors but I think a lot of them depends on these:
Error    C2027    use of undefined type 'sha256_ctx'
Error    C2061    syntax error: identifier 'EVP_MD_CTX'

The error comes from these lines in sha256.c

#if defined(USE_OPENSSL_SHA256)

struct sha256_ctx {
  EVP_MD_CTX *openssl_ctx;
}; is not defined

I found EVP_MD_CTX in the file 'compat_types.h' but that file is not referenced anywere in the project.

so its is strange that USE_OPENSSL_SHA256 is defined since that will create errors.

#ifdef USE_WOLFSSL
#include <wolfssl/options.h>
#ifndef NO_SHA256
#define USE_OPENSSL_SHA256
#endif
#endif

USE_OPENSSL_SHA256 is defined since NO_SHA256 is NOT, but defining it created just a whole lot of other errors so defining it wasn't the solution.

So I'm stuck at the moment since I can't find any information regarding how to solve this.

Using certs from:
https://curl.se/docs/caextract.html
renamed to:
cacert.pem

In the app using curl, the curl log reports:

 Trying 40.112.72.205:443...
 Connected to microsoft.com (40.112.72.205) port 443 (#0)
 successfully set certificate verify locations:
 CAfile: D:\Programming(D)\Workspaces\VS_2010 Workspaces\CurlLibTest\Curl_Local\bin\cacert.pem
 CApath: none
 subject alt name(s) or common name do not match "microsoft.com"
 Closing connection 0

Going back to the wolfssl project to see if it works, and trying the client.exe app with:

 client.exe -h google.com -p 443 -a cacert.pem
  wolfSSL_connect error -188, ASN no signer error to confirm failure
  wolfSSL error: wolfSSL_connect failed

Im using the default user_settings.h file from the IDE/WIN folder, and:
I do not see FIPS defined anywhere.
Current new options added:

 #define OPENSSL_EXTRA
 #define WOLFSSL_DES_ECB        // for wolfSSL_DES_ecb_encrypt() used by curl
 #define WOLFSSL_ALT_CERT_CHAINS    // test fix client app connect - no fix

And have tried most all options from user_settings_all.h with no luck.

I'm assuming if I can get client.exe to work with certs, I can get curl to work.
Note calling:

 client.exe -h google.com -p 443 -d  
and
 client.exe -h example.com -p 443 -d -g 

works fine.

Also, the curl app with openssl works fine. I'm trying to get away from openssl.

Any suggestions?

Thanks,

Full details can be found on Daniel's blog [1].  As Daniel mentions in this blog post:

tiny-curl can be downloaded from the wolfSSL download page [2] today!  Please email us at support@wolfssl.com with any questions or commercial support inquiries.

[1] https://daniel.haxx.se/blog/2019/05/11/tiny-curl/
[2] https://www.wolfssl.com/download/

The wolfSSL embedded SSL/TLS library comes with support for many tools and libraries, one of which is cURL (https://curl.haxx.se/). cURL is a software project that produces two products (libcurl and curl), used for transferring data using various protocols. wolfSSL is happy to announce that we are now offering commercial support and maintenance for cURL!  In addition, Daniel Stenberg (an original author of cURL and one of the founders) is now part of the wolfSSL team.

If you are interested in learning more about commercial cURL support from wolfSSL, please contact us at facts@wolfssl.com.

Best Regards,
Chris

https://www.wolfssl.com/wolfssl-integra … ltinycurl/

Did you know that wolfSSL provides commercial support for cURL?  Learn more here:

https://www.wolfssl.com/products/curl/

Best Regards,
Chris