like FlowCrypt/flowcrypt-ios#1491
There will likely be a fix needed. On browser extension, the fix was mostly this:
private static chooseSigningKey = async (
view: ComposeView,
senderKis: KeyInfoWithIdentity[]
): Promise<ParsedKeyInfo | undefined> => {
const parsedSenderPrvs = await KeyStoreUtil.parse(senderKis);
// to consider - currently we choose first valid key for signing. Should we sign with all?
// alternatively we could use most recenlty modified valid key
return parsedSenderPrvs.find(k => k.key.usableForSigning);
};Until then, it was using a key for signing that may not be usable (eg revoked).
On Android, we choose signing key based on email. We have to therefore additionally filter keys by their ability to sign messages.
Larger context of the PR FlowCrypt/flowcrypt-browser@cd824fc
like FlowCrypt/flowcrypt-ios#1491
There will likely be a fix needed. On browser extension, the fix was mostly this:
Until then, it was using a key for signing that may not be usable (eg revoked).
On Android, we choose signing key based on email. We have to therefore additionally filter keys by their ability to sign messages.
Larger context of the PR FlowCrypt/flowcrypt-browser@cd824fc