Wishlist: Allow peers with duplicate public keys

[T-X]

Scenario: For a while now we have fastd public keys announced via respondd in Gluon. One feature idea to use this for was to have a method somewhere in between accepting any peer or the manual email/webform submission methods.

One such new approach would be "gluon-autokeys": https://git.chaotikum.org/freifunk-luebeck/gluon-autokeys

It helps putting these respondd announced keys into fastd peer config files. So that one already accepted node could automatically onboard and allow another node which is physically close by.

Issue: Currently it would be very easy to then kick out another node as when fastd detects a duplicate public key usage then it will disable both the original and the new peer.

Proposal: In case of public key duplicates only deactivate/ignore the one which has just a public key setting. If both only have a public key entry, disable any of the two as they are identical anyway. (Or just add both? If that made sense for fastd?)

[T-X]

Nevermind, not that important anymore, adjusted the checks in the gluon-autokeys and would probably go with a single keys repo for now, instead of the two separate ones for manually and automatically added keys that I had originally in mind. (Current state for the new fastd key repo looks like this now: https://git.chaotikum.org/freifunk-luebeck/ffhl-fastd-autokeys)