<?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>LE Secure Connections and Legacy Pairing</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/19427/le-secure-connections-and-legacy-pairing</link><description>Is it possible to support both LE Secure Connections Just Works pairing and Legacy Just Works pairing in a single device? 
 My concern at the moment is that if I require LE Secure Connections my product won&amp;#39;t be able to connect to most Android devices</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 06 Feb 2017 14:54:29 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/19427/le-secure-connections-and-legacy-pairing" /><item><title>RE: LE Secure Connections and Legacy Pairing</title><link>https://devzone.nordicsemi.com/thread/75460?ContentTypeID=1</link><pubDate>Mon, 06 Feb 2017 14:54:29 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:6f5671dc-67b3-41cf-a1b5-563dca7e954b</guid><dc:creator>Petter Myhre</dc:creator><description>&lt;p&gt;A peripheral example that supports LESC but falls back to legacy Just Works if LESC is not supported by the central device? The best way is to catch the BLE_GAP_EVT_AUTH_STATUS event, and check that auth_status.sm1_levels.lv4 is set.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: LE Secure Connections and Legacy Pairing</title><link>https://devzone.nordicsemi.com/thread/75461?ContentTypeID=1</link><pubDate>Sun, 05 Feb 2017 18:31:14 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:cc2246cb-3ec6-4d30-98fa-c84f30f7a118</guid><dc:creator>WestCoastDaz</dc:creator><description>&lt;p&gt;Petter,&lt;/p&gt;
&lt;p&gt;Thanks for the comment and the details on which section of the Bluetooth spec detail this.  Does Nordic have any examples of this?  Also what is the best way to determine if a connection is using LE Secure connections or not?&lt;/p&gt;
&lt;p&gt;Cheers,
Darren&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: LE Secure Connections and Legacy Pairing</title><link>https://devzone.nordicsemi.com/thread/75459?ContentTypeID=1</link><pubDate>Thu, 02 Feb 2017 21:33:04 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:2f18d8d3-cc88-4827-b494-e20d34d6d10d</guid><dc:creator>Petter Myhre</dc:creator><description>&lt;p&gt;It should be possible. Per spec if one of the devices doesn&amp;#39;t support LESC LE Legacy pairing should be used:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;The SC field is a 1 bit flag. If LE
Secure Connections pairing is
supported by the device, then the SC
field shall be set to 1, otherwise it
shall be set to 0. If both devices
support LE Secure Connections pairing,
then LE Secure Connections pairing
shall be used, otherwise LE Legacy
pairing shall be used.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;Taken from Vol 3, Part H, Section 3.5.1.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>