Triaging as high, as this introduces a vulnerability should I ever lose access over the private key.

For the record, this key is currently (and intentionally) used by _two_ developer accounts:

• https://ldap.toolforge.org/user/urbanecm (my main account)
• https://ldap.toolforge.org/user/urbanecmtest (my testing account)

I do see the key in Bitu on my testing account, but not on my main account. The same is true for the other duplicated key (urbanecm@notebook, also still under my control).

As far as I know, we don't have a "only one user per key" policy (only "production key is strictly for production" kind of rule, which I respect). So, maybe Bitu is having issues handling keys that are assigned to multiple developer accounts?

So, maybe Bitu is having issues handling keys that are assigned to multiple developer accounts?

Correct, perhaps not as much "issues" as a design choice. The thinking was that a key re-use across accounts would only happen if a key was stolen.

We'll need to work out what the best course of action is, because you're correct that your use case isn't disallow, and it would introduce a vulnerability if you lose your key. On the other hand the feature is there to protect others :-)

Let me just work out with the others involved how we want to solve this.

I see. Maybe you have already thought about this, but can we simply display "key also used by XX" in IDM? If we want to, we can even add an "Ack" button, forcing both accounts to explicitly acknowledge this is done intentionally.

On a larger note, I'm not sure how realistic this protection would be. If someone gained access to my private key, they very likely have access to my disk (where the key is stored). At that point, it is relatively trivial to manipulate my browser to do stuff for them (such as read the password the next time I login).