thunderbird / thunderbird/thunderbird-android
Display transport security of received email
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 14k
- Forks
- 2.8k
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 57
Description
Expected behaviour
An email which was delivered between two servers (i.e. not between a server and itself over a loopback address) should be marked as insecure if it was not done in an encrypted fashion.
An email which was delivered securely in each step should be mark as secure.
Note: This does still apply to PGP/MIME and S/MIME email which otherwise leak information like the subject, to and from address and other headers.
Steps to test
- Receive an email sent securely, check the secure indicator is shown.
- Receive an email sent insecurely, check the insecure indicator is shown.
Method to implement
Processing of MIME "Received" headers.
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
Start by tracing the MIME "Received" header processing and the existing secure indicator. Use the listed steps to test messages delivered securely and insecurely, including multi-server delivery. Done means each delivery path is marked secure only when every server-to-server step was encrypted, while loopback delivery is excluded.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin
- Domain
- mobile, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100