From: "michal.lowas-rzechonek@silvair.com" <michal.lowas-rzechonek@silvair.com>
To: "Gix, Brian" <brian.gix@intel.com>
Cc: "anupam.r@samsung.com" <anupam.r@samsung.com>,
"Stotland, Inga" <inga.stotland@intel.com>,
"semun.lee@samsung.com" <semun.lee@samsung.com>,
"dh79.pyun@samsung.com" <dh79.pyun@samsung.com>,
"linux-bluetooth@vger.kernel.org"
<linux-bluetooth@vger.kernel.org>
Subject: Re: Regarding OOB authentication method & action for Mesh provisioner
Date: Tue, 3 Mar 2020 09:55:26 +0100 [thread overview]
Message-ID: <20200303085526.g3iqcijh4enapxbh@mlowasrzechonek2133> (raw)
In-Reply-To: <17a69d79616ada7b4e64da8c7b3829ec594c755a.camel@intel.com>
Hi,
On 03/02, Gix, Brian wrote:
> > The daemon indeed is missing the dynamic acquisition of the
> > provisioner's agent capabilities. I think there is no need for a new
> > D- Bus method, the current API is sufficient. What is needed, is to
> > add call for GetProperty() request of "Capabilities" on the Agent
> > interface (in agent.c) prior to sending provisioning invite (in
> > prov-initiator.c, before or in prov_init_open())
>
> Yes, after talking with Inga, this is absolutely correct: I think we
> have everything in our existing API to support full control by the
> Provisioner App as to what OOB methodology gets used... But the
> functionality in the prov-initator.c to use it is currently missing.
Ack. Thanks for the explanation, we'll do it this way when we get to it.
--
Michał Lowas-Rzechonek <michal.lowas-rzechonek@silvair.com>
Silvair http://silvair.com
Jasnogórska 44, 31-358 Krakow, POLAND
next prev parent reply other threads:[~2020-03-03 8:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20200302125344epcms5p3e31d97ef6263e0513b94f6306536269b@epcms5p3>
2020-03-02 12:53 ` Regarding OOB authentication method & action for Mesh provisioner Anupam Roy
2020-03-02 14:22 ` Michał Lowas-Rzechonek
[not found] ` <CGME20200302125344epcms5p3e31d97ef6263e0513b94f6306536269b@epcms5p7>
2020-03-02 14:55 ` Anupam Roy
2020-03-02 16:56 ` Gix, Brian
2020-03-02 17:15 ` Stotland, Inga
2020-03-02 17:31 ` Gix, Brian
2020-03-03 8:55 ` michal.lowas-rzechonek [this message]
[not found] ` <CGME20200302125344epcms5p3e31d97ef6263e0513b94f6306536269b@epcms5p1>
2020-03-03 9:18 ` Anupam Roy
2020-03-03 18:26 ` Gix, Brian
[not found] ` <CGME20200302125344epcms5p3e31d97ef6263e0513b94f6306536269b@epcms5p4>
2020-03-04 14:52 ` Anupam Roy
2020-03-27 13:47 ` RE: Re: Mesh Key Refreshment procedure from Config client Anupam Roy
2020-03-30 6:04 ` Stotland, Inga
[not found] ` <CGME20200302125344epcms5p3e31d97ef6263e0513b94f6306536269b@epcms5p5>
2020-03-31 8:05 ` Anupam Roy
2020-03-27 5:35 ` Anupam Roy
[not found] <20200326144743epcms5p401053700dae86ae93749df5fc77a2807@epcms5p4>
[not found] ` <20200304153920epcms5p47e26659f715177b0244f18c71e4b5fed@epcms5p4>
[not found] ` <CGME20200302125344epcms5p3e31d97ef6263e0513b94f6306536269b@epcms5p2>
2020-03-26 14:52 ` Anupam Roy
2020-03-27 5:10 ` Stotland, Inga
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=20200303085526.g3iqcijh4enapxbh@mlowasrzechonek2133 \
--to=michal.lowas-rzechonek@silvair.com \
--cc=anupam.r@samsung.com \
--cc=brian.gix@intel.com \
--cc=dh79.pyun@samsung.com \
--cc=inga.stotland@intel.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=semun.lee@samsung.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.