From: "Gix, Brian" <brian.gix@intel.com>
To: "michal.lowas-rzechonek@silvair.com"
<michal.lowas-rzechonek@silvair.com>,
"linux-bluetooth@vger.kernel.org"
<linux-bluetooth@vger.kernel.org>
Cc: "Stotland, Inga" <inga.stotland@intel.com>
Subject: Re: mesh: Missing API for delivering provisioning public key via OOB?
Date: Thu, 6 Feb 2020 17:25:39 +0000 [thread overview]
Message-ID: <cd23abb8286bfa1bd8ac2ea5eabeeaa98dd39888.camel@intel.com> (raw)
In-Reply-To: <20200206171600.227uzfonhepltydy@kynes>
Hi Michał,
On Thu, 2020-02-06 at 18:16 +0100, Michał Lowas-Rzechonek wrote:
> Hi,
>
> I have been playing with mesh-cfgclient, and I've noticed that
> provisioning procedure gets stuck when node reports Public Key OOB
> information available' in 'Public Key Type' field of Provisioning
> Capabilities PDU.
>
> While digging into the code and API, I think we have a missing feature
> in the API between provisioner application and the daemon - while there
> is an API to deliver OOB keys to the daemon when *the application* is
> being provisioned, there doesn't seem to be a way to deliver provisioned
> device's public key when is the application who does the provisioning.
>
> Is my understanding correct, or is there something I've missed?
Yes... It looks like tools/mesh-cfgclient.c needs to implement the:
array{byte} PublicKey()
method.
This is a good catch, and needs to be added.
>
> regards
next prev parent reply other threads:[~2020-02-06 17:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-06 17:16 mesh: Missing API for delivering provisioning public key via OOB? Michał Lowas-Rzechonek
2020-02-06 17:25 ` Gix, Brian [this message]
2020-02-06 17:29 ` Gix, Brian
2020-02-06 17:53 ` michal.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=cd23abb8286bfa1bd8ac2ea5eabeeaa98dd39888.camel@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