Hi All,
SDK => v17.1.0
IDE => Segger
I'm using ble_app_gls and I want to remove LESC.
According to my project => 
I have define a macro,the name is LESC, it used to switch whether to use the LESC function.
My pairing parameter settings are shown in the figure :
Why pm_sec_params_set(&sec_param) return invalid?
Best regards,
Kai
Hi Vidar,
I just disabled MITM and the device can connect.
But when I access characteristic the device automatically disconnects.
Hi Vidar,
First, let me reply this message.
You have to make a few more changes as the example is set up to require MITM protection by default. It should work if you comment these sections:
It can work now.
Second,I want to tell you about the project I am testing.
I am testing this pairing table :
And set the security level to the characteristic :
Based on the combination of pairing table and security level, I have listed one of the test items:
What is the result of my purpose for these combinations to actually run.
I am confused about the choice of security level and the setting of pairing parameters.
Hi Kai,
The SEC_PARAM_* symbols define the security capabilities of your device. E.g. if LESC and MITM pairing is supported. But it will not prevent a central from initiating pairing with lower security. For instance, legacy just works.
The security requirements is controlled by the security level configured for your characteristics in service_init():
So you will still be able to pair without MITM even if the SEC_PARAM_MITM bit is set, but then you will only be able to access characteristics that has the security level set to "SEC_OPEN" or "SEC_JUST_WORKS".
Hi Vidar,
I'm doing these combinations for explore the problem of data encryption.
I don't know if the data encryption is because SEC_PARAM_MITM is set or SEC_MITM is set.
Among them, the security level selection just works will also have encryption.
The following shows the results I actually tested through the example code and Sniffer.
