<?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>Re-bonding issue with Android and S110</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/24647/re-bonding-issue-with-android-and-s110</link><description>Hello, 
 we are facing the following issue when using Android and trying to rebond with a previously bonded S110 peripheral:
Bonding the Android device with the S110 based device the first time is working fine - no problems. Next, the user of the Android</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 25 Aug 2017 14:11:32 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/24647/re-bonding-issue-with-android-and-s110" /><item><title>RE: Re-bonding issue with Android and S110</title><link>https://devzone.nordicsemi.com/thread/97020?ContentTypeID=1</link><pubDate>Fri, 25 Aug 2017 14:11:32 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:4ec71a6e-5a73-455a-a160-2a82e7209f69</guid><dc:creator>michael</dc:creator><description>&lt;p&gt;Thank you. Toggling Bluetooth on and off won&amp;#39;t help. In the meantime we tried IOS and it seems that IOS can rebond without problems.  I think I understand now why this is a security issue even when using whitelisting and it makes sense to have to delete the bond on both devices. It is a bit of a problem to delete a single specific bond if the device only has a single button and allows to bond with up to 8 smartphones. The only viable option in this case is to delete all bonds at once. But then all other  7 smartphones need to delete their bonds and rebond again, too. That is quite painfull for many users.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Re-bonding issue with Android and S110</title><link>https://devzone.nordicsemi.com/thread/97019?ContentTypeID=1</link><pubDate>Fri, 25 Aug 2017 12:53:17 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:1f2f78fc-7baf-4ed4-b18e-180af16c8a35</guid><dc:creator>run_ar</dc:creator><description>&lt;p&gt;I don&amp;#39;t know why Android tries to encrypt using the previous exchanged keys, if you have actually deleted them. Did you try to toggle bluetooth off/on on Android to see if that helps?&lt;/p&gt;
&lt;p&gt;Regardless. An existing previous bond should only be authenticated based on the Long term key, so if this is deleted on the peer it is no way for a device to know if this is indeed the bonded device reconnecting or an attacker. This is why you have to delete the bond on both peers. Note that the old sdk has a //bond/key refresh feature (which is actually a security issue), that would allow the android device to create a new bond, overwriting the existing one if it only tried to do so.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>