examples/l2fwd-crypto: remove key size validation
In the example application the key can be provided by the user or generated randomly by the example application. Then a validation is done in order to check if the key size is supported in the algorithm capabilities. A new feature flag is added in crypto PMDs to allow wrapped keys, hence, to allow wrapped keys, app should remove the validation of key size in the application and rely on a PMD key size validation. The validation is removed in case the key is provided by user and the RTE_CRYPTODEV_FF_CIPHER_WRAPPED_KEY feature flag is set, and kept in case the key should be generated by the application or RTE_CRYPTODEV_FF_CIPHER_WRAPPED_KEY is not set. Signed-off-by: Shiri Kuzin <shirik@nvidia.com> Acked-by: Matan Azrad <matan@nvidia.com> Acked-by: Akhil Goyal <gakhil@marvell.com>
This commit is contained in:
parent
07b0b75370
commit
3ea6ee38ec
@ -2126,12 +2126,21 @@ check_capabilities(struct l2fwd_crypto_options *options, uint8_t cdev_id)
|
||||
cap->sym.cipher.key_size.max,
|
||||
cap->sym.cipher.key_size.increment)
|
||||
!= 0) {
|
||||
RTE_LOG(DEBUG, USER1,
|
||||
"Device %u does not support cipher "
|
||||
"key length\n",
|
||||
if (dev_info.feature_flags &
|
||||
RTE_CRYPTODEV_FF_CIPHER_WRAPPED_KEY) {
|
||||
RTE_LOG(DEBUG, USER1,
|
||||
"Key length does not match the device "
|
||||
"%u capability. Key may be wrapped\n",
|
||||
cdev_id);
|
||||
return -1;
|
||||
} else {
|
||||
RTE_LOG(DEBUG, USER1,
|
||||
"Key length does not match the device "
|
||||
"%u capability\n",
|
||||
cdev_id);
|
||||
return -1;
|
||||
}
|
||||
}
|
||||
|
||||
/*
|
||||
* Check if length of the cipher key to be randomly generated
|
||||
* is supported by the algorithm chosen.
|
||||
|
Loading…
x
Reference in New Issue
Block a user