You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We're leaning towards having device IDs be generated from the device's MAC address, meaning a physical device will always have the same ID. The server can coordinate the linking of IDs to users.
The UUID library we're using can be seeded so that its generation isn't truly random. At that point, we may not need to bother with storing the UUID in "EEPROM" either.
Maybe the UUID format is not even necessary? Is it bad to expose our MAC addresses? Might want some input from cybersecurity people on this...
The text was updated successfully, but these errors were encountered:
We could generate our own IDs and permanently store them in eFuse memory. Would just need a tool/script to generate new IDs and make sure they are always unique.
I've made the device ID a UUID generated from the device's MAC address which should be okay to start with. Still need to confirm if we should burn custom IDs instead.
We're leaning towards having device IDs be generated from the device's MAC address, meaning a physical device will always have the same ID. The server can coordinate the linking of IDs to users.
The UUID library we're using can be seeded so that its generation isn't truly random. At that point, we may not need to bother with storing the UUID in "EEPROM" either.
Maybe the UUID format is not even necessary? Is it bad to expose our MAC addresses? Might want some input from cybersecurity people on this...
The text was updated successfully, but these errors were encountered: