bazel-contrib / bazel-contrib/rules_go
Support GOFIPS140 build time opt-in to FIPS
Open
- Dominant language
- Go
- Stars
- 1.5k
- Forks
- 760
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 12
Description
Before 1.24, the API to opt into boringcrypto is:
```
go_download_sdk(
name = "go_sdk",
experiments = ["boringcrypto"],
...
)
```
The new API is to set the `GOFIPS140` variable and the `GOEXPERIMENT` is going to go away in an upcoming release. How should we support this in rules_go?
Contributor guide
Research direction
Start by tracing the go_download_sdk entry point and the existing experiments=["boringcrypto"] handling. Determine how rules_go should accept the GOFIPS140 variable as GOEXPERIMENT is removed, and consider the compatibility behavior that the completed change must provide.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100