<?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>ble authentication and pairing</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/84180/ble-authentication-and-pairing</link><description>Hi, 
 I have looked around the internet and am trying to understand the ble security options. I cannot understand the correct approach to take for our application. 
 Our situation is that we have a peripheral which is only allowed to connect a specific</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 01 Feb 2022 12:02:02 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/84180/ble-authentication-and-pairing" /><item><title>RE: ble authentication and pairing</title><link>https://devzone.nordicsemi.com/thread/350651?ContentTypeID=1</link><pubDate>Tue, 01 Feb 2022 12:02:02 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:69d72007-d585-4423-9c5a-7f25860e8eee</guid><dc:creator>Martijn Jonkers</dc:creator><description>&lt;p&gt;It can still occur multiple devices are used to connect to the peripheral, but only used by users&amp;nbsp;allowed to connect to that device. That is why we thought about a login to a remote server from the windows machine where we can download the pairing information for that specific device. That way only authorised users are able to connect.&lt;/p&gt;
&lt;p&gt;We are currently on the track of using an open BLE connection and implement the authentication and encryption on the application level.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: ble authentication and pairing</title><link>https://devzone.nordicsemi.com/thread/350648?ContentTypeID=1</link><pubDate>Tue, 01 Feb 2022 11:53:00 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:70756882-c610-4b35-8688-a8e667f90726</guid><dc:creator>Martijn Jonkers</dc:creator><description>&lt;p&gt;nice idea. But a requirement is that we can use the bluetooth features of windows, so no additional hardware is needed.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: ble authentication and pairing</title><link>https://devzone.nordicsemi.com/thread/350643?ContentTypeID=1</link><pubDate>Tue, 01 Feb 2022 11:38:24 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:97d4cec9-d2d2-4f90-9242-c05139c82568</guid><dc:creator>mrono</dc:creator><description>&lt;p&gt;Is it a requirement that the peripheral is tied to a specific client from the very beginning? If it were acceptable that the device bonds to the first client it encounters, then you could use regular bonding over BLE. You could add an application level authentication method to make sure the initial bond is made to your application and not some phone app or such.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: ble authentication and pairing</title><link>https://devzone.nordicsemi.com/thread/350626?ContentTypeID=1</link><pubDate>Tue, 01 Feb 2022 10:57:45 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:479eaf56-18e3-4e16-a8d5-9ef492bcb253</guid><dc:creator>Sigurd</dc:creator><description>&lt;p&gt;Link to your other post:&amp;nbsp;&lt;a href="https://devzone.nordicsemi.com/f/nordic-q-a/84233/oob-pairing-other-than-nfc"&gt;https://devzone.nordicsemi.com/f/nordic-q-a/84233/oob-pairing-other-than-nfc&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Another option could be some sort of USB dongle that&amp;nbsp;have that&amp;nbsp;bonding information stored / linked to the&amp;nbsp;peripheral, and the peripheral have the central/dongle information stored.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: ble authentication and pairing</title><link>https://devzone.nordicsemi.com/thread/350228?ContentTypeID=1</link><pubDate>Fri, 28 Jan 2022 13:59:38 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:1b2362a6-0727-4155-b3a8-03f867d6e81d</guid><dc:creator>Martijn Jonkers</dc:creator><description>&lt;p&gt;thank you. But I do not see how this answers my question.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: ble authentication and pairing</title><link>https://devzone.nordicsemi.com/thread/350227?ContentTypeID=1</link><pubDate>Fri, 28 Jan 2022 13:57:48 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:eab87540-418f-4c8d-abbf-c0d0a928bc05</guid><dc:creator>sipan112</dc:creator><description>&lt;p class="p"&gt;hello&lt;/p&gt;
&lt;p class="p"&gt;When the pairing procedure has been completed, the following changes are displayed:&lt;/p&gt;
&lt;ul class="ul" id="nRF_Connect_Pairing_devices__ul_rys_y3s_lw"&gt;
&lt;li class="li"&gt;A log entry shows the new security level of the connection.&lt;/li&gt;
&lt;li class="li"&gt;The connection info padlock changes to locked if the connection is encrypted.&lt;/li&gt;
&lt;li class="li"&gt;The event view text turns green to indicate success.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;and may this link will be helpful:&amp;nbsp;&lt;a href="https://infocenter.nordicsemi.com/index.jsp?topic=%2Fug_nrfconnect_ble%2FUG%2FnRF_Connect_BLE%2FnRF_Connect_intro.html"&gt;Nordic Semiconductor Infocenter&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>