Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement a mechanism to recover channel map update by sniffing #24

Open
virtualabs opened this issue Sep 13, 2018 · 1 comment
Open
Assignees
Labels
enhancement New feature or request

Comments

@virtualabs
Copy link
Owner

Channel map update recovery based on channel mapping can take some time, and sometimes this process fails and give the user no other way to synchronize btlejack with an existing connection.

Implementing a dedicated channel map update sniffer, iterating over all the possible channels, would help capturing this type of packet if it is sent frequently by a master device.

@virtualabs virtualabs added the enhancement New feature or request label Sep 13, 2018
@virtualabs virtualabs self-assigned this Sep 13, 2018
@Matheus-Garbelini
Copy link

Matheus-Garbelini commented May 21, 2019

@virtualabs I was wondering then, how legitimate devices can keep the connection with the master? Is the slave device listening for channel map updates from the master? If so, why the sniffer can't keep a normal connection? Is this because the sniffer is not decrypting packets such as LL_CONNECTION_UPDATE_REQ ?

Do you know if encryption/decryption features is a hardware feature or software libraries that could be extracted from nordic SDKs?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants