rte_crypto_dh_op_param(3)

📦
version 25.11.3 · 9 versions
, in ubuntu resolute, ubuntu stonking

💖 rte_crypto_dh_op_param 💖

okay so welcome bestie, you're reading the rte_crypto_dh_op_param(3) page from the DPDK library functions manual, and it's literally just the vibe breakdown of one struct. it's giving "short but important", and we're gonna go through every single field together 🫶

🌸 NAME 🌸

rte_crypto_dh_op_param — the struct that holds all your Diffie-Hellman operation params ✨

🎀 SYNOPSIS 🎀

#include <rte_crypto_asym.h>

✨ Data Fields ✨

  • enum rte_crypto_asym_ke_type ke_type
  • rte_crypto_uint priv_key
  • rte_crypto_uint pub_key
  • rte_crypto_uint shared_secret

💜 Detailed Description 💜

Diffie-Hellman Operations params, periodt. that's the whole summary, no notes app essay needed 💅

Note — bestie the note here is literally just a : and nothing else. that's it. that's the note. 💀

it lives at Definition line 503 of file rte_crypto_asym.h.

👑 Field Documentation 👑

🌈 enum rte_crypto_asym_ke_type ke_type

Key exchange operation type. like, which move are we making in this exchange, yk?

Definition line 504 of file rte_crypto_asym.h.

🦋 rte_crypto_uint priv_key

okay this one is doing double duty depending on the vibe of ke_type, so pay attention bestie:

  • Output — your generated private key, but only when ke_type is RTE_CRYPTO_ASYM_KE_PRIV_KEY_GENERATE.
  • Input — your private key when ke_type is one of:
RTE_CRYPTO_ASYM_KE_PUB_KEY_GENERATE
RTE_CRYPTO_ASYM_KE_SHARED_SECRET_COMPUTE

and here's the lil plot twist 🫢 in case priv_key.length is 0 and ke_type is set with RTE_CRYPTO_ASYM_KE_PUB_KEY_GENERATE, a CSRNG capable device will generate a private key and use it for public key generation. so it's lowkey doing the work for you, iconic behaviour honestly.

Definition line 506 of file rte_crypto_asym.h.

🍓 rte_crypto_uint pub_key

  • Output — your generated public key, when ke_type is RTE_CRYPTO_ASYM_KE_PUB_KEY_GENERATE.
  • Input — the peer's public key, when ke_type is RTE_CRYPTO_ASYM_KE_SHARED_SECRET_COMPUTE. yes you need their key, it's a whole two-player game 🎮

Definition line 520 of file rte_crypto_asym.h.

🧚 rte_crypto_uint shared_secret

Output — the calculated shared secret, and it only shows up when ke_type is RTE_CRYPTO_ASYM_KE_SHARED_SECRET_COMPUTE. this is the moment, the main character field, the payoff 🔥

Definition line 528 of file rte_crypto_asym.h.

⭐ Author ⭐

Generated automatically by Doxygen for DPDK from the source code. so no human wrote this by hand, shoutout to the robot 🫡

and that's the whole page bestie, you ate it 💅🌸✨ — this was rte_crypto_dh_op_param from DPDK, Version 25.11.3, mwah, go forth and compute your shared secrets responsibly 🎀💖🌈

📦 where this page comes from