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;
Date:   Tue, 3 Mar 2020 09:55:26 +0100
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
Message-ID: <20200303085526.g3iqcijh4enapxbh@mlowasrzechonek2133>
Mail-Followup-To: "Gix, Brian" <brian.gix@intel.com>,
        "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>
References: <20200302142239.re57glm4ixjot7d3@mlowasrzechonek2133>
 <20200302125344epcms5p3e31d97ef6263e0513b94f6306536269b@epcms5p3>
 <CGME20200302125344epcms5p3e31d97ef6263e0513b94f6306536269b@epcms5p7>
 <20200302145518epcms5p7ec2da0403de9efa6733e12290f3cc80d@epcms5p7>
 <7686b0b5ec818946fef72d8eb438460898d53c40.camel@intel.com>
 <f2ea1cd7ff4a84671a53c518e3bdbabc286343cd.camel@intel.com>
 <17a69d79616ada7b4e64da8c7b3829ec594c755a.camel@intel.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <17a69d79616ada7b4e64da8c7b3829ec594c755a.camel@intel.com>
User-Agent: NeoMutt/20180716
Sender: linux-bluetooth-owner@vger.kernel.org
Precedence: bulk

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