Meshtastic’s low privicy design is just dissappointing! I wish persistant identifiers were way less relied apon as they are given out freely in order for the system to work. Verry much NOT designed for urban areas or being in the presence of adversaries.
There should be “discovery” metadata, encrypted “known” and encrypted “well known” metadata, each with a diffrent encryption key that is given out in stages over a few round trips and maybe some user TOFU prompts and/or auto promotion on a timer. Brand new radios will gain trust with other radios.
“Known” gives an identifier and public key based on the context, maybe per gps area or per individual device.
“well known” being enough to preform persistant non contextual identification for the lifetime of the device.
Actions like karking a device as a “favorite” may also push it into the “well known” catagory.
Meshtastic’s low privicy design is just dissappointing! I wish persistant identifiers were way less relied apon as they are given out freely in order for the system to work. Verry much NOT designed for urban areas or being in the presence of adversaries.
There should be “discovery” metadata, encrypted “known” and encrypted “well known” metadata, each with a diffrent encryption key that is given out in stages over a few round trips and maybe some user TOFU prompts and/or auto promotion on a timer. Brand new radios will gain trust with other radios.
“Known” gives an identifier and public key based on the context, maybe per gps area or per individual device.
“well known” being enough to preform persistant non contextual identification for the lifetime of the device.
Actions like karking a device as a “favorite” may also push it into the “well known” catagory.