NimBLE/SM: Application should be able to accept or reject pairing request
- Dominant language
- C
- Stars
- 893
- Forks
- 512
- Avg merge
- 13d 31m
- Merged PRs (30d)
- 7
Description
- Current implementation does not have any support to accept/reject pairing request, having this support will be helpful for implementing different security levels.
- As an use-case, if the device wants to only establish Authenticated Secure Connection only connection, then any unauthenticated pairing request can be rejected.
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue names NimBLE/SM pairing-request handling but no files or tests. Start by tracing the pairing request entry point and how application callbacks are exposed, then determine the API and state flow needed for an application decision. Done means applications can accept or reject requests, including rejecting unauthenticated pairing when authenticated secure connections are required.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- authentication, embedded-iot, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100