Trace and strip ssl algo/feature into the minimal features that rustup use.
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Rust
- Stars
- 7k
- Forks
- 1.1k
- Avg merge
- 22h 40m
- Merged PRs (30d)
- 46
Description
Problem you are trying to solve
We shouldn't build a full feature/algo set with ssl libraries, as we're just using a limited set of algo and features of openssl.
So maybe we can trace down to the minimal used set of openssl.
This would have these benefits:
- Better binary size
- Less build time
- More control over the build system, making sure that issues like https://github.com/rust-lang/rustup/issues/4979 happen less.
Solution you'd like
Trace the API usage of openssl, finding the minimal features that rustup is using, then we apply the minimal feature set to openssl build, making this possible.
Notes
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
Start by tracing rustup's OpenSSL API usage and reviewing how the OpenSSL build features are configured. Identify the algorithms and features actually used, then verify that the build applies only that minimal set and preserves rustup's existing HTTPS behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- build-system
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100