S/MIME certificate email address not correctly detected
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1k
- Forks
- 348
- Avg merge
- 12h 28m
- Merged PRs (30d)
- 91
Description
Steps to reproduce
- Open S/MIME certificate import dialog
- Import .p12 certificate
- After the import, check that the certificate name and email field contains the same value
Expected behavior
The email address of the certificate should be correctly detected, allowing to assign it to an email alias and use it to sign/encrypt emails.
Actual behavior
The email address is not correctly detected and contains the certificate name value, which means the certificate cannot be assigned to an email alias, thus preventing from using it.
Mail app version
3.2.4
Mailserver or service
No response
Operating system
Ubuntu 22.04 - Docker Nextcloud All-In-One
PHP engine version
PHP 8.1
Web server
Apache (supported)
Database
PostgreSQL
Additional info
My first thought is that maybe it contains the email address in a non-conventional field? In my case is the Subject Alternative Name. For obvious reasons, I cannot share the certificate to allow you to reproduce it, but I can try to give you as much information as possible, in case you need it. Thank you all.
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 at the S/MIME certificate import dialog and trace how a .p12 certificate populates its name and email fields, including whether the email is read from Subject Alternative Name. Reproduce with a certificate exposing that field if possible; done means the detected email differs from the certificate name and can be assigned to an alias for signing or encryption.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- cryptography, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100