Trond Einar Snekvik eca0141152 Bluetooth: Mesh: Isolate cryptographic material ... This is a major refactoring of the handling of the cryptographic material of both the network and transport layers. The aim is to encapsulate the key object manipulation, and improve overall modularity. Pulls Applications and Subnets out of the bt_mesh and into separate modules, with static storage types on the data. This has several side-effects: - The Config Server no longer operates directly on the bt_mesh.subs and bt_mesh.apps lists, but goes through a public configuration interface, following the pattern set in #27908. - All iteration through the keys is done through iteration APIs - Key resolution on RX and TX is centralized. - Changes to the keys triggers events the other modules can register handlers for. - Friendship credentials are stored in the lpn and friend structures. Part of #27842. Signed-off-by: Trond Einar Snekvik <Trond.Einar.Snekvik@nordicsemi.no>		2020-10-22 14:36:02 +03:00
..
access.h	Bluetooth: Mesh: Isolate cryptographic material	2020-10-22 14:36:02 +03:00
cdb.h	bluetooth: mesh: cdb: fix include files and add language directive	2020-07-08 16:47:10 +03:00
cfg_cli.h	Bluetooth: Mesh: Config Client network transmit set/get API	2020-10-02 11:30:12 +02:00
cfg_srv.h
cfg.h	Bluetooth: Mesh: Isolate cryptographic material	2020-10-22 14:36:02 +03:00
health_cli.h
health_faults.h
health_srv.h
main.h
proxy.h