microsoft / microsoft/SymCrypt-OpenSSL
EVP_PKEY_private_check does not seem to work when no private key params are set
Open
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 81
- Forks
- 15
- Avg merge
- 17h 18m
- Merged PRs (30d)
- 4
Description
********* STEPS ***********
- Create
OSSL_PARAM_BLD_new()and push exponent and modulus BN params ONLY. - Create an EVP_PKEY using
EVP_PKEY_fromdata(...)and pass it params created usingOSSL_PARAM_BLD_to_param(...). - Call
EVP_PKEY_private_check()
Expected behavior: EVP_PKEY_private_check should return an error.
Actual: EVP_PKEY_private_check returns 1 (success).
OpenSSL version: 3.5.0
SymCrypt provider version: default from AzureLinux3.0.
Contributor guide
No contributing guide indexed for this repository
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 reproducing the issue with OSSL_PARAM_BLD_new(), EVP_PKEY_fromdata(), and EVP_PKEY_private_check() using only exponent and modulus parameters. Trace how the SymCrypt provider handles the resulting key during private_check; done means the incomplete key is rejected with an error rather than returning success.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- cryptography, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100