Skip to content

multiple pubkeys per email - Importing pub keys manually #1542

@tomholub

Description

@tomholub

Importing pub keys
Here we can have two cases:

  1. key with a single user id: for example key for A@flowcrypt.test It's a simple case.

Here we have the same behavior as before.

Not the same as before. Before, you were always the public key. Now, need to compare it to existing public keys of that one recipient by primary fingerprint.

  • if the key is not present in the list of keys of that one recipient, add it to the list
  • if already present, then compare by lastModified. If the offered key is newer, then replace the existing key by the newer key. If older, then do nothing.
  1. key with a few user ids: for example key for A@flowcrypt.test, B@flowcrypt.test

Here we have 2 theoretical recipients: A@flowcrypt.test, B@flowcrypt.test. Should I add 2 entries to the local database

1| FINGERPRINT| A@flowcrypt.test | KEY
2| FINGERPRINT| B@flowcrypt.test | KEY

I suppose here we're talking about manual import of potentially many public keys? Where user is just importing keys without further interaction, and not indicating for which user they are importing the keys. Let's do the safer thing - only import for primary user id. So that would be one entry (subject to the same procedure with list handling as above). We could reconsider it in the future.

Originally posted by @DenBond7 in #1188 (comment)

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions