<?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>How to set up nrf52833 Security 2 Level 2?</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/88775/how-to-set-up-nrf52833-security-2-level-2</link><description>Hi, 
 I looked at some of the questions on the forum and they didn&amp;#39;t give me good advice. Currently all I can do is nrf52832 Security 1 Level 4 and nrf52833 Security 1 Level 3. But according to my bluetooth protocol requirement is Security 2 Level 2 of</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 23 Jun 2022 07:02:51 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/88775/how-to-set-up-nrf52833-security-2-level-2" /><item><title>RE: How to set up nrf52833 Security 2 Level 2?</title><link>https://devzone.nordicsemi.com/thread/373825?ContentTypeID=1</link><pubDate>Thu, 23 Jun 2022 07:02:51 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a7ed3550-66ae-43d9-89a9-244d0ef14957</guid><dc:creator>Emil Lenngren</dc:creator><description>&lt;p&gt;The difference between level 3 and 4 is the use of &amp;quot;LE Secure Connections&amp;quot;. If you already know that both devices (central and peripheral) support LESC, then do require the use of LESC during pairing, since the legacy methods are all considered unsecure. If you only intend to communicate with Android, iOS and other &amp;quot;big&amp;quot; operating systems, there is no need to support the legacy methods since these systems have support for LESC since a long time ago.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How to set up nrf52833 Security 2 Level 2?</title><link>https://devzone.nordicsemi.com/thread/373799?ContentTypeID=1</link><pubDate>Thu, 23 Jun 2022 00:57:42 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ee7d2b73-c875-4433-bbe0-bf407df0ea80</guid><dc:creator>Mikey</dc:creator><description>&lt;p&gt;Should I choose level3 or level4 in security mode 1?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How to set up nrf52833 Security 2 Level 2?</title><link>https://devzone.nordicsemi.com/thread/371779?ContentTypeID=1</link><pubDate>Fri, 10 Jun 2022 07:07:48 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:767b2da4-f2c1-4814-8a26-80cab9ab67e0</guid><dc:creator>Simonr</dc:creator><description>&lt;p&gt;That is correct. And as Emil suggests, security mode 1 is generally a better security implementation all around.&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How to set up nrf52833 Security 2 Level 2?</title><link>https://devzone.nordicsemi.com/thread/371771?ContentTypeID=1</link><pubDate>Fri, 10 Jun 2022 06:30:39 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:64ca6843-4d7e-40e6-948e-27d578128cd7</guid><dc:creator>Emil Lenngren</dc:creator><description>&lt;p&gt;Can you use security mode 1 instead? It&amp;#39;s a much better mode in almost all aspects. Bluetooth SIG recommends to use mode 1 instead of 2.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How to set up nrf52833 Security 2 Level 2?</title><link>https://devzone.nordicsemi.com/thread/371632?ContentTypeID=1</link><pubDate>Thu, 09 Jun 2022 11:21:08 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d7645638-88a1-4b68-9d99-f2c7107b99ce</guid><dc:creator>Mikey</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;That is to say, if I want to use these digital signature functions, I have to change another SDK and change another zephyr os to support these functions.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How to set up nrf52833 Security 2 Level 2?</title><link>https://devzone.nordicsemi.com/thread/371620?ContentTypeID=1</link><pubDate>Thu, 09 Jun 2022 11:05:13 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:7c783c3c-ef44-48b3-8c85-e37bec8a8b92</guid><dc:creator>Simonr</dc:creator><description>&lt;p&gt;Hi&lt;/p&gt;
&lt;p&gt;Security mode 2 (or more specifically data signing) is not supported in any of the SoftDevices in the nRF5 SDK. From what I have heard, data signing is in general not very widely used as most phones on the market doesn&amp;#39;t support this feature either.&lt;/p&gt;
&lt;p&gt;The alternative will be to use the nRF Connect SDK where data signing is supported and should work. The GAP security features in Zephyr are described &lt;a href="https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/zephyr/connectivity/bluetooth/gap-pics.html"&gt;here&lt;/a&gt;, and &lt;a href="https://docs.zephyrproject.org/1.14.1/reference/kconfig/CONFIG_BT_SIGNING.html"&gt;data signing here&lt;/a&gt; in the Zephyr project.&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Simon&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How to set up nrf52833 Security 2 Level 2?</title><link>https://devzone.nordicsemi.com/thread/371530?ContentTypeID=1</link><pubDate>Thu, 09 Jun 2022 03:27:42 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:421e5316-4a88-4966-bdef-dd6e4eea3edb</guid><dc:creator>Mikey</dc:creator><description>&lt;p&gt;This is currently set by nrf52833, and the phone needs to enter the key.&lt;pre class="ui-code" data-mode="c_cpp"&gt;#define  SEC_PARAM_BOND  1															/**&amp;lt; Perform bonding. */
#define  SEC_PARAM_MITM  1															/**&amp;lt; Man In The Middle protection required. */
#define  SEC_PARAM_LESC  0															/**&amp;lt; LE Secure Connections not enabled. */
#define  SEC_PARAM_KEYPRESS  0														/**&amp;lt; Keypress notifications not enabled. */
#define  SEC_PARAM_IO_CAPABILITIES   BLE_GAP_IO_CAPS_DISPLAY_ONLY					/**&amp;lt; No I/O capabilities. */
#define  SEC_PARAM_OOB  0															/**&amp;lt; Out Of Band data not available. */
#define  SEC_PARAM_MIN_KEY_SIZE  7													/**&amp;lt; Minimum encryption key size. */
#define  SEC_PARAM_MAX_KEY_SIZE  16													/**&amp;lt; Maximum encryption key size. */&lt;/pre&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>