<?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>Identification of central devices</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/97363/identification-of-central-devices</link><description>Hi 
 I&amp;#39;m using an nRF5280 with Zephyr and nRF Connect SDK v2.1.0. 
 My peripheral refuses connections unless there is a bond. In order to accept bonding, it needs to be put into a specific state (i.e. a button press). 
 Today I received an additional</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 07 Mar 2023 05:38:01 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/97363/identification-of-central-devices" /><item><title>RE: Identification of central devices</title><link>https://devzone.nordicsemi.com/thread/413694?ContentTypeID=1</link><pubDate>Tue, 07 Mar 2023 05:38:01 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d936fa52-e840-4448-95ac-f1859044a2b1</guid><dc:creator>giz</dc:creator><description>&lt;p&gt;I&amp;#39;ll try my best to reject it. At least I can argue with technical reasons now, thanks!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Identification of central devices</title><link>https://devzone.nordicsemi.com/thread/413558?ContentTypeID=1</link><pubDate>Mon, 06 Mar 2023 13:32:56 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:4ae9893c-2c3b-4f8b-9ee3-0d572fcc68d5</guid><dc:creator>Turbo J</dc:creator><description>&lt;p&gt;You should probably REJECT that requirement outright - users don&amp;#39;t always know what they want.&lt;/p&gt;
&lt;p&gt;There is no way to differentiate an attacker spoofing the address of an existing central from the case where the user deleted the bonding information.&lt;/p&gt;
&lt;p&gt;Thus a proper funtioning BTLE devices has to reject all re-pair attempts unless it was put into pairing mode explicitly.&lt;/p&gt;
&lt;p&gt;TL;DR there is no way to uniquely identify the central &lt;strong&gt;without&lt;em&gt; &lt;/em&gt;&lt;/strong&gt;the bonding data.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>