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

[Spec Change] Use public key (hashed?) as id #12

Open
Aras14HD opened this issue Jan 20, 2022 · 1 comment
Open

[Spec Change] Use public key (hashed?) as id #12

Aras14HD opened this issue Jan 20, 2022 · 1 comment
Labels
accepted The feature is accepted enhancement New feature or request
Projects

Comments

@Aras14HD
Copy link
Collaborator

This would eliminate attacks based on impersonating nodes, but potentially increase the message length and need a few more features like a key type byte attached to the ID, moving to new IDs, certificates signed via the old ID referring to the new ID and potentially more.

@Aras14HD Aras14HD added the enhancement New feature or request label Jan 20, 2022
@Aras14HD
Copy link
Collaborator Author

Potential solution for moving to new IDs:

Set the distance to the old ID(s) to 0, and respond with a "moved" message containing the new ID signed by the old one on its behalf.
Upon receiving such a response, the node sending the message/request verifies the signature and changes the ID/Public Key of the contact internally.

@Aras14HD Aras14HD added this to Accepted in Planning May 7, 2022
@Aras14HD Aras14HD added the accepted The feature is accepted label May 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
accepted The feature is accepted enhancement New feature or request
Projects
Planning
Accepted
Development

No branches or pull requests

1 participant