Lines Matching +refs:sign +refs:any

49 structure is never modified by any @acronym{GnuTLS} function, except
117 If any non fatal errors, that require an action, are to be returned by
242 a single thread and no other thread may be performing any operation.
260 the function @funcref{gnutls_global_set_mutex} before calling any other
298 As well as any calls needed for memory allocation to work. Note however, that GnuTLS
370 The initialization typically enables CPU-specific acceleration, performs any required
371 precalculations needed, opens any required system devices (e.g., /dev/urandom on Linux)
562 and key pair must be loaded. This occurs before any @acronym{TLS} 
584 If the imported keys and certificates need to be accessed before any TLS session
623 authentication methods.  For example keys marked as sign-only, will
834 resumed (called again), if any of the above error codes is returned. The
879 that they only apply to the kernel sockets API. To check for any
938 Note, that when this function is used, any connection failures will be reported during the
1106 to generate a secret key that is used to sign a cookie@footnote{A key of 128 bits or 16 bytes shoul…
1132 Although DTLS can run under any reliable or unreliable layer, there are
1161 accounting for stapled OCSP responses during the handshake; any error will
1187 at any time, when DTLS is used the GnuTLS receive functions must be
1411 for @emph{special keywords}) can be prefixed with any of the following
1532 will prevent the sending of any TLS extensions in client side. Note
1640 Finally the ciphersuites enabled by any priority string can be
1936 additional session tickets at any time using @funcref{gnutls_session_ticket_send}.
2033 According to the TLS specification a client may initiate a rehandshake at any