• State Verified Answer
  • Locked Locked
  • Replies 18 replies
  • Subscribers 88 subscribers
  • Views 4468 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 288346
Options
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Question about "Mapping of IO capabilities to key generation method"

kai19960504

Hi All,

I would like to know how Nordic's pairing mode corresponds to the bluetooth specification.

If my smartphone(initiator) is keyboard display,and my slave(responder) is display only.

The comparison to the table is to use the passkey entry.

So which one should I choose for the settings in the program?

Best regards,

Kai

  • 0 in reply to Einar Thorsrud

    Hi Einar,

    Einar Thorsrud said:
    If the level you got from pairing/bonding is the same or higher as you have specified for a given characteristic, then you can read/write it. If it is lower, then you cannot.

    "the level you got from pairing/bonding" - Do you mean this part of the picture?

    or here?

  • 0 in reply to kai19960504
    kai19960504 said:
    "the level you got from pairing/bonding" - Do you mean this part of the picture?

    No, that is where you set the security requirement for a specific characteristic. Here you set it to open so that it can be accessed even with an unencrypted link (no pairing needed for that specific characteristic to be used).

    kai19960504 said:
    or here?

    These defines are used further down in the examples main.c and  is input to the peer manager, and configures if it should support bonding etc. Here you also set IO capabilities to none, so just works (or no pairing at all) is the only posibility.

  • 0 in reply to Einar Thorsrud

    Hi Einar,

    Einar Thorsrud said:
    If the level you got from pairing/bonding is the same or higher as you have specified for a given characteristic, then you can read/write it. If it is lower, then you cannot.

    Could you please elaborate a little more on what this means?

  • 0 in reply to kai19960504

    Hi Kai,

    It goes back to what I have attempted to describe:

    1. The security level of the link depends on the IO-capabilities of the peers (and if LESC is supported). The highest possible given the combined support is used.
    2. Each characteristic can requier separate specific security levels (from 1.) for each characteristic (and even separate for reading and writing).

    Tese two concepts are closely related. You need to understand the concepts in order to work with this, and it is basically as I have deescribed. If you need more understanding of this you can read up on Bluetooth security in general as this is a generic concept ant not specific to Nordic.

  • 0 in reply to Einar Thorsrud

    Hi Einar,

    So you mean that the security level set by the characteristic is preferably higher than the IO capability,right?

Related