mbedtls_rsa_rsassa_pss_sign_ext() function

The initialized RSA context to use.

The RNG function. It is mandatory and must not be \c NULL.

The RNG context to be passed to \p f_rng. This may be \c NULL if \p f_rng doesn't need a context argument.

The message-digest algorithm used to hash the original data. Use #MBEDTLS_MD_NONE for signing raw data.

The length of the message digest or raw data in Bytes. If \p md_alg is not #MBEDTLS_MD_NONE, this must match the output length of the corresponding hash algorithm.

The buffer holding the message digest or raw data. This must be a readable buffer of at least \p hashlen Bytes.

The length of the salt that should be used. If passed #MBEDTLS_RSA_SALT_LEN_ANY, the function will use the largest possible salt length up to the hash length, which is the largest permitted by some standards including FIPS 186-4 §5.5.

The buffer to hold the signature. This must be a writable buffer of length \c ctx->len Bytes. For example, \c 256 Bytes for an 2048-bit RSA modulus. A buffer length of #MBEDTLS_MPI_MAX_SIZE is always safe.

This function retrieves the length of RSA modulus in Bytes.

This function frees the components of an RSA key.

This function imports a set of core parameters into an RSA context. Any sequence of calls to this function should be followed by a call to mbedtls_rsa_complete(), which checks and completes the provided information to a ready-for-use public or private RSA key.

This function exports the core parameters of an RSA key. If this function runs successfully, the non-NULL buffers pointed to by \p N, \p P, \p Q, \p D, and \p E are fully written, with additional unused space filled leading by zero Bytes. Possible reasons for returning #MBEDTLS_ERR_PLATFORM_FEATURE_UNSUPPORTED: An alternative RSA implementation is in use, which stores the key externally, and either cannot or should not export it into RAM. A SW or HW implementation might not support a certain deduction. For example, \p P, \p Q from \p N, \p D, and \p E if the former are not part of the implementation. If the function fails due to an unsupported operation, the RSA context stays intact and remains usable.

This function sets padding for an already initialized RSA context.

This function performs an RSA public key operation.

Load the contents of a key buffer into an internal RSA representation

This function checks if a context contains at least an RSA public key. If the function runs successfully, it is guaranteed that enough information is present to perform an RSA public key operation using mbedtls_rsa_public().

Parse a PKCS#1 (ASN.1) encoded private RSA key.

Parse a PKCS#1 (ASN.1) encoded public RSA key.

This function performs a private RSA operation to sign a message digest using PKCS#1. It is the generic wrapper for performing a PKCS#1 signature.

This function adds the message padding, then performs an RSA operation. It is the generic wrapper for performing a PKCS#1 encryption operation.

This function initializes an RSA context.

This function checks if a context contains an RSA private key and perform basic consistency checks. \warning This function should catch accidental misconfigurations like swapping of parameters, but it cannot establish full trust in neither the quality nor the consistency of the key material that was used to setup the given RSA context: Consistency: Imported parameters that are irrelevant for the implementation might be silently dropped. If dropped, the current function does not have access to them, and therefore cannot check them. See mbedtls_rsa_complete(). If you want to check the consistency of the entire content of a PKCS1-encoded RSA private key, for example, you should use mbedtls_rsa_validate_params() before setting up the RSA context. Additionally, if the implementation performs empirical checks, these checks substantiate but do not guarantee consistency. Quality: This function is not expected to perform extended quality assessments like checking that the prime factors are safe. Additionally, it is the responsibility of the user to ensure the trustworthiness of the source of his RSA parameters, which goes beyond what is effectively checkable by the library.

This function performs an RSA private key operation. \warning It is deprecated and a security risk to not provide a PRNG here and thereby prevent the use of blinding. Future versions of the library may enforce the presence of a PRNG.

This function completes an RSA context from a set of imported core parameters. To setup an RSA public key, precisely \c N and \c E must have been imported. To setup an RSA private key, sufficient information must be present for the other parameters to be derivable. The default implementation supports the following: Derive \c P, \c Q from \c N, \c D, \c E. Derive \c N, \c D from \c P, \c Q, \c E. Alternative implementations need not support these. If this function runs successfully, it guarantees that the RSA context can be used for RSA operations without the risk of failure or crash. \warning This function need not perform consistency checks for the imported parameters. In particular, parameters that are not needed by the implementation might be silently discarded and left unchecked. To check the consistency of the key material, see mbedtls_rsa_check_privkey().

This function performs an RSA operation, then removes the message padding. It is the generic wrapper for performing a PKCS#1 decryption operation. \warning When \p ctx->padding is set to #MBEDTLS_RSA_PKCS_V15, mbedtls_rsa_rsaes_pkcs1_v15_decrypt() is called, which is an inherently dangerous function (CWE-242).

This function exports CRT parameters of a private RSA key.

This function performs a PKCS#1 v2.1 PSS verification operation (RSASSA-PSS-VERIFY).

This function performs a public RSA operation and checks the message digest. This is the generic wrapper for performing a PKCS#1 verification.

Write a PKCS#1 (ASN.1) encoded private RSA key.

Parse a PKCS#1 (ASN.1) encoded public RSA key.

Export an RSA key to export representation

This function performs a PKCS#1 v1.5 decryption operation (RSAES-PKCS1-v1_5-DECRYPT). \warning This is an inherently dangerous function (CWE-242). Unless it is used in a side channel free and safe way (eg. implementing the TLS protocol as per 7.4.7.1 of RFC 5246), the calling code is vulnerable.

This function imports core RSA parameters, in raw big-endian binary format, into an RSA context. Any sequence of calls to this function should be followed by a call to mbedtls_rsa_complete(), which checks and completes the provided information to a ready-for-use public or private RSA key.

This function performs a PKCS#1 v2.1 OAEP decryption operation (RSAES-OAEP-DECRYPT).

This function performs a PKCS#1 v2.1 OAEP encryption operation (RSAES-OAEP-ENCRYPT).

This function performs a PKCS#1 v2.1 PSS signature operation (RSASSA-PSS-SIGN).

This function copies the components of an RSA context.

This function retrieves padding mode of initialized RSA context.

This function retrieves hash identifier of mbedtls_md_type_t type.

This function retrieves the length of the RSA modulus in bits.

This function generates an RSA keypair.

This function checks a public-private RSA key pair. It checks each of the contexts, and makes sure they match.

This function performs a PKCS#1 v1.5 encryption operation (RSAES-PKCS1-v1_5-ENCRYPT).

This function performs a PKCS#1 v1.5 signature operation (RSASSA-PKCS1-v1_5-SIGN).

This function performs a PKCS#1 v1.5 verification operation (RSASSA-PKCS1-v1_5-VERIFY).

This function performs a PKCS#1 v2.1 PSS verification operation (RSASSA-PSS-VERIFY).

This function is analogue to \c mbedtls_rsa_rsassa_pss_sign(). The only difference between them is that this function is more flexible on the parameters of \p ctx that are set with \c mbedtls_rsa_set_padding().

This function exports core parameters of an RSA key in raw big-endian binary format. If this function runs successfully, the non-NULL buffers pointed to by \p N, \p P, \p Q, \p D, and \p E are fully written, with additional unused space filled leading by zero Bytes. Possible reasons for returning #MBEDTLS_ERR_PLATFORM_FEATURE_UNSUPPORTED: An alternative RSA implementation is in use, which stores the key externally, and either cannot or should not export it into RAM. A SW or HW implementation might not support a certain deduction. For example, \p P, \p Q from \p N, \p D, and \p E if the former are not part of the implementation. If the function fails due to an unsupported operation, the RSA context stays intact and remains usable.