#include <rte_crypto_asym.h>
RSA operation params
Definition at line 414 of file rte_crypto_asym.h.
◆ op_type
◆ message
Pointer to input data
- to be encrypted for RSA public encrypt.
- to be signed for RSA sign generation.
- to be authenticated for RSA sign verification.
Pointer to output data
- for RSA private decrypt. In this case the underlying array should have been allocated with enough memory to hold plaintext output (i.e. must be at least RSA key size). The message.length field could be either 0 or minimal length expected from PMD. This could be validated and overwritten by the PMD with the decrypted length.
- Examples:
- examples/fips_validation/main.c.
Definition at line 418 of file rte_crypto_asym.h.
◆ cipher
Pointer to input data
- to be decrypted for RSA private decrypt.
Pointer to output data
- for RSA public encrypt. In this case the underlying array should have been allocated with enough memory to hold ciphertext output (i.e. must be at least RSA key size). The cipher.length field could be either 0 or minimal length expected from PMD. This could be validated and overwritten by the PMD with the encrypted length.
When RTE_CRYPTO_RSA_PADDING_NONE and RTE_CRYPTO_ASYM_OP_VERIFY selected, this is an output of decrypted signature.
Definition at line 435 of file rte_crypto_asym.h.
◆ sign
Pointer to input data
- to be verified for RSA public decrypt.
Pointer to output data
- for RSA private encrypt. In this case the underlying array should have been allocated with enough memory to hold signature output (i.e. must be at least RSA key size). The sign.length field could be either 0 or minimal length expected from PMD. This could be validated and overwritten by the PMD with the signature length.
- Examples:
- examples/fips_validation/main.c.
Definition at line 453 of file rte_crypto_asym.h.
The documentation for this struct was generated from the following file:
