Add "legacy", key and cert PBE alg options to openssl_pkcs12_export
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 40.4k
- Forks
- 8.1k
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 96
Description
Description
Please consider adding support for forcing legacy mode for openssl_pkcs12_export. Currently the only workaround I know, is to switch completely to calling command line openssl pkcs12 -export directly with -legacy option, which requires enabling proc_open or other similar functions, which can pose security risk. Unfortunately many systems and applications still understands only legacy algorithms in PKCS#12 files so many are still forced to use them when creating PKCS#12 files.
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 locating the openssl_pkcs12_export implementation and its related tests in php-src, then inspect how PKCS#12 export options are passed to OpenSSL. Done means the legacy, key PBE, and certificate PBE options can be forced without invoking the command-line tool, with coverage for the new behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, php
- Domain
- cryptography, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100