This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CC2642R: Reject debug keys when using LE secure connection

Part Number: CC2642R

Hi, I have the same question (with the related post): how to reject the connection when the other party use debug key? Or how can I know the other party use the debug key or not?

Does the latest TI SDK resolve the 2 questions below, since 5 months past:

  • Is there a way I can retrieve the peer's public key in use at pairing time?
  • Is there a way I can retrieve my own device's private key in use at pairing time?

Thanks.

Ming

  • Hey Ming,

    how to reject the connection when the other party use debug key?

    I was able to prioritize this feature for the next upcoming release (should be released very soon, look for SDK v5.10). An option is now given inside GapBondMgr (GAPBOND_ALLOW_DEBUG_KEYS) to allow/disallow the use of debug keys.

    For your other two questions, I would take a look at the gapbondmgr.c file. You can access some parameters once the connection is formed retroactively but I'm unaware of any callback that is triggered to the application during pairing time. This is usually handled inside the stack and not fed to the application.

  • Hi Ammar,

    What is the difference between the parameter GAPBOND_ALLOW_DEBUG_KEYS and GAPBOND_SC_HOST_DEBUG?

    If I can control the use of the debug key, then the later 2 questions are not important.

    Thanks,

    Ming

  • Hey Ming,

    GAPBOND_SC_HOST_DEBUG allows the CC2642 to use debug keys, meaning it is the one requesting other devices to accept its debug keys. If you have this enabled, it means you are using debug keys. If it's disabled, you can still connect to a device using that is using debug keys. GAPBOND_SC_HOST_DEBUG allows you to control the use of debug keys for its own device, but has no control over rejecting/accepting an incoming connection with a peer using debug keys.

    On the receive side, say if you were a central, and did not want to accept a connection with a peer using debug keys, this is where you would set  GAPBOND_ALLOW_DEBUG_KEYS to false.

    Hope this helps clarify things.

  • Thanks Ammar