<?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>What are most common pairing steps?</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/82230/what-are-most-common-pairing-steps</link><description>Dear Nordic, 
 we are developing FW based on nRF52832, SDK 17.0.2. We have 2 devices: BLE Central with SD S332 and BLE Peripheral with SD S112. The Peripheral is basically a sensor, the Central is a controller / data analyzer. 
 Our boards work in an</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 30 Nov 2021 15:19:39 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/82230/what-are-most-common-pairing-steps" /><item><title>RE: What are most common pairing steps?</title><link>https://devzone.nordicsemi.com/thread/341358?ContentTypeID=1</link><pubDate>Tue, 30 Nov 2021 15:19:39 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:af7e7a92-d9db-4618-9223-8e91411c4f8a</guid><dc:creator>Kenneth</dc:creator><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;There are many ways this can be done, all have various pros and cons.&lt;/p&gt;
&lt;p&gt;You can for instance provide the two peers with a pre-shared OOB key that is used when initially establishing connection to perform the bonding. Without this OOB key they would not be able to perform bonding, and either side can quickly disconnect the link to allow the next peer to connect that hopefully will have the correct OOB key to perform bonding. The advantage of using OOB key, is that it will follow a standard bonding procedure, so even if you do changes to your application (e.g. firmware update) it is very unlikely this will cause issues. Of course others may still be able to connect, but since they don&amp;#39;t have the OOB key they will quickly be disconnected based on my above suggestion. The only way for anyone being able to get the OOB key would be an attacker with in-depth knowledge of your software and hardware, and that have physical access to both, so it may be a more theoretical issue than a realistic scenario, but I mention it in any case since using pre-shared keys are security weakness.&lt;/p&gt;
&lt;p&gt;I made an example here a few years ago on how to do bonding using pre-shared OOB keys:&lt;br /&gt;&lt;a href="https://devzone.nordicsemi.com/f/nordic-q-a/66209/modify-pre-shared-oob-key-for-legacy-connection/270823#270823"&gt;https://devzone.nordicsemi.com/f/nordic-q-a/66209/modify-pre-shared-oob-key-for-legacy-connection/270823#270823&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Hope it helps,&lt;br /&gt;Kenneth&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>