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
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.
The text was updated successfully, but these errors were encountered:
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.
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.
The text was updated successfully, but these errors were encountered: