linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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: remove hardcoded keys to force randomization
Date: Tue, 29 Aug 2017 12:51:21 -0700	[thread overview]
Message-ID: <20170829195121.9868-1-brian.gix@intel.com> (raw)

---
 mesh/prov_db.json | 5 +----
 1 file changed, 1 insertion(+), 4 deletions(-)

diff --git a/mesh/prov_db.json b/mesh/prov_db.json
index d810a7d..dbed934 100644
--- a/mesh/prov_db.json
+++ b/mesh/prov_db.json
@@ -1,25 +1,22 @@
 {
   "$schema":"file:\/\/\/Bluetooth SIG\/Mesh\/schema\/mesh.jsonschema",
   "meshName":"Intel BT Mesh",
-  "IVindex":5,
+  "IVindex":1,
   "IVupdate":0,
   "netKeys":[
     {
       "index":0,
       "keyRefresh":0,
-      "key":"18eed9c2a56add85049ffc3c59ad0e12"
     }
   ],
   "appKeys":[
     {
       "index":0,
       "boundNetKey":0,
-      "key":"4f68ad85d9f48ac8589df665b6b49b8a"
     },
     {
       "index":1,
       "boundNetKey":0,
-      "key":"2aa2a6ded5a0798ceab5787ca3ae39fc"
     }
   ],
   "provisioners":[
-- 
2.9.5


                 reply	other threads:[~2017-08-29 19:51 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20170829195121.9868-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).