[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
6.1.4 Debugging and auditing
In many cases things may not go as expected and further information, to assist debugging, from GnuTLS is desired. Those are the cases where the gnutls_global_set_log_level and gnutls_global_set_log_function are to be used. Those will print verbose information on the GnuTLS functions internal flow.
void gnutls_global_set_log_level (int level)
void gnutls_global_set_log_function (gnutls_log_func log_func)
Alternatively the environment variable GNUTLS_DEBUG_LEVEL
can be
set to a logging level and GnuTLS will output debugging output to standard
error.
When debugging is not required, important issues, such as detected attacks on the protocol still need to be logged. This is provided by the logging function set by gnutls_global_set_audit_log_function. The provided function will receive an message and the corresponding TLS session. The session information might be used to derive IP addresses or other information about the peer involved.
- Function: void gnutls_global_set_audit_log_function (gnutls_audit_log_func log_func)
log_func: it is the audit log function
This is the function to set the audit logging function. This is a function to report important issues, such as possible attacks in the protocol. This is different from
gnutls_global_set_log_function()
because it will report also session-specific events. The session parameter will be null if there is no corresponding TLS session.gnutls_audit_log_func
is of the form, void (*gnutls_audit_log_func)( gnutls_session_t, const char*);Since: 3.0
[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
This document was generated on February 9, 2014 using texi2html 5.0.