microsoft / microsoft/msix-packaging
Unhardcode crypto libraries
Open
Nobody has claimed this yet.
Needs-Triage
- Dominant language
- C
- Stars
- 1.1k
- Forks
- 193
- Avg merge
- 2h 16m
- Merged PRs (30d)
- 2
Description
Safer to consume crypto libraries from upstream sources, such as openssl-dev(el).
https://conan.io/center/recipes/openssl
Relates to https://github.com/microsoft/msix-packaging/issues/706
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 reviewing issue 706 and the linked Conan OpenSSL recipe, then locate where the crypto libraries are hardcoded in the repository. Done means the project consumes the upstream OpenSSL sources or packages instead of the hardcoded libraries; the issue does not name a specific file or test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- build-system, cryptography, security
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100