Blame doc/functions/gnutls_priority_init
|
Packit |
aea12f |
|
|
Packit |
aea12f |
|
|
Packit |
aea12f |
|
|
Packit |
aea12f |
|
|
Packit |
aea12f |
@deftypefun {int} {gnutls_priority_init} (gnutls_priority_t * @var{priority_cache}, const char * @var{priorities}, const char ** @var{err_pos})
|
|
Packit |
aea12f |
@var{priority_cache}: is a @code{gnutls_prioritity_t} type.
|
|
Packit |
aea12f |
|
|
Packit |
aea12f |
@var{priorities}: is a string describing priorities (may be @code{NULL} )
|
|
Packit |
aea12f |
|
|
Packit |
aea12f |
@var{err_pos}: In case of an error this will have the position in the string the error occurred
|
|
Packit |
aea12f |
|
|
Packit |
aea12f |
For applications that do not modify their crypto settings per release, consider
|
|
Packit |
aea12f |
using @code{gnutls_priority_init2()} with @code{GNUTLS_PRIORITY_INIT_DEF_APPEND} flag
|
|
Packit |
aea12f |
instead. We suggest to use centralized crypto settings handled by the GnuTLS
|
|
Packit |
aea12f |
library, and applications modifying the default settings to their needs.
|
|
Packit |
aea12f |
|
|
Packit |
aea12f |
This function is identical to @code{gnutls_priority_init2()} with zero
|
|
Packit |
aea12f |
flags.
|
|
Packit |
aea12f |
|
|
Packit |
aea12f |
A @code{NULL} @code{priorities} string indicates the default priorities to be
|
|
Packit |
aea12f |
used (this is available since GnuTLS 3.3.0).
|
|
Packit |
aea12f |
|
|
Packit |
aea12f |
@strong{Returns:} On syntax error @code{GNUTLS_E_INVALID_REQUEST} is returned,
|
|
Packit |
aea12f |
@code{GNUTLS_E_SUCCESS} on success, or an error code.
|
|
Packit |
aea12f |
@end deftypefun
|