Hallo, dies ist ein Test.

PWD: /www/data-lst1/unixsoft/unixsoft/kaempfer/.public_html

Running in File Mode
Relative path: ./../../../../../../sbin/../man/man3lib/libucrypto_sign.3lib
Real path: /usr/share/man/man3lib/libucrypto_sign.3lib
Zurück

.\" Copyright (c) 2016, 2018, Oracle and/or its affiliates. All rights reserved.
.nf

Ucrypto Digital Signatures					libucrypto(3LIB)

NAME
	crypto_sign, crypto_sign_init, crypto_sign_update,
	crypto_sign_final, crypto_verify, crypto_verify_init,
	crypto_verify_update, crypto_verify_final - digital
	signature operations
SYNOPSIS
	#include <libucrypto.h>

int crypto_sign(crypto_mechanism_t *mech, crypto_key_t *key,
	    crypto_data_t *data, crypto_ctx_template_t tmpl,
	    crypto_data_t *signature, crypto_call_req_t *cr);

int crypto_sign_init(crypto_mechanism_t *mech, crypto_key_t *key,
	    crypto_ctx_template_t tmpl, crypto_context_t *ctxp,
	    crypto_call_req_t *cr);

int crypto_sign_update(crypto_context_t ctx, crypto_data_t *data,
	    crypto_call_req_t *cr);

int crypto_sign_final(crypto_context_t ctx, crypto_data_t *signature,
	    crypto_call_req_t *cr);

int crypto_verify(crypto_mechanism_t *mech, crypto_key_t *key,
	    crypto_data_t *data, crypto_ctx_template_t tmpl,
	    crypto_data_t *signature, crypto_call_req_t *cr);

int crypto_verify_init(crypto_mechanism_t *mech, crypto_key_t *key,
	    crypto_ctx_template_t tmpl, crypto_context_t *ctxp,
	    crypto_call_req_t *cr);

int crypto_verify_update(crypto_context_t ctx, crypto_data_t *data,
	    crypto_call_req_t *cr);

int crypto_verify_final(crypto_context_t ctx, crypto_data_t *signature,
	    crypto_call_req_t *cr);

DESCRIPTION
	The function crypto_sign() performs a digital signature operation
	on single part data.

The function crypto_sign_init() begins a digital signature
	on multi-part data.

The function crypto_sign_update() continues a digital signature
	operation on multi-part data.

The function crypto_sign_final() finishes a digital signature
	operation on multi-part data.

The function crypto_verify() verifies a digital signature
	on single part data.

The function crypto_verify_init() begins a digital signature
	verification on multi-part data.

The function crypto_verify_update() continues a digital signature
	verification on multi-part data.

The function crypto_verify_final() finishes a digital signature
	verification on multi-part data.

The libucrypto digital signature API currently supports
	the following mechanisms:
	CRYPTO_MD5_RSA_PKCS, CRYPTO_SHA1_RSA_PKCS, CRYPTO_SHA224_RSA_PKCS,
	CRYPTO_SHA245_RSA_PKCS, CRYPTO_SHA384_RSA_PKCS, CRYPTO_SHA512_RSA_PKCS,
	CRYPTO_SHA224_DSA, CRYPTO_SHA256_DSA, CRYPTO_SHA384_DSA,
	CRYPTO_SHA512_DSA, CRYPTO_ECDSA, CRYPTO_ECDSA_SHA1, CRYPTO_ECDSA_SHA224,
	CRYPTO_ECDSA_SHA256, CRYPTO_ECDSA_SHA384, and CRYPTO_ECDSA_SHA512.
	To use a given mechanism for an API call, set the cm_type field of
	the crypto_mechanism_t argument to the appropriate value.

RETURN VALUES
       Upon successful completion, crypto_sign(), crypto_sign_init(),
       crypto_sign_update(), crypto_sign_final(), crypto_verify(),
       crypto_verify_init(), crypt_verify_update(), and
       crypto_verify_final() will return CRYPTO_SUCCESS (0x00).
       Otherwise, they return an error code. See ucrypto_strerror(3LIB)
       for descriptions of error codes.

ATTRIBUTES
See attributes(5) for descriptions of the following attributes: