libeXosip2  5.3.0
Data Fields
eXosip_tls_ctx_s Struct Reference

#include <eX_setup.h>

Data Fields

char random_file [1024]
 
char dh_param [1024]
 
char root_ca_cert [1024]
 
char cipher_list [2048]
 
unsigned long tls_flags
 
unsigned long dtls_flags
 
eXosip_tls_credentials_t client
 
eXosip_tls_credentials_t server
 

Detailed Description

structure to describe the whole TLS-context for eXosip consists of a certificate, a corresponding private key and its password

When a client connects to a server, if you wish to verify certificate, you just have to configure the root_ca_cert parameter to a file with all your trusted CA. (example file at https://pki.google.com/roots.pem)

On Windows & Macosx, the trusted certificates from the store are loaded automatically.

Field Documentation

◆ random_file

char eXosip_tls_ctx_s::random_file[1024]

absolute path to a file with random(!) data

◆ dh_param

char eXosip_tls_ctx_s::dh_param[1024]

absolute path to a file necessary for diffie hellman key exchange

◆ root_ca_cert

char eXosip_tls_ctx_s::root_ca_cert[1024]

absolute path to the file with known rootCAs

◆ cipher_list

char eXosip_tls_ctx_s::cipher_list[2048]

openssl cipher list (default: HIGH:!COMPLEMENTOFDEFAULT:!kRSA:!PSK:!SRP)

◆ tls_flags

unsigned long eXosip_tls_ctx_s::tls_flags

openssl additionnal flag (example: SSL_OP_NO_TLSv1, SSL_OP_NO_TLSv1_1)

◆ dtls_flags

unsigned long eXosip_tls_ctx_s::dtls_flags

openssl additionnal flag (example: SSL_OP_NO_DTLSv1)

◆ client

eXosip_tls_credentials_t eXosip_tls_ctx_s::client

credential of the client

◆ server

eXosip_tls_credentials_t eXosip_tls_ctx_s::server

credential of the server


The documentation for this struct was generated from the following file: