eXosip_tls_credentials_s(3)

πŸ“¦ version 5.3.0, in epel 9

eXosip_tls_credentials_s(3)

bestie, welcome to the eXosip_tls_credentials_s page from libeXosip2 πŸ’– This is the struct that holds TLS credential stuff for a client or a server. Every field matters, so let’s go.


✨ NAME ✨

eXosip_tls_credentials_s


🌸 SYNOPSIS 🌸

#include <eX_setup.h>

πŸŽ€ Data Fields πŸŽ€

  • char priv_key [1024]
  • char priv_key_pw [1024]
  • char cert [1024]
  • char public_key_pinned [1024]

πŸ’– Detailed Description πŸ’–

Okay so this struct is used to describe credentials for a client or server. It consists of a certificate, a corresponding private key and its password. periodt. πŸ¦‹

If the server requires a certificate from the client, you must provide the certificate, private key, and your private key password. πŸ”‘

You can 'pin' your public key certificate if you have received it. public_key_pinned must contains your public key file in DER format. To extract your public key from a PEM certificate in DER format, you can use the following command line:

openssl x509 -in server-cert.pem -pubkey -noout | openssl enc -base64 -d > pub_key.der

πŸ”₯ Field Documentation πŸ”₯

char eXosip_tls_credentials_s::priv_key[1024]

absolute path to a file with a private key πŸ”

char eXosip_tls_credentials_s::priv_key_pw[1024]

password to open private key πŸ—οΈ

char eXosip_tls_credentials_s::cert[1024]

absolute path to a file with a certificate for the private key πŸ“œ

char eXosip_tls_credentials_s::public_key_pinned[1024]

absolute path to a file with the expected public key of server πŸ›‘οΈ


πŸ‘‘ Author πŸ‘‘

Generated automatically by Doxygen for libeXosip2 from the source code. πŸ’…


okay that’s the whole page, bestie β€” from libeXosip2, Version 5.3.0, Thu May 18 2023. 🫢✨

πŸ“¦ where this page comes from