Received-SPF: pass (google.com: best guess record for domain of linux-bluetooth-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
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 v3 0/3] mesh: Fix Remote/Local dev key usage
Date:   Thu, 26 Sep 2019 11:14:41 -0700
Message-Id: <20190926181444.4916-1-brian.gix@intel.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Sender: linux-bluetooth-owner@vger.kernel.org
Precedence: bulk

V3:  By popular demand, the name "remote" is now used for both DevKeySend()
and DevKeyMessageReceived().

In DevKeySend(), setting remote == true means that the Key Ring *must* be
used to encrypt the outgoing message, and a failure will be returned if
the requested destination address does not include a device key in the
local key ring. For remote == false requests, the request will be rejected
if the destination is an element on the local node.

In DevKeyMessageReceived(), the remote boolean will be set == true if it
required the key ring to decrypot the message.  If remote == false, this
means that the local nodes Device Key successfully decrypted the message,
and the message may be used to change or query privileged states.


Brian Gix (3):
  mesh: Add local/remote bools to DevKey transactions
  mesh: Use explicit Local vs Remote Device key usage
  mesh: Fix Key Ring permissions for local nodes

 doc/mesh-api.txt | 17 ++++++++++++++---
 mesh/manager.c   |  5 -----
 mesh/model.c     | 11 +++++++----
 mesh/node.c      | 40 +++++++++++++++-------------------------
 4 files changed, 36 insertions(+), 37 deletions(-)

-- 
2.21.0