The Key Wrap approach is used by applications in order to protect keys
located in untrusted storage or transmitted over untrusted
communications networks. The constructions are typically built from
standard primitives such as block ciphers and cryptographic hash

The Key Wrap method and its parameters are a secret between the keys
provider and the device, means that the device is preconfigured for
this method using very secured way.

The key wrap method may change the key length and layout.

Add a description for the cipher transformation key to allow wrapped key
to be forwarded by the same API.

Signed-off-by: Matan Azrad <>
 lib/librte_cryptodev/rte_crypto_sym.h | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/lib/librte_cryptodev/rte_crypto_sym.h 
index 5973e31..6aca2c7 100644
--- a/lib/librte_cryptodev/rte_crypto_sym.h
+++ b/lib/librte_cryptodev/rte_crypto_sym.h
@@ -200,6 +200,13 @@ struct rte_crypto_cipher_xform {
                uint16_t length;        /**< key length in bytes */
        } key;
        /**< Cipher key
+        * The original key data may be provided wrapped (encrypted) using a key
+        * wrap algorithm such as AES key wrap (from rfc3394) or other. In such
+        * case, the wrapping details is a secret between the key provider and
+        * the device. Such key wrapping may increase the length of the provided
+        * key beyond the advertised supported key size. Hence it is the
+        * responsibility of the driver/device to validate the length of the
+        * provided key.
         * For the RTE_CRYPTO_CIPHER_AES_F8 mode of operation, will
         * point to a concatenation of the AES encryption key followed by a

Reply via email to