From: Brian Gix <brian.gix@intel.com>
To: linux-bluetooth@vger.kernel.org
Cc: marcel@holtmann.org, johan.hedberg@gmail.com,
inga.stotland@intel.com, Brian Gix <brian.gix@intel.com>
Subject: [PATCH BlueZ 0/2] Central Net Key storage cache for multiple Nodes
Date: Wed, 19 Sep 2018 13:44:15 -0700 [thread overview]
Message-ID: <20180919204415.20510-1-brian.gix@intel.com> (raw)
The strategy for Bluetooth Mesh is to allow each application that want to use
mesh services to operate as an independant Node on one or more Mesh networks.
To enable this, at the lowest network layer, we are creating a cache of Network
Keys and associated credentials (NIDs, Privacy Keys, Encryption Keys, etc).
This will allow Network decryption to be done once per incoming packets,
without requiring each "Node" on the local device to handle them redundantly.
Brian Gix (2):
mesh: Add centralized caching Net Key management
mesh: Refactor friend.c and net.c for central key DB
Makefile.mesh | 1 +
mesh/friend.c | 188 +++++++++-------------
mesh/friend.h | 2 +-
mesh/net.c | 476 +++++++++++++++----------------------------------------
mesh/net.h | 14 +-
mesh/net_keys.c | 326 +++++++++++++++++++++++++++++++++++++
mesh/net_keys.h | 33 ++++
mesh/provision.c | 5 +-
8 files changed, 572 insertions(+), 473 deletions(-)
create mode 100644 mesh/net_keys.c
create mode 100644 mesh/net_keys.h
--
2.14.4
next reply other threads:[~2018-09-19 20:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-19 20:44 Brian Gix [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-09-19 20:40 [PATCH BlueZ 0/2] Central Net Key storage cache for multiple Nodes Brian Gix
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=20180919204415.20510-1-brian.gix@intel.com \
--to=brian.gix@intel.com \
--cc=inga.stotland@intel.com \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=marcel@holtmann.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).