<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://devzone.nordicsemi.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>#BluetoothMesh OOB authentication</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/29158/bluetoothmesh-oob-authentication</link><description>I hope Nordic Semiconductor is working on #BluetoothMesh provisioner &amp;amp; configuration App like Silicon Labs already has. 
 But could anybody inform me, how you are going to implement OOB authentication which happens during provisioning process ? 
 Currently</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 22 Jan 2018 14:57:13 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/29158/bluetoothmesh-oob-authentication" /><item><title>RE: #BluetoothMesh OOB authentication</title><link>https://devzone.nordicsemi.com/thread/115884?ContentTypeID=1</link><pubDate>Mon, 22 Jan 2018 14:57:13 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:209312c1-16b5-40b6-878b-ab088fbaf5fd</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;Yes, I don&amp;#39;t see any problem with that. Currently our static data is hardcoded as STATIC_AUTH_DATA.&lt;/p&gt;
&lt;p&gt;You can use your algorithm to generate your own static authentication data. Make sure you match them on both the provisionee and provisioner.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: #BluetoothMesh OOB authentication</title><link>https://devzone.nordicsemi.com/thread/115883?ContentTypeID=1</link><pubDate>Fri, 19 Jan 2018 19:22:20 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:74f5ec27-9ff3-49b2-911b-2852d270bdfd</guid><dc:creator>vikrant8051</dc:creator><description>&lt;p&gt;I don&amp;#39;t want to use OOB channel for authentication like NFC, display etc. etc.
Can I generate 16 bytes of Static-OOB using DEVICE (nRF52) MAC address using some algorithm ?
The same algorithm will work on Provisioner to generate 16-byte static-OOB to authenticate DEVICE (here I&amp;#39;m assuming provisioner has fetched MAC address from DEVICE advertisement)&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: #BluetoothMesh OOB authentication</title><link>https://devzone.nordicsemi.com/thread/115882?ContentTypeID=1</link><pubDate>Fri, 22 Dec 2017 15:54:09 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:5866badb-5493-4e5c-b457-6da76c7d7bab</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;Hi Vikrant,&lt;/p&gt;
&lt;p&gt;Static authentication (including OOB static authentication) is already used in our example. Currently we used a fix data (look for STATIC_AUTH_DATA). But you can use NFC, QR code or anything to update this value (on both provisioner and provisionee). It should be pretty straight forward to implement. Have a look at the config_params in main() in our light switch example.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: #BluetoothMesh OOB authentication</title><link>https://devzone.nordicsemi.com/thread/115881?ContentTypeID=1</link><pubDate>Fri, 22 Dec 2017 14:21:28 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:1bce8ecd-08f8-4a75-96f1-51a3a9dfc102</guid><dc:creator>vikrant8051</dc:creator><description>&lt;p&gt;I&amp;#39;ve already send inquiry email regarding release date for Provisioner App &amp;amp;
PB-GATT firmware support in Mesh SDK to Mr. Wendell Boyd. He will reply after 2 Jan since he is on Holiday.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: #BluetoothMesh OOB authentication</title><link>https://devzone.nordicsemi.com/thread/115880?ContentTypeID=1</link><pubDate>Fri, 22 Dec 2017 12:24:48 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b7773e58-26fc-4c3e-9268-7ec962f68127</guid><dc:creator>David Edwin</dc:creator><description>&lt;p&gt;(yes, I see that, apologies). We will release a provisioner for the mobile apps based on our roadmap. Typically roadmap questions and specific dates can be taken up with the sales manager for your region. If you need the contact for your region send me a private message with your location and I can send you the contact details.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: #BluetoothMesh OOB authentication</title><link>https://devzone.nordicsemi.com/thread/115879?ContentTypeID=1</link><pubDate>Fri, 22 Dec 2017 12:16:49 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:0d8f88f9-99a6-4045-92c5-1195447f1eec</guid><dc:creator>vikrant8051</dc:creator><description>&lt;p&gt;I&amp;#39;ve raised this Question assuming Nordic Semiconductor is going to launch #BluetoothMesh Provisioner App . OOB authentication is related to it. Then tell me what is logic behind asking this Question on Zephyr forum ??????&lt;/p&gt;
&lt;p&gt;I mentioned about Zephyr just for reference purpose.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: #BluetoothMesh OOB authentication</title><link>https://devzone.nordicsemi.com/thread/115878?ContentTypeID=1</link><pubDate>Fri, 22 Dec 2017 11:50:50 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:9b8465a3-6667-4c11-ab61-2b5f23ac28b4</guid><dc:creator>David Edwin</dc:creator><description>&lt;p&gt;Please post on the ZephyrOS forums or use their IRC channels for answers.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>