<?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>Peer Manager central device issue</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/58506/peer-manager-central-device-issue</link><description>Hello, 
 I am trying to implement the Peer Manager for bonding and pairing on my central device (nrf52840 Dongle) using SDK 15.3. I based my project off of the ble_app_uart_c example, which did not have peer manager capabilities, but I have added the</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 04 Mar 2020 12:32:13 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/58506/peer-manager-central-device-issue" /><item><title>RE: Peer Manager central device issue</title><link>https://devzone.nordicsemi.com/thread/238018?ContentTypeID=1</link><pubDate>Wed, 04 Mar 2020 12:32:13 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:9da51ec4-b4b6-47ed-89cc-b5afa2c0a0fd</guid><dc:creator>Simonr</dc:creator><description>&lt;p&gt;Hi&lt;/p&gt;
&lt;p&gt;So you aren&amp;#39;t able to get any useful information when debugging your application? Have you tried setting a breakpoint at the&amp;nbsp;&lt;span&gt;PM_EVT_SLAVE_SECURITY_REQ event and go step by step to see what exactly happens? Can you upload the debug log so we might have a look at what happens?&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Best regards,&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Simon&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Peer Manager central device issue</title><link>https://devzone.nordicsemi.com/thread/237885?ContentTypeID=1</link><pubDate>Tue, 03 Mar 2020 20:07:48 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b0089803-e60f-411f-9c1c-d2f721dc442d</guid><dc:creator>a93radon</dc:creator><description>&lt;p&gt;Thank you for the informative response. I have tried deleting the peers, but that does not fix the issue.&lt;/p&gt;
&lt;p&gt;To elaborate more, when I compare the behavior of&amp;nbsp;the nrf52840 dongle&amp;nbsp;vs nRF Connect on my phone, they both prompt this sequence of events in the peer manager of the advertiser:&lt;/p&gt;
&lt;p&gt;PM_EVT_CONN_SEC_PARAMS_REQ&lt;/p&gt;
&lt;p&gt;PM_EVT_CONN_SEC_START&lt;/p&gt;
&lt;p&gt;&lt;span&gt;PM_EVT_CONN_SEC_PARAMS_REQ&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;At this point, using my phone, the advertiser prompts my phone to pair, which leads to a successful connection. On the other hand, using the dongle, no pairing is initiated. The peer manager on the dongle&amp;nbsp;side receives the&amp;nbsp;PM_EVT_SLAVE_SECURITY_REQ event before it appears to crash.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;What do I need to do in the dongle code to initiate the pairing that I see on the phone?&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Peer Manager central device issue</title><link>https://devzone.nordicsemi.com/thread/237267?ContentTypeID=1</link><pubDate>Sat, 29 Feb 2020 10:07:37 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b02a4c2d-cd71-47f6-922d-d0a07a355332</guid><dc:creator>Turbo J</dc:creator><description>[quote userid="86205" url="~/f/nordic-q-a/58506/peer-manager-central-device-issue"]changes the behavior during the debugging[/quote]
&lt;p&gt;That why the NRF_LOG stuff exists.&lt;/p&gt;
&lt;p&gt;You probably ran into the &amp;quot;key deleted on one side&amp;quot; issue - the NRF examples DO NOT allow re-pairing if a key already exists for a peer. You are supposed to delete all peers on BOTH ends in order to make the NRF examples to work.&lt;/p&gt;
&lt;p&gt;Reasoning behind this is the MITM or imposter attack: An attacker just claims to have victims MAC address (can be extracted over the air unencrypted) but has no access to the actual keys.&lt;/p&gt;
&lt;p&gt;That is why the code that allows re-pairing is intentionally made more difficult to find - re-pairing could block the legit peer from establishing a secure connection.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>