rte_crypto...m_encap_op(3)

πŸ“¦
version 25.11.3 Β· 4 versions
, in ubuntu resolute, ubuntu stonking

πŸ’– NAME πŸ’–

rte_crypto_ml_kem_encap_op β€” bestie, this is the struct you reach for when you're doing PQC ML-KEM encapsulation πŸ’…


✨ SYNOPSIS ✨

#include <rte_crypto_asym.h>

πŸ¦‹ Data Fields

  • rte_crypto_param message
  • rte_crypto_param ek
  • rte_crypto_param cipher
  • rte_crypto_param sk

🌸 DETAILED DESCRIPTION 🌸

okay so, this is the PQC ML-KEM ENCAP op ✨

It's holding all the parameters for the PQC ML-KEM encapsulation operation β€” the whole lil squad of things you gotta hand over before the math does its thing.

fr fr, this is defined at line 861 of the file rte_crypto_asym.h. no cap. πŸ‘‘

πŸŽ€ FIELD DOCUMENTATION πŸŽ€

πŸ’Œ rte_crypto_param message

The message β€” and bestie, it's 32 bytes in length β€” used for randomness. it's giving entropy, but make it cute 🎲✨

Definition at line 862 of file rte_crypto_asym.h.

πŸ”‘ rte_crypto_param ek

The encapsulation key. yep, that's the one. the key that does the encapsulating, main character energy πŸ’…

Definition at line 865 of file rte_crypto_asym.h.

🫧 rte_crypto_param cipher

Pointer to output data 🌈 which is, specifically:

  • The computed cipher.
  • Refer rte_crypto_ml_kem_cipher_size for size of buffer.
bestie do NOT forget to check rte_crypto_ml_kem_cipher_size for the buffer size, i'm literally begging πŸ™ˆ

Definition at line 868 of file rte_crypto_asym.h.

🀫 rte_crypto_param sk

Pointer to output data πŸ’œ and that output is:

  • The computed shared secret key (32 bytes).

Definition at line 875 of file rte_crypto_asym.h.


πŸ‘‘ AUTHOR πŸ‘‘

Generated automatically by Doxygen for DPDK from the source code. so iconic of it, honestly. the docs literally wrote themselves 😭✨


aaaand that's the whole vibe check, bestie 🫢 this lil page came to you straight from DPDK, version 25.11.3 🌈, and yeah β€” it's the rte_crypto...m_encap_op(3) page from the Library Functions Manual. go forth and encapsulate, you absolute legend πŸ’–πŸŽ€πŸ¦‹

πŸ“¦ where this page comes from