rust-openssl / rust-openssl/rust-openssl
boringssl conflict
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 1.6k
- Forks
- 841
- Avg merge
- 6h 51m
- Merged PRs (30d)
- 4
Description
Hi everyone!
I'm currently trying to use the rust-openssl on iOS, and my project originally depended on boringSSL. It will cause a crash. I guess it may be caused by the conflict between openSSL and boringSSL.
I want to know if there is any way to get rust-openssl link to the existing boringSSL in my project？
Here are the dependencies
openssl = { version = "0.10.61", features = ["vendored"], optional = true }
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 the reported openssl dependency declaration, especially the vendored feature, and the iOS project's existing BoringSSL linkage. Determine whether rust-openssl can use that existing library without the reported crash; the issue does not name source files or tests, so completion criteria are not defined beyond resolving the linkage conflict.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100