DPDK patches and discussions
 help / color / mirror / Atom feed
* [RFC] cryptodev: asymmetric crypto random number source
@ 2021-12-03 10:03 Kusztal, ArkadiuszX
  2021-12-13  8:14 ` Akhil Goyal
  0 siblings, 1 reply; 4+ messages in thread
From: Kusztal, ArkadiuszX @ 2021-12-03 10:03 UTC (permalink / raw)
  To: gakhil, Anoob Joseph, Zhang, Roy Fan; +Cc: dev

[-- Attachment #1: Type: text/plain, Size: 1126 bytes --]

ECDSA op:
rte_crypto_param k;
               /**< The ECDSA per-message secret number, which is an integer
               * in the interval (1, n-1)
               */
DSA op:
               No 'k'.

This one I think have described some time ago:
Only PMD that verifies ECDSA is OCTEON which apparently needs 'k' provided by user.
Only PMD that verifies DSA is OpenSSL PMD which will generate its own random number internally.

So in case PMD supports one of these options (or especially when supports both) we need to give some information here.

The most obvious option would be to change rte_crypto_param k -> rte_crypto_param *k
In case (k == NULL) PMD should generate it itself if possible, otherwise it should push crypto_op to the response ring with appropriate error code.

Another options would be:

  *   Extend rte_cryptodev_config and rte_cryptodev_info with information about random number generator for specific device (though it would be ABI breakage)
  *   Provide some kind of callback to get random number from user (which could be useful for other things like RSA padding as well)




[-- Attachment #2: Type: text/html, Size: 6854 bytes --]

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2021-12-17 15:26 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-12-03 10:03 [RFC] cryptodev: asymmetric crypto random number source Kusztal, ArkadiuszX
2021-12-13  8:14 ` Akhil Goyal
2021-12-13  9:27   ` Ramkumar Balu
2021-12-17 15:26     ` Kusztal, ArkadiuszX

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).