RTE_SECURITY_TLS_RECORD_XFORM(3)

πŸ’– NAME πŸ’–

rte_security_tls_record_xform β€” bestie, this is the struct that holds all your TLS record session config πŸŽ€ (it's from the Library Functions Manual, iykyk)


✨ SYNOPSIS ✨

#include <rte_security.h>

πŸ¦‹ Data Fields

  • enum rte_security_tls_version ver
  • enum rte_security_tls_sess_type type
  • struct rte_security_tls_record_sess_options options
  • struct rte_security_tls_record_lifetime life

🌸 Detailed Description 🌸

TLS record protocol session configuration.

This structure contains data required to create a TLS record security session. literally the starter pack for spinning up a session, no cap.

Definition at line 678 of file rte_security.h.

πŸ’… Field Documentation πŸ’…

  • enum rte_security_tls_version ver β€” TLS record version. bestie this is the whole vibe check on which TLS we're doing.

Definition at line 680 of file rte_security.h.

  • enum rte_security_tls_sess_type type β€” TLS record session type. what kind of session we're serving today πŸ’

Definition at line 682 of file rte_security.h.

  • struct rte_security_tls_record_sess_options options β€” TLS record session options. all the little knobs and toggles, obsessed.

Definition at line 684 of file rte_security.h.

  • struct rte_security_tls_record_lifetime life β€” TLS record session lifetime. how long this session gets to be the main character ⏳

Definition at line 686 of file rte_security.h.

  • uint64_t seq_no β€” Starting sequence number. 6B starting sequence number to be used. yes, six bytes, exact, don't come for me πŸ™ˆ

Definition at line 691 of file rte_security.h.

  • uint8_t imp_nonce[RTE_SECURITY_DTLS_1_2_IMP_NONCE_LEN] β€” Implicit nonce to be used for AEAD algos. slay, AEAD girlies stay winning πŸ”₯

Definition at line 693 of file rte_security.h.

  • struct { ... } tls_1_2 β€” TLS 1.2 parameters. the classic, still iconic ✨
  • uint32_t min_payload_len β€” Minimum payload length (in case of write sessions). For shorter inputs, the payload would be padded appropriately before performing crypto transformations. so if your input is giving smol, it gets padded first, then crypto does its thing 🧚

Definition at line 707 of file rte_security.h.

  • struct { ... } tls_1_3 β€” TLS 1.3 parameters. the new gen, we love her πŸ’œ
  • uint16_t epoch β€” Epoch value to be used.

Definition at line 713 of file rte_security.h.

  • uint32_t ar_win_sz β€” Anti replay window size to enable sequence replay attack handling. Anti replay check is disabled if the window size is 0. ⚠️ like, that is a real off switch β€” set it to 0 and the replay handling is just not there, so pls be intentional about that one.

Definition at line 722 of file rte_security.h.

  • struct { ... } dtls_1_2 β€” DTLS 1.2 parameters

πŸ‘‘ Author πŸ‘‘

Generated automatically by Doxygen for DPDK from the source code. not a human writing this, a robot did, and honestly? she ate πŸ’…


okay that's the whole page, bestie πŸ’– this was DPDK, Version 25.11.3, and the manual page is rte_securi...ecord_xform(3) πŸŽ€ go forth and configure your TLS record session, mwah 🫢✨

πŸ“¦ where this page comes from