Skip to contentSkip to conversation

mesh: ELL encrypt dependancy README section added

PATCH In review Brian Gix 1 participant 2 messages May 31, 2019 Bluetooth drivers

lore
Share & tools
lore

Brian Gix

author
#0 lore raw

PATCH 1/1 mesh: ELL encrypt dependancy README section added

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.

---
 mesh/README | 14 ++++++++++++++
 1 file changed, 14 insertions(+)
mesh/README +14 -0
index 82fd5a017..f36b97c2b 100644
@@ -71,6 +71,20 @@ Each subdirectory contains the following files:
 The node.json and node.json.bak are in JSON format. All other files are stored
 in little endian binary format.
 
+Known Issues
+============
+
+Bluetooth Mesh makes heavy usage of AEAD-AES_CCM encryption, which is
+implemented in the Linux kernel on most platforms. Some platforms, including
+those with kernel versions including and prior to v4.8, did *not* correctly
+implement the AEAD encryption routines. If Mesh is to be ported to such a
+system, it will be the responsibility of the vendor to provide support for
+AEAD-AES_CCM encryption by some other method.
+
+Support for the required AEAD routines can be determined by running the unit
+tests provided with the ELL libraries used by Mesh. Specifically, the tests
+found in .../ell/unit/test-cipher.c
+
 Information
 ===========
 
Signature · 1 line
2.14.5
author
#1 lore raw

Patch Applied

Quoted 40 lines · Brian Gix

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.

---
 mesh/README | 14 ++++++++++++++
 1 file changed, 14 insertions(+)
mesh/README +0 -0
index 82fd5a017..f36b97c2b 100644
@@ -71,6 +71,20 @@ Each subdirectory contains the following files:
 The node.json and node.json.bak are in JSON format. All other files

are stored
in little endian binary format.

mesh/README +4 -0
+Known Issues
+============
+
+Bluetooth Mesh makes heavy usage of AEAD-AES_CCM encryption, which

is
+implemented in the Linux kernel on most platforms. Some platforms, including
+those with kernel versions including and prior to v4.8, did *not* correctly
+implement the AEAD encryption routines. If Mesh is to be ported to such a
+system, it will be the responsibility of the vendor to provide support for

mesh/README +3 -0
+AEAD-AES_CCM encryption by some other method.
+
+Support for the required AEAD routines can be determined by running

the unit
+tests provided with the ELL libraries used by Mesh. Specifically, the tests

mesh/README +2 -0
+found in .../ell/unit/test-cipher.c
+
 Information
 ===========