MIN_PAYLOAD_LEN(3)
π rte_securi...ecord_xform(3) β from the Library Functions Manual π
okay so bestie, before anything else: this page lives in the Library Functions Manual, and the star of the show is rte_security_tls_record_xform. she's a struct, she's got range, and she's about to make your TLS sessions make sense. buckle up. π¦
β¨ NAME β¨
rte_security_tls_record_xform β literally the blueprint for setting up a TLS record security session. that's the whole vibe. π«Ά
πΈ SYNOPSIS πΈ
#include <rte_security.h>
π Data Fields
enum rte_security_tls_version verenum rte_security_tls_sess_type typestruct rte_security_tls_record_sess_options optionsstruct rte_security_tls_record_lifetime life
π Detailed Description π
TLS record protocol session configuration. periodt.
this struct holds all the data you need to actually create a TLS record security session β it's giving "everything you need, nothing you don't." π
Definition at line 678 of file rte_security.h.
π Field Documentation π
π enum rte_security_tls_version ver
TLS record version. the receipts of which TLS you're on. β¨
Definition at line 680 of file rte_security.h.
π enum rte_security_tls_sess_type type
TLS record session type. she has a type, and it's this one. π
Definition at line 682 of file rte_security.h.
π struct rte_security_tls_record_sess_options options
TLS record session options. all the little extras. π
Definition at line 684 of file rte_security.h.
π struct rte_security_tls_record_lifetime life
TLS record session lifetime. how long she lives her truth. πΈ
Definition at line 686 of file rte_security.h.
π uint64_t seq_no
Starting sequence number.
6B starting sequence number to be used. yes, 6 bytes specifically, no cap. π₯
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. iconic little nonce, doing nonce things for the AEAD girlies. β¨
Definition at line 693 of file rte_security.h.
π struct { ... } tls_1_2
TLS 1.2 parameters. the classic. the icon. π
π 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 like β if your input is shorter than this, it gets padded first, and then the crypto transformations happen. order matters bestie, don't skip ahead. π§
Definition at line 707 of file rte_security.h.
π struct { ... } tls_1_3
TLS 1.3 parameters. the newer one. she ate. π
π 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.
β οΈ real talk: set this to 0 and the anti replay check is straight up off. not disabled-in-a-cute-way, disabled-disabled. so maybe don't unless you mean it. π
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. it wasn't me, it was the robot. π€π
and that's the whole page, bestie β every field, every line number, every vibe intact. mwah. π
π« sign-off time: this iconic little page comes to you from DPDK, Version 26.03.0 β go forth and configure your TLS record sessions responsibly. π«Άβ¨
π¦ where this page comes from
- nixos 26.05: dpdk 26.03
- nixpkgs unstable: dpdk 26.03
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms