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

Feature: Radio configuration over GATT #89

Open
ojousima opened this issue Jul 10, 2020 · 5 comments
Open

Feature: Radio configuration over GATT #89

ojousima opened this issue Jul 10, 2020 · 5 comments
Labels
enhancement New feature or request

Comments

@ojousima
Copy link
Member

e.g. data format, transmission interval, PHYs used, channels used.

@ojousima ojousima added the enhancement New feature or request label Jul 10, 2020
@ojousima ojousima added this to the 3.32.0 milestone Jul 10, 2020
@DG12
Copy link
Contributor

DG12 commented Jul 10, 2020

It seems to me that NFC would be less susceptible to vandalism due to the required proximity and keeping the communications away from BLE would also simplify implementation on both the ruuvi tag and the application to do the setting.

@ojousima
Copy link
Member Author

True, there should be some kind of security to unlock DFU updates and configuration.

@DG12
Copy link
Contributor

DG12 commented Jul 10, 2020

If you're near enough to do NFC then you are near enough to grab the tag and do whatever you want. Simple security, if any, to avoid accidentally alterations seems all that is necessary.

@theBASTI0N
Copy link

You should be able to add passkey to tag just like eddystone tags can be configured with. That would prevent users from changing settings and flashing the device if passkey is not knwon.

@ojousima
Copy link
Member Author

ojousima commented Mar 3, 2021

Currently NFC scan is required to enable BLE bootloader, I have been thinking about using the unique ID of tag as a passkey. The ID will be exposed to anyone with NFC reader, but I think it would be secure enough as attackers need physical access to tag to configure it.

@ojousima ojousima removed this from the 3.32.0 milestone Mar 19, 2021
@niksiboxi niksiboxi self-assigned this Apr 12, 2021
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

4 participants