Home
last modified time | relevance | path

Searched refs:secured (Results 1 – 8 of 8) sorted by relevance

/Zephyr-latest/include/zephyr/net/
Dieee802154_pkt.h219 static inline void net_pkt_set_ieee802154_frame_secured(struct net_pkt *pkt, bool secured) in net_pkt_set_ieee802154_frame_secured() argument
221 net_pkt_cb_ieee802154(pkt)->frame_secured = secured; in net_pkt_set_ieee802154_frame_secured()
/Zephyr-latest/samples/bluetooth/peripheral_sc_only/
DREADME.rst12 accept connections that are secured using security level 4 (FIPS).
/Zephyr-latest/soc/nordic/nrf54l/
DKconfig73 will be constant and kept at a minimum. This is secured by forcing a set
/Zephyr-latest/doc/services/device_mgmt/
Dota.rst31 this implementation, the connection between cloud and device is secured using
/Zephyr-latest/doc/services/
Dsecure_storage.rst72 It is only secured at rest. Protecting it at runtime as well
/Zephyr-latest/doc/security/
Dsensor-threat.rst187 communication received over a secured channel to the service.
216 secrecy. The communication shall be secured by the following:
/Zephyr-latest/samples/net/mqtt_publisher/
DREADME.rst211 specified by SERVER_ADDR in config.h. If the broker is secured using TLS, users
/Zephyr-latest/doc/connectivity/networking/api/
Dlwm2m.rst233 configured to use normal unsecure network sockets or sockets secured via DTLS.