thunderbird / thunderbird/thunderbird-android
Problems encrypting email to self with Openkeychain.
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 14k
- Forks
- 2.8k
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 57
Description
Expected Behavior
When I type in my email address in the to line in k9mail, it should show my contact as a green (has key) and then successfully encrypt to it.
Current Behavior
my contacts (both emails for which I have my own keys (public and private) show up as red; when I tell it to encrypt then try to send it says 'no keys found for some of the recipients (or similar)
Steps to Reproduce (for bugs)
try to send an encrypted email from yourself to yourself in k9mail, with openkeychain encryption set up.
Context
Forgive me if I'm doing something wrong in how this is supposed to work but I can't get it to work for me...any suggestions appreciated.
I've also noticed, that if I do this a different way round - i.e. share some text from another app to openkeychain, encrypt to self, share to k9mail, it then recognises the contact and allows me to encrypt to it it in k-9 mail. However this causes problems as the email is then encrypted twice over (or various other problems which mean it can't be automatically decrypted by email clients).
I get the impression that this problem is related to k-9mails features which stop one's own email coming up in the list of suggested emails - and therefore it can't be properly selected and recognised for openkeychain.
Your Environment
Android Version: CyanogenMod 13 / Android 6.0.1
K-9 Mail: F-droid version 5.203
OpenKeychain Version: F-droid version 4.24
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Begin by reproducing the self-encryption flow in K-9 Mail with OpenKeychain using the Android and app versions reported in the issue. Investigate how the recipient is suggested and recognized, then verify that selecting the user's own address shows a usable key and permits one correctly encrypted message without the share-to-OpenKeychain workaround.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- mobile, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100