From: Brian Gix <brian.gix@intel.com>
To: linux-bluetooth@vger.kernel.org
Cc: Brian Gix <brian.gix@intel.com>
Subject: [PATCH 1/1] mesh: Enforce HIGH security when provisioning
Date: Fri, 1 Sep 2017 08:35:46 -0700 [thread overview]
Message-ID: <20170901153546.17111-1-brian.gix@intel.com> (raw)
---
mesh/prov.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/mesh/prov.c b/mesh/prov.c
index 32785dd..f78a876 100644
--- a/mesh/prov.c
+++ b/mesh/prov.c
@@ -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
--
2.9.5
next reply other threads:[~2017-09-01 15:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-01 15:35 Brian Gix [this message]
2017-09-03 19:15 ` [PATCH 1/1] mesh: Enforce HIGH security when provisioning Luiz Augusto von Dentz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170901153546.17111-1-brian.gix@intel.com \
--to=brian.gix@intel.com \
--cc=linux-bluetooth@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).