From: Brian Gix <brian.gix@intel.com>
To: linux-bluetooth@vger.kernel.org
Cc: brian.gix@intel.com, inga.stotland@intel.com,
michal.lowas-rzechonek@silvair.com
Subject: [PATCH BlueZ 0/1] mesh: Require Dev Key authentication
Date: Sun, 15 Sep 2019 01:14:07 -0700 [thread overview]
Message-ID: <20190915081408.18116-1-brian.gix@intel.com> (raw)
Per Mesh Working group discussions, we decided that calls that require
device keys require explicit knowledge of the key being used. This
includes looped-back calls to the local Config Server, meaning that
nodes wanting to change their own states, must be granted that
permission by possession of their own key, entered into the local key
database.
We will be removing automatic device key entry nto the key database
from all methods except the Create() method.
Brian Gix (1):
mesh: Add local/remote bools to DevKey transactions
doc/mesh-api.txt | 13 +++++++++++--
1 file changed, 11 insertions(+), 2 deletions(-)
--
2.21.0
next reply other threads:[~2019-09-15 8:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-15 8:14 Brian Gix [this message]
2019-09-15 8:14 ` [PATCH BlueZ 1/1] mesh: Add local/remote bools to DevKey transactions Brian Gix
2019-09-16 9:58 ` Michał Lowas-Rzechonek
2019-09-16 10:55 ` Gix, Brian
2019-09-16 11:08 ` Michał Lowas-Rzechonek
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=20190915081408.18116-1-brian.gix@intel.com \
--to=brian.gix@intel.com \
--cc=inga.stotland@intel.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=michal.lowas-rzechonek@silvair.com \
/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).