rte_crypto_dh_op_param(3)

📦 version 26.03, in nixos 26.05, nixpkgs unstable

💅 rte_crypto_dh_op_param 💅

ok so bestie, welcome to the rte_crypto_dh_op_param(3) page — yes that's a manual page, from the Library Functions Manual, and yes it's about Diffie-Hellman. Cryptography!! We love her!! 🔥 Let's get into it because this struct is lowkey the whole gossip of the key-exchange world.

✨ 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. That's it, that's the vibe — this is the little container that carries your key-exchange stuff around. 💫

Note: — so there's literally a note here in the original and it's just a colon : with nothing after it 😭 bestie it's giving unfinished thought. Nothing to see, moving on 💀

It's defined at line 503 of the file rte_crypto_asym.h. Slay, we stan a specific line number. 📍

👑 Field Documentation 👑

🧚 enum rte_crypto_asym_ke_type ke_type

Key exchange operation type — like, which flavor of key exchange are we doing right now. Defined at line 504 of the file rte_crypto_asym.h. ✨

🦋 rte_crypto_uint priv_key

ok so this one has a whole personality depending on context, listen:

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

And the special case that lives in my head rent free: if priv_key.length is 0 and ke_type is set with RTE_CRYPTO_ASYM_KE_PUB_KEY_GENERATE, then the CSRNG capable device will generate a private key and use it for public key generation. Like it just does it for you. main character energy fr fr. 👑

Defined at line 506 of the file rte_crypto_asym.h.

🌈 rte_crypto_uint pub_key

  • Output — the 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.

So sometimes she's yours, sometimes she's your bestie's. Depends on the ke_type vibe check. 💅

Defined at line 520 of the file rte_crypto_asym.h.

🍓 rte_crypto_uint shared_secret

Output — the calculated shared secret, when ke_type is RTE_CRYPTO_ASYM_KE_SHARED_SECRET_COMPUTE. This is the moment we've all been waiting for, the whole point of the operation, the finale, the ate-and-left-no-crumbs. 🔥

Defined at line 528 of the file rte_crypto_asym.h.

🌟 Author 🌟

Generated automatically by Doxygen for DPDK from the source code. Not a human, just a robot doing its little robot thing 🤖💜

ok that's the page!! mwah, go encrypt something 🫶

sign-off time bestie: this iconic little page comes courtesy of DPDK, Version 26.03.0 — no cap, that's the version, go forth and Diffie-Hellman responsibly 💖🎀✨
📦 where this page comes from