Zephyr API Documentation 4.0.0
A Scalable Open Source RTOS
Loading...
Searching...
No Matches
ieee802154_security_ctx Struct Reference

Interface-level security attributes, see section 9.5. More...

#include <ieee802154.h>

Data Fields

uint32_t frame_counter
 Interface-level outgoing frame counter, section 9.5, table 9-8, secFrameCounter.
 
uint8_t key [16]
 Interface-level frame encryption security key material.
 
uint8_t key_len
 Length in bytes of the interface-level security key material.
 
uint8_t level: 3
 Frame security level, possible values are defined in section 9.4.2.2, table 9-6.
 
uint8_t key_mode: 2
 Frame security key mode.
 

Detailed Description

Interface-level security attributes, see section 9.5.

Field Documentation

◆ frame_counter

uint32_t ieee802154_security_ctx::frame_counter

Interface-level outgoing frame counter, section 9.5, table 9-8, secFrameCounter.

Only used when the driver does not implement key-specific frame counters.

◆ key

uint8_t ieee802154_security_ctx::key[16]

Interface-level frame encryption security key material.

Currently native L2 only supports a single secKeySource, see section 9.5, table 9-9, in combination with secKeyMode zero (implicit key mode), see section 9.4.2.3, table 9-7.

Warning
This is no longer in accordance with the 2015+ versions of the standard and needs to be extended in the future for full security procedure compliance.

◆ key_len

uint8_t ieee802154_security_ctx::key_len

Length in bytes of the interface-level security key material.

◆ key_mode

uint8_t ieee802154_security_ctx::key_mode

Frame security key mode.

Currently only implicit key mode is partially supported, see section 9.4.2.3, table 9-7, secKeyMode.

Warning
This is no longer in accordance with the 2015+ versions of the standard and needs to be extended in the future for full security procedure compliance.

◆ level

uint8_t ieee802154_security_ctx::level

Frame security level, possible values are defined in section 9.4.2.2, table 9-6.

Warning
Currently native L2 allows to configure one common security level for all frame types, commands and information elements. This is no longer in accordance with the 2015+ versions of the standard and needs to be extended in the future for full security procedure compliance.

The documentation for this struct was generated from the following file: