Skip to contentSkip to conversation

mesh: Enforce HIGH security when provisioning

PATCH In review Brian Gix 2 participants 2 messages Sep 1, 2017 – Sep 3, 2017 Bluetooth drivers

lore
Share & tools
lore

Brian Gix

author
#0 lore raw

PATCH 1/1 mesh: Enforce HIGH security when provisioning

---
 mesh/prov.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
mesh/prov.c +1 -1
index 32785dd..f78a876 100644
@@ -57,7 +57,7 @@
 #define MESH_PROV_SEC_LOW	0
 
 /* For Deployment, Security levels below HIGH are *not* recomended */
-#define mesh_gatt_prov_security()	MESH_PROV_SEC_MED
+#define mesh_gatt_prov_security()	MESH_PROV_SEC_HIGH
 
 #define PROV_INVITE	0x00
 #define PROV_CAPS	0x01
Signature · 1 line
2.9.5
maintainer
#1 lore raw

HI Brian,

Quoted 9 lines · Brian Gix
---
 mesh/prov.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
mesh/prov.c +0 -0
index 32785dd..f78a876 100644

mesh/prov.c line 60

Quoted 5 lines
mesh/prov.c +1 -1
@@ -57,7 +57,7 @@
 #define MESH_PROV_SEC_LOW      0
 
 /* For Deployment, Security levels below HIGH are *not* recomended */
-#define mesh_gatt_prov_security()      MESH_PROV_SEC_MED
+#define mesh_gatt_prov_security()      MESH_PROV_SEC_HIGH

I fine having the security it as high by default, but should we have a command to set to other levels for testing purposes?

Quoted 9 lines
mesh/prov.c +0 -1
 #define PROV_INVITE    0x00
 #define PROV_CAPS      0x01
--

2.9.5

--
To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

Signature · 1 line
Luiz Augusto von Dentz