-
Notifications
You must be signed in to change notification settings - Fork 37
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
Comments
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. |
True, there should be some kind of security to unlock DFU updates and configuration. |
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. |
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. |
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. |
e.g. data format, transmission interval, PHYs used, channels used.
The text was updated successfully, but these errors were encountered: