Provider.add_conf_parameter
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 276
- Forks
- 200
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 7
Description
Originally I thought that providers could only be configured through openssl.cnf or environment variables, unlike engines which had engine.ctrl_cmd("MODULE_PATH", path) to achieve that.
But last week I noticed that libp11 (the same one where engine-pkcs11 comes from) implemented another PKCS#11 provider, their documentation now says that OSSL_PROVIDER_load() can be used to load a provider as needed and then OSSL_PROVIDER_add_conf_parameter() can be used to configure it.
ruby-openssl already has OSSL_PROVIDER_load(); would it be possible to also add an OpenSSL::Provider#add_conf_parameter() method that performs OSSL_PROVIDER_add_conf_parameter()?
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 examining ruby-openssl’s existing OSSL_PROVIDER_load binding and the libp11 provider-controls documentation. Trace how OpenSSL::Provider methods map to provider APIs, then verify that the requested method performs OSSL_PROVIDER_add_conf_parameter() and accepts the intended provider configuration values.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- cryptography
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100