BLE_GAP_CONN_SEC_MODE_SET_ENC_NO_MITM vs BLE_GAP_CONN_SEC_MODE_SET_SIGNED_NO_MITM

Question

there is no sample code in nrf5188 sdk to use BLE_GAP_CONN_SEC_MODE_SET_SIGNED_NO_MITM,
what's the difference between the two settings?
for BLE_GAP_CONN_SEC_MODE_SET_SIGNED_NO_MITM, is there a place to set private key?

FormerMember · Accepted Answer

Hello, 
 The main difference between BLE_GAP_CONN_SEC_MODE_SET_ENC_NO_MITM and BLE_GAP_CONN_SEC_MODE_SET_SIGNED_NO_MITM is that for ENC_NO_MITM the link is encryped and for SIGNED_NO_MITM the link is not encrypted. Instead of encrypting the link for SIGNED_NO_MITM, there is a signature in the end of the "message", to show that the "message" comes from a trusted source.
The SIGNED_NO_MITM does not have a lot of use cases and is not implemented in our stack. 
 Regards,
Kristin