RTE_CRYPTO_ECDSA_OP_PARAM(3)

πŸ’– NAME πŸ’–

rte_crypto_ecdsa_op_param β€” bestie, this is the DPDK struct that holds all the params for an ECDSA operation, and we are obsessed with her πŸŽ€

(It lives in the DPDK Library Functions Manual, in case you were wondering where this slay came from ✨)


πŸ¦‹ SYNOPSIS πŸ¦‹

#include <rte_crypto_asym.h>

🌸 Data Fields 🌸

  • enum rte_crypto_asym_op_type op_type
  • rte_crypto_param message
  • rte_crypto_uint k
  • rte_crypto_uint r
  • rte_crypto_uint s

πŸ‘‘ DETAILED DESCRIPTION πŸ‘‘

So literally this whole struct is just "ECDSA operation params" β€” that's the entire vibe πŸ’…

It's defined at line 606 of the file rte_crypto_asym.h, no cap.


πŸ”₯ FIELD DOCUMENTATION πŸ”₯

⭐ enum rte_crypto_asym_op_type op_type

Okay so this one tells you whether you're doing signature generation or signature verification. That's it, that's the whole job 🫢

Defined at line 607 of rte_crypto_asym.h.

πŸ“ rte_crypto_param message

This is your input message digest β€” the thing that's gonna get signed, or the thing that's getting verified. Either way she's the star of the show 🌟

Defined at line 610 of rte_crypto_asym.h.

🧚 rte_crypto_uint k

The ECDSA per-message secret number, bestie. She's an integer kickin' it in the interval (1, n-1) πŸ”

Heads up, and this part matters: if the random number is generated by the PMD, then the 'rte_crypto_param.data' parameter should be set to NULL. Do not forget this, I am begging πŸ™ˆ

Defined at line 613 of rte_crypto_asym.h.

πŸ’œ rte_crypto_uint r

The r component of the elliptic curve signature ✍️

  • For signature generation: it's an output
  • For signature verification: it's an input

Defined at line 620 of rte_crypto_asym.h.

🌈 rte_crypto_uint s

The s component of the elliptic curve signature, and yes she's matching r's energy entirely πŸ’«

  • For signature generation: it's an output
  • For signature verification: it's an input

Defined at line 625 of rte_crypto_asym.h.


πŸŽ€ AUTHOR πŸŽ€

This one was generated automatically by Doxygen for DPDK from the source code β€” so nobody hand-wrote it, it basically spawned fully formed like a little documentation icon πŸ¦‹


okay that's the whole page, ily, go sign something πŸ’–

This was DPDK, Version 25.11.3, and you were reading rte_crypto...sa_op_param(3) β€” slay, periodt πŸ‘‘βœ¨

πŸ“¦ where this page comes from