Blame doc/functions/gnutls_privkey_sign_hash2

Packit Service 4684c1
Packit Service 4684c1
Packit Service 4684c1
Packit Service 4684c1
Packit Service 4684c1
@deftypefun {int} {gnutls_privkey_sign_hash2} (gnutls_privkey_t @var{signer}, gnutls_sign_algorithm_t @var{algo}, unsigned int @var{flags}, const gnutls_datum_t * @var{hash_data}, gnutls_datum_t * @var{signature})
Packit Service 4684c1
@var{signer}: Holds the signer's key
Packit Service 4684c1
Packit Service 4684c1
@var{algo}: The signature algorithm used
Packit Service 4684c1
Packit Service 4684c1
@var{flags}: Zero or one of @code{gnutls_privkey_flags_t} 
Packit Service 4684c1
Packit Service 4684c1
@var{hash_data}: holds the data to be signed
Packit Service 4684c1
Packit Service 4684c1
@var{signature}: will contain newly allocated signature
Packit Service 4684c1
Packit Service 4684c1
This function will sign the given hashed data using the specified signature
Packit Service 4684c1
algorithm. This function is an enhancement of @code{gnutls_privkey_sign_hash()} ,
Packit Service 4684c1
as it allows utilizing a alternative signature algorithm where possible
Packit Service 4684c1
(e.g, use an RSA key with RSA-PSS).
Packit Service 4684c1
Packit Service 4684c1
The flags may be @code{GNUTLS_PRIVKEY_SIGN_FLAG_TLS1_RSA} .
Packit Service 4684c1
In that case this function will ignore  @code{hash_algo} and perform a raw PKCS1 signature.
Packit Service 4684c1
Note that this flag is supported since 3.6.9.
Packit Service 4684c1
Packit Service 4684c1
Note also that, not all algorithm support signing already hashed data. When
Packit Service 4684c1
signing with Ed25519, @code{gnutls_privkey_sign_data2()}  should be used instead.
Packit Service 4684c1
Packit Service 4684c1
@strong{Returns:} On success, @code{GNUTLS_E_SUCCESS}  (0) is returned, otherwise a
Packit Service 4684c1
negative error value.
Packit Service 4684c1
Packit Service 4684c1
@strong{Since:} 3.6.0
Packit Service 4684c1
@end deftypefun