S/MIME: Verification Backend: Migrate code to openssl cms module
Nobody has claimed this yet.
- 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.
This module is supported since PHP 8.0. This requirement was not fulfilled when I started developing S/MIME verification and decryption.
Describe the solution you'd like
Use more modern opnssl cms module.
More context is available on https://security.stackexchange.com/questions/41399/openssl-pkcs7-vs-s-mime
- PKCS#7 -> S/MIME v3.0 (current implementation)
- CMS -> S/MIME v3.1 (proposed by this issue)
Describe alternatives you've considered
Leave the code as is. This might break compatibility with newer S/MIME versions in the future.
Additional context
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 reading lib/Service/SmimeService.php at lines 79-82, where the current PKCS#7-based S/MIME implementation is referenced. Review the linked context on PKCS#7 versus CMS, then determine the migration scope for verification and decryption. Done means the backend uses the modern OpenSSL CMS module while retaining the intended S/MIME behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend, security
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100