1 Reply by move

(3 replies, posted in wolfSSL)

alex.abrahamson wrote:

Every application using the wolfSSL library should be including the file wolfssl/wolfcrypt/settings.h before including any other wolfSSL headers, and I see that it is being included in examples/client/client.c around line 27. Is this the client you're referring to?

Yes, you're right. I missed that.

Suppose I built the library using the configure script, and now want to compile an application, I see one way to detect feature is to define HAVE_CONFIG_H and include the generated config.h, like in the example client:

#ifdef HAVE_CONFIG_H
        #include <config.h>
#endif

Is that a reasonable approach?

Go to forum: wolfSSL

2 Topic by move

(2 replies, posted in wolfSSL)

I want to check if the max_fragment_length extension is negotiated. I could sniff the server_hello message and parse it in the client. But is there built-in support for this?

Thanks a lot!

Go to forum: wolfSSL

3 Topic by move

(3 replies, posted in wolfSSL)

Hi all,

I'm working on an HTTPS client using wolfSSL. I want to use HAVE_* or NO_* flags to make the client work with different configurations. I see there are ''wolfssl/options.h', 'wolfssl/wolfcrypt/settings.h', and config.h produced by configure. Which should I use to detect features? client.c includes neither...

Fan

Go to forum: wolfSSL