S/MIME on FIPS-enabled system
Open
Nobody has claimed this yet.
1. to develop
bug
feature:smime
- Dominant language
- JavaScript
- Stars
- 1k
- Forks
- 348
- Avg merge
- 12h 28m
- Merged PRs (30d)
- 91
Description
Steps to reproduce
- Run a FIPS-enabled system like RHEL
- Receive an encrypted S/MIME email that was encrypted using the PKCS#1 v1.5 padding
Expected behavior
Incoming email can be decrypted
Actual behavior
Incoming email can not be decrypted
Mail app version
5.x
Nextcloud version
No response
Mailserver or service
No response
Operating system
No response
PHP engine version
None
Nextcloud memory caching
No response
Web server
None
Database
None
Additional info
No response
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
No file, entry point, or test is named. Start by locating the S/MIME decryption path and its handling of PKCS#1 v1.5 on FIPS-enabled systems, then reproduce the failure on RHEL or an equivalent environment; done means the encrypted incoming message decrypts successfully without weakening FIPS constraints.
Written by the indexing model from the issue text.
Assessment
- Domain
- security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100