Add compile-time OpenSSL version configuration
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 431
- Forks
- 44
- Avg merge
- 21h 18m
- Merged PRs (30d)
- 30
Description
- Same scenario as https://github.com/microsoft/go/issues/928
The OpenSSL version is configured through env vars, but this could lead to problems if the env vars are changed.
If an app is built for OpenSSL 1.1.1+FIPS and someone uses a tag that has both OpenSSL 1.1.1+FIPS and 3.0 (non-FIPS) installed, the OpenSSL backend will find 3.0 and not be able to enable FIPS mode. This can be fixed using GO_OPENSSL_VERSION_OVERRIDE at runtime, but the dependency on an env variable is undesirable.
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 comparing this request with microsoft/go#928 and tracing the OpenSSL backend's handling of GO_OPENSSL_VERSION_OVERRIDE. Determine where the OpenSSL version is selected during a Go build and define how compile-time configuration should prevent an installed non-FIPS version from being chosen. Done means the build no longer depends on that runtime environment variable for this selection and the relevant behavior is covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- build-system, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100