[Feature Request]: Handle node reset properly: preserve the old keys

[FFAMax]

Platform

Cross-Platform

Description

Hello, Team.

Seems like we have a gap when users reset their devices: on other devices previously learned node stuck with old key and no way to update Public Key in case device was wiped.

if we have a key for this user already, don't overwrite with a new one if the key doesn't match, don't update nodeDB at all.

[korbinianbauer]

Duplicate of #8211

[GUVWAF]

It is also related to meshtastic/protobufs#793. I think that proposal mostly solves what you're proposing too.

[FFAMax]

Commented in meshtastic/protobufs#793
Need redesign NodeDB to handle different users of the same device.

[github-actions]

This issue has not had any comment or update in the last month. If it is still relevant, please post update comments. If no comments are made, this issue will be closed automagically in 7 days.

[github-actions]

This issue has not had any comment since the last notice. It has been closed automatically. If this is incorrect, or the issue becomes relevant again, please request that it is reopened.