thunderbird / thunderbird/thunderbird-android

Error reporting for unsafe keys isn't very helpful

Open
#2,054 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

type: third-party integration
Dominant language
Kotlin
Stars
14k
Forks
2.8k
Avg merge
3d 3h
Merged PRs (30d)
57

Description

Expected behavior

When I open a Mail in the "Sent Mail" Folder that was encrypted and signed by my own GPG Key it should be OK and no Warning displayed.

Actual behavior

Opening an E-Mail that was signed and encrypted by my own GPG Key (with K-9 and OpenKeychain) from the "Sent E-Mail Folder, I get the message "Safety Warning: This message was signed by an unsafe Key - Show message anyways"

Steps to reproduce
  1. Send an encrypted E-Mail
  2. go the the "Sent E-Mails Folder and open the Mail you just sent
  3. Read the Error Message
Environment

K-9 Mail version: 5.202

Android version:4.4.2

Account type (IMAP, POP3, WebDAV/Exchange): IMAP


First of all I want to tell you that the new K-9 Version made an enormous improvement in handling encrypted messages.
Great work :-)

The Bug is merely a little annoying - why is my own Key "unsafe" ?
Why does K-9 not trust my own identity ?

screenshot_2017-01-14-10-08-23

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no source file or test; start by reproducing the sent-mail case on Android with K-9 Mail and OpenKeychain, then trace the unsafe-key warning shown when opening the message. Done means the user's own signing and encryption key is recognized appropriately and the warning no longer appears for this case.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, kotlin
Domain
mobile-dev, security
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.