| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
| |
Due to known AEAD encryption deficiencies in old versions of the
kernel, we have added a section on identifying and back-porting
mesh to otherwise non-supporting platforms.
|
| |
|
|
|
|
| |
Add a tree structure to a nodes data storage, in order to safely handle
Replay Protection list, Refactor local Sequence Numbers, and add Key
storage for Config Client nodes.
|
| |
|
|
|
|
|
|
|
|
|
| |
Instead of keeping track of unique 16bit node identifiers, reuse their
UUIDs to create both storage directories and dbus objects.
Because of that:
- UUID is no longer stored in the JSON file, it's inferred from the
directory name instead
- Join(), CreateNetwork() and ImportLocalNode() APIs return an error if
given UUID already registered within the daemon
|
| |
|
|
|
| |
This file contains instructions for Bluetooth mesh daemon
configuration and description of the persistent storage.
|
| |
|
|
| |
This is a temporary location until the unified mesh solution is provided
|
| |
|
