Skip to contentSkip to conversation

mesh: Missing API for delivering provisioning public key via OOB?

DISCUSSION Michał Lowas-Rzechonek 2 participants 4 messages Feb 6, 2020 Bluetooth drivers

lore
Share & tools
lore
#0 lore raw

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?

regards

Signature · 3 lines
Michał Lowas-Rzechonek <[email protected]>
Silvair http://silvair.com
Jasnogórska 44, 31-358 Krakow, POLAND
#1 lore raw

Hi Michał,

Quoted 7 lines · Michał Lowas-Rzechonek

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.

Quoted 7 lines

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.

Quoted 2 lines

regards

#2 lore raw
Quoted 18 lines · Brian

Hi Michał,

Quoted 7 lines · Michał Lowas-Rzechonek

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.

Quoted 7 lines

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?

Quoted 7 lines

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.

And before you respond, yes it also needs to be added to mesh/agent.c

Quoted 3 lines
Quoted 3 lines

regards

#3 lore raw
In reply to Gix, Brian

Brian,

Quoted 8 lines · Brian
Quoted 1 line

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.

Ok, thanks. I'll give it a shot, if time permits.

What puzzled me is that the provisioning gets stuck instead of failing, so it seems it's not only that cfgclient doesn't implement the method, but also the daemon doesn't seem to check for errors?

Signature · 3 lines
Michał Lowas-Rzechonek <[email protected]>
Silvair http://silvair.com
Jasnogórska 44, 31-358 Krakow, POLAND