cryptodev: clarify RSA verify with none padding

- Clarified where should output be stored of signature
decryption with padding none.
PMD is not able to know what padding algorithm was used,
therefore decrypted signature should be returned to the user.
- Removed incorrect big-endian constraints.
Not all data in RSA can be treated as big endian integer,
therefore some of the constraints were lifted.

Signed-off-by: Arek Kusztal <arkadiuszx.kusztal@intel.com>
Acked-by: Fan Zhang <roy.fan.zhang@intel.com>
Acked-by: Akhil Goyal <gakhil@marvell.com>

diff --git a/lib/cryptodev/rte_crypto_asym.h b/lib/cryptodev/rte_crypto_asym.h
index 0e3051337ec0d7cb3035a7f977d18bef19013814..4ef7b2b579235fe61a67ec5279a70968e685c0d4 100644 (file)
--- a/lib/cryptodev/rte_crypto_asym.h
+++ b/lib/cryptodev/rte_crypto_asym.h
@@ -398,8 +398,6 @@ struct rte_crypto_rsa_op_param {
         * (i.e. must be at least RSA key size). The message.length
         * field should be 0 and will be overwritten by the PMD
         * with the decrypted length.
-        *
-        * All data is in Octet-string network byte order format.
         */
 
        rte_crypto_param cipher;
@@ -414,7 +412,8 @@ struct rte_crypto_rsa_op_param {
         * at least RSA key size). The cipher.length field should
         * be 0 and will be overwritten by the PMD with the encrypted length.
         *
-        * All data is in Octet-string network byte order format.
+        * When RTE_CRYPTO_RSA_PADDING_NONE and RTE_CRYPTO_ASYM_OP_VERIFY
+        * selected, this is an output of decrypted signature.
         */
 
        rte_crypto_param sign;
@@ -428,8 +427,6 @@ struct rte_crypto_rsa_op_param {
         * with enough memory to hold signature output (i.e. must be
         * at least RSA key size). The sign.length field should
         * be 0 and will be overwritten by the PMD with the signature length.
-        *
-        * All data is in Octet-string network byte order format.
         */
 
        struct rte_crypto_rsa_padding padding;