From: "Michał Lowas-Rzechonek" <michal.lowas-rzechonek@silvair.com>
To: Anupam Roy <anupam.r@samsung.com>
Cc: "linux-bluetooth@vger.kernel.org"
<linux-bluetooth@vger.kernel.org>,
Semun Lee <semun.lee@samsung.com>,
Dohyun Pyun <dh79.pyun@samsung.com>,
Nitin Jhanwar <nitin.j@samsung.com>
Subject: Re: Regarding OOB authentication method & action for Mesh provisioner
Date: Mon, 2 Mar 2020 15:22:39 +0100 [thread overview]
Message-ID: <20200302142239.re57glm4ixjot7d3@mlowasrzechonek2133> (raw)
In-Reply-To: <20200302125344epcms5p3e31d97ef6263e0513b94f6306536269b@epcms5p3>
Hi,
On 03/02, Anupam Roy wrote:
> Also, I would like to know, whether there is any plan to Request
> external provisioning Agent to choose Provisioning method & specific
> action? The reason being, some *application* may be interested in a
> particular Security level & Authentication action, depending on its
> own I/O capabilities.
For the record, we also need this is functionality. One of the possible
scenarios is having a provisioner who doesn't have a reliable Internet
connection and might want to fall back to (less secure) OOB actions if
it cannot obtain OOB public key.
We've been planning to send a patch implementing a D-Bus API for that,
but it's not ready yet :(
regards
--
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-02 14:22 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 [this message]
[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
[not found] ` <CGME20200302125344epcms5p3e31d97ef6263e0513b94f6306536269b@epcms5p1>
2020-03-03 9:18 ` Re: " 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=20200302142239.re57glm4ixjot7d3@mlowasrzechonek2133 \
--to=michal.lowas-rzechonek@silvair.com \
--cc=anupam.r@samsung.com \
--cc=dh79.pyun@samsung.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=nitin.j@samsung.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).