rte_security_macsec_sa(3)

πŸ“¦ version 26.03, in nixos 26.05, nixpkgs unstable

πŸ’– rte_security_macsec_sa β€” the MACsec SA glow-up πŸ’–

okay so bestie, welcome to the rte_security_macsec_sa page from the DPDK Library Functions Manual 🌸 this one's a struct, and honestly? she's giving "secure association configuration, but make it fashion" ✨


✨ NAME ✨

rte_security_macsec_sa β€” literally the MACsec secure association (SA) configuration structure, no cap πŸ‘‘


πŸ¦‹ SYNOPSIS πŸ¦‹

#include <rte_security.h>

πŸŽ€ Data Fields πŸŽ€

enum rte_security_macsec_direction dir
struct {
   const uint8_t * data
   uint16_t length
} key
uint8_t salt [RTE_SECURITY_MACSEC_SALT_LEN]
uint8_t an: 2
uint32_t ssci
uint32_t xpn
uint32_t next_pn

that's the whole squad right there πŸ’… nine-ish fields, all iconique, all accounted for.


🌈 Detailed Description 🌈

rte_security_macsec_sa is the MACsec secure association (SA) configuration structure πŸ’– that's it, that's the vibe. she holds the config for one SA and she does it well.

ngl the source says she lives at definition line 352 of file rte_security.h β€” go visit her sometime 🫢

πŸ’œ Field Documentation πŸ’œ

πŸ’« enum rte_security_macsec_direction dir

direction of SA 🧭 β€” which way the traffic's headed, bestie.

definition line 354 of file rte_security.h.

πŸ’« const uint8_t* data

pointer to key data πŸ”‘ β€” like, the actual key material lives over there, this is just the pointer.

definition line 357 of file rte_security.h.

πŸ’« uint16_t length

key length in bytes πŸ“ β€” how many bytes we're working with, fr fr.

definition line 358 of file rte_security.h.

πŸ’« struct { ... } key

MACsec SA key for AES-GCM 128/256 πŸ” β€” both flavours, she's flexible like that.

πŸ’« uint8_t salt[RTE_SECURITY_MACSEC_SALT_LEN]

96-bit value distributed by key agreement protocol πŸ§‚βœ¨ β€” not the kind of salt you put on fries, the cryptographic kind, iykyk.

definition line 361 of file rte_security.h.

πŸ’« uint8_t an

association number to be used πŸ”’ β€” which AN slot we're rolling with.

definition line 363 of file rte_security.h.

πŸ’« uint32_t ssci

Short Secure Channel Identifier, to be used for XPN cases πŸ†” β€” yes, only for the XPN situations, don't come for her otherwise.

definition line 365 of file rte_security.h.

πŸ’« uint32_t xpn

Extended packet number πŸ”’πŸ”₯ β€” the extended one, obviously.

definition line 367 of file rte_security.h.

πŸ’« uint32_t next_pn

Packet number expected/ to be used for next packet of this SA πŸ“¬ β€” like, the next packet's number, this SA's business only.

definition line 369 of file rte_security.h.


🧚 Author 🧚

Generated automatically by Doxygen for DPDK from the source code πŸ€–πŸ’– so like, no human wrote this, the robot did, and she ate.


πŸ’€ friendly reminder that this whole page is machine-generated documentation for a struct β€” the field list above is the entire truth of her, don't go reading extra behaviour into it, bestie πŸ™ˆ

and that's the page!! πŸŽ€ written by Doxygen for DPDK, from the source code, version 26.03.0 β€” catch you on the next one, mwah πŸ’‹βœ¨

πŸ“¦ where this page comes from