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:   =?UTF-8?q?Micha=C5=82=20Lowas-Rzechonek?= 
        <michal.lowas-rzechonek@silvair.com>
To:     linux-bluetooth@vger.kernel.org
Subject: [PATCH BlueZ 0/6] Honor provisioner's capabilities during authentication
Date:   Wed,  1 Apr 2020 12:24:56 +0200
Message-Id: <20200401102502.746-1-michal.lowas-rzechonek@silvair.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Sender: linux-bluetooth-owner@vger.kernel.org
Precedence: bulk

This patch adds ability for the provisioner application to declare a set
of supported authentication methods via ProvisionAgent1 API. The daemon
will then select the most secure method available on both ends.

This fixes an issue where nodes declaring OOB public key availability
could not be provisioned by applications lacking means to obtain such
keys.

v2:
 - fixed memory leak when displaying OOB data in cfgclient
 - fixed action bitmask endianness between mesh_agent_prov_caps and
   mesh_net_prov_caps

Michał Lowas-Rzechonek (6):
  tools/mesh-cfgclient: Display unprovisioned OOB data
  mesh: Remove unused 'server' argument
  mesh: Clean up naming of provisioning callbacks
  mesh: Refresh provisioner's capabilities
  mesh: Honor provisioner's capabilities
  doc/mesh-api: OOB Information field is 16 bit, not 32

 doc/mesh-api.txt       |   2 +-
 mesh/agent.c           | 105 ++++++++++++++++++++++++-----
 mesh/agent.h           |   2 +
 mesh/manager.c         |  33 ++++++---
 mesh/prov-initiator.c  | 148 +++++++++++++++++++++++++++--------------
 mesh/provision.h       |   6 +-
 tools/mesh-cfgclient.c |  20 ++++++
 7 files changed, 236 insertions(+), 80 deletions(-)

-- 
2.20.1