choosing our own pubkey (sender) during compose/reply

[tomholub]

There will need to be some logic improvements in how our own pubkey is selected when encrypting a message.

I will add details

[tomholub]

Need to solve the following:

1. I may have 2 different accounts: me@company.com and me@hello.eu
2. The me@company.com may have several alias emails: me@company.com, contact@company.com, purchases@company.com
3. I may have many private keys that serve various purposes for these accounts
4. Which of my own public keys to encrypt for when sending out a message?

To be continued

[tomholub]

Where do we currently get our own public key? In in the private key table, or in the contacts table?

[DenBond7]

As you can see

flowcrypt-android/FlowCrypt/src/main/java/com/flowcrypt/email/api/email/sync/tasks/SendMessageSyncTask.java

Line 462 in 8ea029b

private String getAccountPublicKey(Context context, Js js, AccountDao accountDao) {

Firstly we try to get an account public key from the database. If the key not found we generate it from the private key and save it to the database,

[tomholub]

I see it. It seems to take the first private key. That is the logic that we need to improve, I'll write something up.

[tomholub]

Note to myself: this should be a high priority

[tomholub]

Use logic from here:
#269 (comment)

[DenBond7]

Is it a duplicate of #269?