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

Prevent connecting from another phone #8

Open
WaGi-Coding opened this issue Sep 3, 2022 · 1 comment
Open

Prevent connecting from another phone #8

WaGi-Coding opened this issue Sep 3, 2022 · 1 comment

Comments

@WaGi-Coding
Copy link

Hey I wonder if you could implement something to bind the scooter to a specific phone, maybe only when it's locked. Currently i or any thief could just connect with another phone to unlock the scooters locked mode, which is pretty useless then.

Maybe, if you can save some persistent data on the BLE, give us an option to enable "phone bind" or something called like that, which saves the phones mac address and only allows connections from that mac then.

Also in case you lose your phone, you make that check only when it's locked. And if it's locked but you do not have that phone anymore, that you can still unlock by disconnecting the battery entirely & give us some button combination to delete the Phone MAC/ID (for example, holding throttle & brake + pressing the button 8 times)

Would be really great if thats possible.

@WaGi-Coding
Copy link
Author

WaGi-Coding commented Sep 3, 2022

Or what would even be better is the need for a user generated password. Like if you want to connect from another phone you still can, but the BLE would drop connection if any commands are sent thats not a custom command validating the password

A combination of both would be maybe smarter tho, that way you don't need to send the custom password command every time, just when you connect from a phone with another mac than the one which validated with the custom password command earlier

So it would be like:

  • The BLE gives you the option to setup password protection through custom commands
  • When password protection is set up, you need to validate the password on first connection
  • With that, it saves the password + the MAC of the phone which password validated successfully last time
  • If another user wants to connect and do something else than sending a command to either validate or delete the password protection (password needed for that as well - so you should never forget that for sure), the BLE will just drop the Connection
  • If the other user supplies correct password via the custom command, the saved MAC gets updated to that phones mac, so you can flawlessly re-connect with various apps

PS: Maybe a command/instruction Blacklist(unlock, flashing) is better than a whitelist(password validate, remove pw protection)
By using the custom commands for all that, i guess apps supporting CamiBLE could built up on this to make validating easier and saves the password on the phone, then the mac would not be really needed anymore, just the password.

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

No branches or pull requests

1 participant