@Ben is going to get this sorted for you, so most of what I'd usually say here is not needed.
I wanted to pick up on the theme of "daft". You're absolutely right about a public key being public - they're fine to share. But not give them to different owners. They should have a single owner (account).
The best analogy for this stuff iI have found s a padlock on a box.
Your public/private keys are not keys, but a padlock and its key. Your public key is a lock. You give that to anyone you want - they can then lock up a box with it and send it where-ever, but only you, the owner of the private key, have the key to unlock it.
So, while it's possible for many people to use the key pair, you reduce your security by sharing public keys with many accounts.
More importantly, you massively reduce trust. Someone sending you something locked up with your padlock probably has a very good reason to use it, and they *really* would like to know that it is only you, on the intended account, that can open the box they send you.
Enforcing uniqueness by key is something more systems should be doing, it is the right thing to do.
But I would like a feature in Bitbucket to allow admins (rather than just Atlassian) to be able to identify the account that needs to stop sharing keys.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.