Assume I have email address user@example.com with an alias alias1@example.com and alias2@example.com.
During setup, I manually import a key with uids user@example.com and alias2@example.com.
What currently happens is that by default, we submit the public key to both user@example.com and alias1@example.com even though this email alias was not mentioned in the key. It confuses some users.
What we should do when importing keys:
- handling of submitting to primary email address is unchanged
- aliases continue to get submitted by default as well, with the checkbox as it is now
- the list of aliases, during setup, will get filtered by whether they are mentioned in the private key being imported.
That means by default, in this situation, public key gets submitted for user@example.com and alias2@example.com. As before, user may uncheck either the aliases checkbox or the overall pubkey submission checkbox.
Assume I have email address
user@example.comwith an aliasalias1@example.comandalias2@example.com.During setup, I manually import a key with uids
user@example.comandalias2@example.com.What currently happens is that by default, we submit the public key to both
user@example.comandalias1@example.comeven though this email alias was not mentioned in the key. It confuses some users.What we should do when importing keys:
That means by default, in this situation, public key gets submitted for
user@example.comandalias2@example.com. As before, user may uncheck either the aliases checkbox or the overall pubkey submission checkbox.