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 "SSL_CTX_SET_TLSEXT_USE_SRTP 3"
way too many mistakes in technical documents.
An OpenSSL client wishing to send the \*(L"use_srtp\*(R" extension should call \fBSSL_CTX_set_tlsext_use_srtp() to set its use for all \s-1SSL\s0 objects subsequently created from an \s-1SSL_CTX.\s0 Alternatively a client may call \fBSSL_set_tlsext_use_srtp() to set its use for an individual \s-1SSL\s0 object. The \fBprofiles parameters should point to a NUL-terminated, colon delimited list of \s-1SRTP\s0 protection profile names.
The currently supported protection profile names are:
Supplying an unrecognised protection profile name will result in an error.
An OpenSSL server wishing to support the \*(L"use_srtp\*(R" extension should also call \fBSSL_CTX_set_tlsext_use_srtp() or SSL_set_tlsext_use_srtp() to indicate the protection profiles that it is willing to negotiate.
The currently configured list of protection profiles for either a client or a server can be obtained by calling SSL_get_srtp_profiles(). This returns a stack of \s-1SRTP_PROTECTION_PROFILE\s0 objects. The memory pointed to in the return value of this function should not be freed by the caller.
After a handshake has been completed the negotiated \s-1SRTP\s0 protection profile (if any) can be obtained (on the client or the server) by calling \fBSSL_get_selected_srtp_profile(). This function will return \s-1NULL\s0 if no \s-1SRTP\s0 protection profile was negotiated. The memory returned from this function should not be freed by the caller.
If an \s-1SRTP\s0 protection profile has been successfully negotiated then the \s-1SRTP\s0 keying material (on both the client and server) should be obtained via a call to \fBSSL_export_keying_material\|(3). This call should provide a label value of \*(L"EXTRACTOR-dtls_srtp\*(R" and a \s-1NULL\s0 context value (use_context is 0). The total length of keying material obtained should be equal to two times the sum of the master key length and the salt length as defined for the protection profile in use. This provides the client write master key, the server write master key, the client write master salt and the server write master salt in that order.
\fBSSL_get_srtp_profiles() returns a stack of \s-1SRTP_PROTECTION_PROFILE\s0 objects on success or \s-1NULL\s0 on error or if no protection profiles have been configured.
\fBSSL_get_selected_srtp_profile() returns a pointer to an \s-1SRTP_PROTECTION_PROFILE\s0 object if one has been negotiated or \s-1NULL\s0 otherwise.
Licensed under the OpenSSL license (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>.