[Feature Request]: Discussion on path encryption #9318
Minfrog314
started this conversation in
Ideas
Replies: 1 comment
-
@Minfrog314, Welcome to Meshtastic! 👋Thanks for opening your first issue. If it's helpful, an easy way If you have ideas for features, note that we often debate big ideas We're very active on discord, Welcome to the community! ❤️ |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Platform
Cross-Platform
Description
Hello, I'm pretty new here so let me know if this is the wrong place to discuss this.
Obviously this wouldn't be a high priority, as I think we should focus on increasing stability rather than adding features that could decrease it, but is there a possibility of encrypting the path in the future? As it is now, geolocating users is relatively easy and I think that could easily be abused especially as more people get involved.
It would probably involve something like how TOR does it, encrypting the next hop with each repeater's public key. I don't know that much about any of this, so may not be feasible at all seeing as each hop is only 1 byte, I suppose it would be trivial to brute force. Also it would complicate some cool ideas I've seen floating around the issue tracker. Maybe it would be off by default, or maybe it would need to be enabled on each repeater. Idk.
Regardless, I do think it is a discussion that should be had, even if it leads to no changes.
(Also to head off any responses that privacy and security don't matter: Meshcore is marketed as a secure messaging system, and it does matter to many of us. You might not care that you can be located or you might not care about encryption at all, just like I might not care about using meshcore for sensors or as an asset tracker.)
Beta Was this translation helpful? Give feedback.
All reactions