Master emulator pairing, passkey and bonding issue

RE: Master emulator pairing, passkey and bonding issue

Jørgen Holmefjord — Mon, 19 Nov 2018 10:27:49 GMT

Some more details and clarifications from the developers:

It is always the Central that has to initiate pairing, i.e, call Bond() in master emulator. The Central can either initiate pairing on own initiative, or wait for Peripheral to send a Security Request. Either way Bond() must be called. SecurityParameters that is sent in SequrityRequestEvent is information about the Peripheral's parameters. The Central's parameters must be set in the Bond()-call. If no parameters are set in then Bond()-call, default SecurityParameters will be used.

RE: Master emulator pairing, passkey and bonding issue

Ben — Tue, 13 Nov 2018 07:37:31 GMT

I've set iocapability to keyboardonly or keyboarddisplay.

When I want to get DIS, it still displays ATT error insufficient authentication.

I think it should be got event to notify me to enter passkey.

May I ask whether is it having this event?

Thank you.

RE: Master emulator pairing, passkey and bonding issue

Jørgen Holmefjord — Sun, 11 Nov 2018 18:49:34 GMT

It is correct that you should set the passkey in the OnPasskeyRequest event, when it is being requested. I see you have set iocapabilities to displayonly. This should be set to keyboardonly or keyboarddisplay in order to get a passkey request.

RE: Master emulator pairing, passkey and bonding issue

Ben — Fri, 09 Nov 2018 03:59:41 GMT

I try to create below function.

        void OnSecurityRequest(object sender, SecurityRequestEventArgs arguments)
        {
            SecurityRequestEventArgs securityRequestEventArgs = new SecurityRequestEventArgs(true, true);
            securityParameters.IoCapabilities = IoCapabilitiesEnum.DisplayOnly;
            securityParameters.MaximumEncryptionKeySize = 16;
            securityParameters.OobAvailability = OobAvailibilityEnum.OobNotAvailable;

        }

        void OnPasskeyRequest(object sender, PasskeyRequestEventArgs eventArgs)
        {
            
            passkeyRequestEventArgs.Passkey = 123456;
        }

And, these functions add in RegisterEventHandlers()

But, I can't check whether the setup is working?

Or, are these setting wrong?

Thank you.

RE: Master emulator pairing, passkey and bonding issue

Jørgen Holmefjord — Mon, 05 Nov 2018 15:20:03 GMT

You should be able to set the IoCapabilities in SecurityParameters Class and pass this as argument to MasterEmulator.Bond Method.

RE: Master emulator pairing, passkey and bonding issue

Ben — Tue, 30 Oct 2018 09:01:39 GMT

Hi,

For Q1:

I'm writing central GUI application by using MCP firmware "MEFW_nRF51822_0.10.0_firmware_1M.hex".

I'm basing on nRF UART of master emulator.

I read blog on SIG. It mentions that SMP should define I/O capability and SC on pairing feature exchange for entering to entry passkey of LE legacy pairing. I found Enumeration name "IoCapabilitiesEnum" on API document, but I couldn't find to associated IoCapabilitiesEnum with method (like PipeStore associate with SetupAddService). And, I also can not find the SC function on API document.

In peripheral device notify central (BLE_GAP_EVT_AUTH_KEY_REQUEST) to enter passkey situations, do I follow the API document to create PasskeyRequestEventArgs? And, when I enter passkey on GUI, the API document depicts set a property "public in Passkey { set;}". Doesn't it require to use any API functions to transmit value to central device?

For Q2:

This blog is really to let me know it better. Thank you for your information and reply.

RE: Master emulator pairing, passkey and bonding issue

Jørgen Holmefjord — Mon, 29 Oct 2018 13:20:58 GMT

Hi,

Q1: Are you writing a Peripheral or Central application? Which example are you basing your application on? The passkey is normally generated and displayed on the Peripheral side (display, terminal, etc.) and then entered on the Central. Please have a look at the Message Sequence Charts in softdevice documentation:

Q2: I would recommend that you read the 4 blog posts on Bluetooth SIG that described Pairing.