Automatically generated by Pod::Man 4.14 (Pod::Simple 3.40)

Standard preamble:
========================================================================
..

..

.. Set up some character translations and predefined strings. \*(-- will
give an unbreakable dash, \*(PI will give pi, \*(L" will give a left
double quote, and \*(R" will give a right double quote. \*(C+ will
give a nicer C++. Capital omega is used to do unbreakable dashes and
therefore won't be available. \*(C` and \*(C' expand to `' in nroff,
nothing in troff, for use with C<>.
.tr \(*W- . ds -- \(*W- . ds PI pi . if (\n(.H=4u)&(1m=24u) .ds -- \(*W\h'-12u'\(*W\h'-12u'-\" diablo 10 pitch . if (\n(.H=4u)&(1m=20u) .ds -- \(*W\h'-12u'\(*W\h'-8u'-\" diablo 12 pitch . ds L" "" . ds R" "" . ds C` "" . ds C' "" 'br\} . ds -- \|\(em\| . ds PI \(*p . ds L" `` . ds R" '' . ds C` . ds C' 'br\}
Escape single quotes in literal strings from groff's Unicode transform.

If the F register is >0, we'll generate index entries on stderr for
titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index
entries marked with X<> in POD. Of course, you'll have to process the
output yourself in some meaningful fashion.

Avoid warning from groff about undefined register 'F'.
.. .nr rF 0 . if \nF \{\ . de IX . tm Index:\\$1\t\\n%\t"\\$2" .. . if !\nF==2 \{\ . nr % 0 . nr F 2 . \} . \} .\} .rr rF
Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2).
Fear. Run. Save yourself. No user-serviceable parts.
. \" fudge factors for nroff and troff . ds #H 0 . ds #V .8m . ds #F .3m . ds #[ \f1 . ds #] .\} . ds #H ((1u-(\\\\n(.fu%2u))*.13m) . ds #V .6m . ds #F 0 . ds #[ \& . ds #] \& .\} . \" simple accents for nroff and troff . ds ' \& . ds ` \& . ds ^ \& . ds , \& . ds ~ ~ . ds / .\} . ds ' \\k:\h'-(\\n(.wu*8/10-\*(#H)'\'\h"|\\n:u" . ds ` \\k:\h'-(\\n(.wu*8/10-\*(#H)'\`\h'|\\n:u' . ds ^ \\k:\h'-(\\n(.wu*10/11-\*(#H)'^\h'|\\n:u' . ds , \\k:\h'-(\\n(.wu*8/10)',\h'|\\n:u' . ds ~ \\k:\h'-(\\n(.wu-\*(#H-.1m)'~\h'|\\n:u' . ds / \\k:\h'-(\\n(.wu*8/10-\*(#H)'\z\(sl\h'|\\n:u' .\} . \" troff and (daisy-wheel) nroff accents . \" corrections for vroff . \" for low resolution devices (crt and lpr) \{\ . ds : e . ds 8 ss . ds o a . ds d- d\h'-1'\(ga . ds D- D\h'-1'\(hy . ds th \o'bp' . ds Th \o'LP' . ds ae ae . ds Ae AE .\} ========================================================================

Title "OSSL_TRACE_SET_CHANNEL 3" For nroff, turn off justification. Always turn off hyphenation; it makes
way too many mistakes in technical documents.
OSSL_trace_set_channel, OSSL_trace_set_prefix, OSSL_trace_set_suffix, OSSL_trace_set_callback, OSSL_trace_cb - Enabling trace output Header "SYNOPSIS" .Vb 1 #include <openssl/trace.h> \& typedef size_t (*OSSL_trace_cb)(const char *buf, size_t cnt, int category, int cmd, void *data); \& void OSSL_trace_set_channel(int category, BIO *bio); void OSSL_trace_set_prefix(int category, const char *prefix); void OSSL_trace_set_suffix(int category, const char *suffix); void OSSL_trace_set_callback(int category, OSSL_trace_cb cb, void *data); .Ve Header "DESCRIPTION" If available (see \*(L"\s-1NOTES\*(R"\s0 below), the application can request internal trace output. This output comes in form of free text for humans to read.

The trace output is divided into categories which can be enabled individually. Every category can be enabled individually by attaching a so called \fItrace channel to it, which in the simplest case is just a \s-1BIO\s0 object to which the application can write the tracing output for this category. Alternatively, the application can provide a tracer callback in order to get more finegrained trace information. This callback will be wrapped internally by a dedicated \s-1BIO\s0 object.

For the tracing code, both trace channel types are indistinguishable. These are called a simple trace channel and a callback trace channel, respectively.

Subsection "Functions" \fBOSSL_trace_set_channel() is used to enable the given trace \*(C`category\*(C' by attaching the \s-1BIO\s0 bio object as (simple) trace channel. On success the ownership of the \s-1BIO\s0 is transferred to the channel, so the caller must not free it directly.

\fBOSSL_trace_set_prefix() and OSSL_trace_set_suffix() can be used to add an extra line for each channel, to be output before and after group of tracing output. What constitutes an output group is decided by the code that produces the output. The lines given here are considered immutable; for more dynamic tracing prefixes, consider setting a callback with \fBOSSL_trace_set_callback() instead.

\fBOSSL_trace_set_callback() is used to enable the given trace \fIcategory by giving it the tracer callback cb with the associated data data, which will simply be passed through to cb whenever it's called. The callback function is internally wrapped by a dedicated \s-1BIO\s0 object, the so called callback trace channel. This should be used when it's desirable to do form the trace output to something suitable for application needs where a prefix and suffix line aren't enough.

\fBOSSL_trace_set_channel() and OSSL_trace_set_callback() are mutually exclusive, calling one of them will clear whatever was set by the previous call.

Calling OSSL_trace_set_channel() with \s-1NULL\s0 for channel or \fBOSSL_trace_set_callback() with \s-1NULL\s0 for cb disables tracing for the given category.

Subsection "Trace callback" The tracer callback must return a size_t, which must be zero on error and otherwise return the number of bytes that were output. It receives a text buffer buf with cnt bytes of text, as well as the category, a control number cmd, and the data that was passed to OSSL_trace_set_callback().

The possible control numbers are:

Item "OSSL_TRACE_CTRL_BEGIN" The callback is called from OSSL_trace_begin(), which gives the callback the possibility to output a dynamic starting line, or set a prefix that should be output at the beginning of each line, or something other. Item "OSSL_TRACE_CTRL_WRITE" This callback is called whenever data is written to the \s-1BIO\s0 by some regular \s-1BIO\s0 output routine. An arbitrary number of \s-1OSSL_TRACE_CTRL_WRITE\s0 callbacks can occur inside a group marked by a pair of \s-1OSSL_TRACE_CTRL_BEGIN\s0 and \fB\s-1OSSL_TRACE_CTRL_END\s0 calls, but never outside such a group. Item "OSSL_TRACE_CTRL_END" The callback is called from OSSL_trace_end(), which gives the callback the possibility to output a dynamic ending line, or reset the line prefix that was set with \s-1OSSL_TRACE_CTRL_BEGIN\s0, or something other. Subsection "Trace categories" The trace categories are simple numbers available through macros. Item "OSSL_TRACE_CATEGORY_TRACE" Traces the OpenSSL trace \s-1API\s0 itself. .Sp More precisely, this will generate trace output any time a new trace hook is set. Item "OSSL_TRACE_CATEGORY_INIT" Traces OpenSSL library initialization and cleanup. .Sp This needs special care, as OpenSSL will do automatic cleanup after exit from \*(C`main()\*(C', and any tracing output done during this cleanup will be lost if the tracing channel or callback were cleaned away prematurely. A suggestion is to make such cleanup part of a function that's registered very early with atexit\|(3). Item "OSSL_TRACE_CATEGORY_TLS" Traces the \s-1TLS/SSL\s0 protocol. Item "OSSL_TRACE_CATEGORY_TLS_CIPHER" Traces the ciphers used by the \s-1TLS/SSL\s0 protocol. Item "OSSL_TRACE_CATEGORY_CONF" Traces details about the provider and engine configuration. Item "OSSL_TRACE_CATEGORY_ENGINE_TABLE" Traces the \s-1ENGINE\s0 algorithm table selection. .Sp More precisely, functions like ENGINE_get_pkey_asn1_meth_engine(), \fBENGINE_get_pkey_meth_engine(), ENGINE_get_cipher_engine(), \fBENGINE_get_digest_engine(), will generate trace summaries of the handling of internal tables. Item "OSSL_TRACE_CATEGORY_ENGINE_REF_COUNT" Traces the \s-1ENGINE\s0 reference counting. .Sp More precisely, both reference counts in the \s-1ENGINE\s0 structure will be monitored with a line of trace output generated for each change. Item "OSSL_TRACE_CATEGORY_PKCS5V2" Traces PKCS#5 v2 key generation. Item "OSSL_TRACE_CATEGORY_PKCS12_KEYGEN" Traces PKCS#12 key generation. Item "OSSL_TRACE_CATEGORY_PKCS12_DECRYPT" Traces PKCS#12 decryption. Item "OSSL_TRACE_CATEGORY_X509V3_POLICY" Traces X509v3 policy processing. .Sp More precisely, this generates the complete policy tree at various point during evaluation. Item "OSSL_TRACE_CATEGORY_BN_CTX" Traces \s-1BIGNUM\s0 context operations. Item "OSSL_TRACE_CATEGORY_CMP" Traces \s-1CMP\s0 client and server activity. Item "OSSL_TRACE_CATEGORY_STORE" Traces \s-1STORE\s0 operations. Item "OSSL_TRACE_CATEGORY_DECODER" Traces decoder operations. Item "OSSL_TRACE_CATEGORY_ENCODER" Traces encoder operations. Item "OSSL_TRACE_CATEGORY_REF_COUNT" Traces decrementing certain \s-1ASN.1\s0 structure references.

There is also \s-1OSSL_TRACE_CATEGORY_ALL\s0, which works as a fallback and can be used to get all trace output.

Note, however, that in this case all trace output will effectively be associated with the '\s-1ALL\s0' category, which is undesirable if the application intends to include the category name in the trace output. In this case it is better to register separate channels for each trace category instead.

Header "RETURN VALUES" \fBOSSL_trace_set_channel(), OSSL_trace_set_prefix(), \fBOSSL_trace_set_suffix(), and OSSL_trace_set_callback() return 1 on success, or 0 on failure. Header "EXAMPLES" In all examples below, the trace producing code is assumed to be the following:

.Vb 3 int foo = 42; const char bar[] = { 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15 }; \& OSSL_TRACE_BEGIN(TLS) { BIO_puts(trc_out, "foo: "); BIO_printf(trc_out, "%d\en", foo); BIO_dump(trc_out, bar, sizeof(bar)); } OSSL_TRACE_END(TLS); .Ve

Subsection "Simple example" An example with just a channel and constant prefix / suffix.

.Vb 6 int main(int argc, char *argv[]) { BIO *err = BIO_new_fp(stderr, BIO_NOCLOSE | BIO_FP_TEXT); OSSL_trace_set_channel(OSSL_TRACE_CATEGORY_SSL, err); OSSL_trace_set_prefix(OSSL_TRACE_CATEGORY_SSL, "BEGIN TRACE[TLS]"); OSSL_trace_set_suffix(OSSL_TRACE_CATEGORY_SSL, "END TRACE[TLS]"); \& /* ... work ... */ } .Ve

When the trace producing code above is performed, this will be output on standard error:

.Vb 4 BEGIN TRACE[TLS] foo: 42 0000 - 00 01 02 03 04 05 06 07-08 09 0a 0b 0c 0d 0e 0f ................ END TRACE[TLS] .Ve

Subsection "Advanced example" This example uses the callback, and depends on pthreads functionality.

.Vb 5 static size_t cb(const char *buf, size_t cnt, int category, int cmd, void *vdata) { BIO *bio = vdata; const char *label = NULL; \& switch (cmd) { case OSSL_TRACE_CTRL_BEGIN: label = "BEGIN"; break; case OSSL_TRACE_CTRL_END: label = "END"; break; } \& if (label != NULL) { union { pthread_t tid; unsigned long ltid; } tid; \& tid.tid = pthread_self(); BIO_printf(bio, "%s TRACE[%s]:%lx\en", label, OSSL_trace_get_category_name(category), tid.ltid); } return (size_t)BIO_puts(bio, buf); } \& int main(int argc, char *argv[]) { BIO *err = BIO_new_fp(stderr, BIO_NOCLOSE | BIO_FP_TEXT); OSSL_trace_set_callback(OSSL_TRACE_CATEGORY_SSL, cb, err); \& /* ... work ... */ } .Ve

The output is almost the same as for the simple example above.

.Vb 4 BEGIN TRACE[TLS]:7f9eb0193b80 foo: 42 0000 - 00 01 02 03 04 05 06 07-08 09 0a 0b 0c 0d 0e 0f ................ END TRACE[TLS]:7f9eb0193b80 .Ve

Header "NOTES" Subsection "Configure Tracing" By default, the OpenSSL library is built with tracing disabled. To use the tracing functionality documented here, it is therefore necessary to configure and build OpenSSL with the 'enable-trace' option.

When the library is built with tracing disabled, the macro \fB\s-1OPENSSL_NO_TRACE\s0 is defined in <openssl/opensslconf.h> and all functions described here are inoperational, i.e. will do nothing.

Header "HISTORY" \fBOSSL_trace_set_channel(), OSSL_trace_set_prefix(), \fBOSSL_trace_set_suffix(), and OSSL_trace_set_callback() were all added in OpenSSL 3.0. Header "COPYRIGHT" Copyright 2019-2023 The OpenSSL Project Authors. All Rights Reserved.

Licensed under the Apache License 2.0 (the \*(L"License\*(R"). You may not use this file except in compliance with the License. You can obtain a copy in the file \s-1LICENSE\s0 in the source distribution or at <https://www.openssl.org/source/license.html>.