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:     inga.stotland@intel.com, brian.gix@intel.com,
        michal.lowas-rzechonek@silvair.com
Subject: [PATCH BlueZ 0/3] mesh: Propagate/Preserve Net Index for Access Layer
Date:   Tue, 16 Jul 2019 15:56:41 -0700
Message-Id: <20190716225644.11449-1-brian.gix@intel.com>
Sender: linux-bluetooth-owner@vger.kernel.org
Precedence: bulk

Two major flaws are corrected by this patch-set:

1. The Spec defined Access Layer AID was being confused with the internally used
key_id which is used to identify Network keys for multiple networks,
sub-networks, and friendships. This confused ID was then being used instead
of the correct Network Key ID for outgoing messages.

2. The specification requires *responses* to all standard Server messages to
be sent with the same credentials as the received command that triggered them.
This requires more complete propagation of the Net Index value on received
messages, so that the same Network key is used in the reverse direction.

This additionally now uses the requested Net Index when sending Device Key
secured messages through the D-Bus interface.

Brian Gix (3):
  mesh: Add bound Net Index lookup for App Keys
  mesh: Normalize Access Key AID naming convention
  mesh: Propagate Net Index up Rx message chain

 mesh/appkey.c        |  59 +++++++++++++-------
 mesh/appkey.h        |   1 +
 mesh/cfgmod-server.c | 154 ++++++++++++++++++++++++++++-----------------------
 mesh/crypto.c        |  37 ++++++-------
 mesh/crypto.h        |   8 +--
 mesh/model.c         | 129 +++++++++++++++++++++---------------------
 mesh/model.h         |  10 ++--
 mesh/net.c           |  92 +++++++++++++++++-------------
 mesh/net.h           |  10 ++--
 mesh/node.c          |  10 ++--
 10 files changed, 276 insertions(+), 234 deletions(-)

-- 
2.14.5