Give insights into S/MIME verification status
Open
Nobody has claimed this yet.
1. to develop
enhancement
feature:smime
security
skill:backend
skill:frontend
- Dominant language
- JavaScript
- Stars
- 1k
- Forks
- 348
- Avg merge
- 12h 28m
- Merged PRs (30d)
- 91
Description
Is your feature request related to a problem? Please describe.
As a user I want to see why incoming message signed via S/MIME have a valid or invalid signature.
Describe the solution you'd like
- Requires https://github.com/nextcloud/mail/issues/7666 for the basic verification.
In addition the app shall collect info about the certificate, the used authority, etc. Same goes for invalid signatures. Tell they user why the signature is invalid, e.g. due to CA mistrust or certificate expiry.
Describe alternatives you've considered
N/a
Additional context
This is part of https://github.com/nextcloud/mail/issues/7085.
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 reviewing issues #7666 and #7085, then trace the existing S/MIME verification flow. Define how certificate details, certificate authority information, and reasons for invalid signatures such as CA mistrust or expiry should be presented for both valid and invalid messages.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, php
- Domain
- full-stack, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100