From: Brian Gix <brian.gix@intel.com>
To: linux-bluetooth@vger.kernel.org
Cc: inga.stotland@intel.com, brian.gix@intel.com
Subject: [PATCH BlueZ v3 0/6] mesh: Add App and Net Key Refresh keyring back-end
Date: Thu, 23 May 2019 09:13:23 -0700 [thread overview]
Message-ID: <20190523161329.13017-1-brian.gix@intel.com> (raw)
This is version 3 of the patch set that now implements the following:
On interface org.bluez.mesh.Management1:
CreateSubnet()
ImportSubnet()
UpdateSubnet()
DeleteSubnet()
CreateAppKey()
ImportAppKey()
UpdateAppKey()
DeleteAppKey()
CompleteAppKeyUpdate()
SetKeyPhase()
ImportRemoteNode()
DeleteRemoteNode()
Brian Gix (6):
mesh: Add new method for Key Refresh procedure
mesh: Centralize definition of PRIMARY_NET_IDX
mesh: Implement Net Key keyring storage handling
mesh: Implement App Key keyring storage handling
mesh: Implement Key Refresh Phasing in keyring
mesh: Implement remote dev key methods for keyring
doc/mesh-api.txt | 66 ++++++++++----
mesh/manager.c | 264 ++++++++++++++++++++++++++++++++++++++++++++++++-------
mesh/mesh-defs.h | 1 +
mesh/node.c | 12 ++-
4 files changed, 285 insertions(+), 58 deletions(-)
--
2.14.5
next reply other threads:[~2019-05-23 16:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-23 16:13 Brian Gix [this message]
2019-05-23 16:13 ` [PATCH BlueZ v3 1/6] mesh: Add new method for Key Refresh procedure Brian Gix
2019-05-23 16:13 ` [PATCH BlueZ v3 2/6] mesh: Centralize definition of PRIMARY_NET_IDX Brian Gix
2019-05-23 16:13 ` [PATCH BlueZ v3 3/6] mesh: Implement Net Key keyring storage handling Brian Gix
2019-05-23 16:13 ` [PATCH BlueZ v3 4/6] mesh: Implement App " Brian Gix
2019-05-23 16:13 ` [PATCH BlueZ v3 5/6] mesh: Implement Key Refresh Phasing in keyring Brian Gix
2019-05-23 16:13 ` [PATCH BlueZ v3 6/6] mesh: Implement remote dev key methods for keyring Brian Gix
2019-05-24 15:07 ` [PATCH BlueZ v3 0/6] mesh: Add App and Net Key Refresh keyring back-end Gix, Brian
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=20190523161329.13017-1-brian.gix@intel.com \
--to=brian.gix@intel.com \
--cc=inga.stotland@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).