Note that is not clear which header should be included for linux structure, you may need to check these structures and constants. If KTLS support is needed, define WITH_KTLS (compile with -DWITH_KTLS). Also, the negotiation must be handled by TLSe. If TLS_RX is not defined, KTLS is send-only (you may use send/sendfile to send data, but you may not use recv). KTLS is a TLS implementation in the linux kernel. TLSe supports KTLS on linux kernel 4.13 or higher. Also, you may want to define LTC_PTHREAD if you're using libtomcrypt. Other than that, TLSe and libtomcrypt are thread-safe. If thread-safety is needed, you need to call tls_init() before letting any other threads in, and not use the same object from multiple threads without a mutex. Alternatively, you may include tlse.h and add tlse.c to your makefile (useful when linking against C++). Tlse.h is optional (is safe to just include tlse.c). $ gcc tlsserverhello.c -o tlsserverhello -DTLS_AMALGAMATION $ gcc tlshello.c -o tlshello -DTLS_AMALGAMATION

In this case, the client may be compiled: The library may also use the libtomcrypt.c amalgamation. The entire library is a single c file that you just include in your source.

$ gcc tlsserverhello.c -o tlsserverhello -ltomcrypt -ltommath -DLTM_DESC $ gcc tlshello.c -o tlshello -ltomcrypt -ltommath -DLTM_DESCįor debuging tls connections, the DEBUG flag must be set (-DDEBUG). Like this project ? You may donate Bitcoin for this project at 14LqvMzFfaJ82C7wY5iavvTf9HPELYWsax Client-side TLS 1.3 support is experimental. I'm working at an alternative efficient RSA signing, DH and Curve25519 implementation, to allow the compilation, alternatively, without tomcrypt, on devices where memory and code size is an issue. Before using tlse.c you may want to download and compile tomcrypt alternatively you may use libtomcrypt.c (see Compiling). Single C file TLS 1.3, 1.2, 1.1 and 1.0(without the weak ciphers) implementation, using libtomcrypt as crypto library.

Test tls 1.2 connections