Tosone 76e1086035 refactor(builder): encrypt builder secrets with AES-GCM ...

The authorization token, signing key and SCM credentials handed to a build
runner were encrypted with AES-CTR, which has no integrity protection: a
tampered environment value decrypted into garbage that downstream code
would only fail on much later.

Use crypt.Seal/crypt.Open for those values. The key stays the same
per-build key derived from the builder and runner IDs, and every secret is
sealed once up front instead of inline in the env list, so a failure is
reported before the runner starts.

Verification:
- go build -tags "netgo,timetzdata,exclude_graphdriver_btrfs,containers_image_openpgp" ./...
- CI_DATABASE_TYPE=turso go test -tags "netgo,timetzdata,exclude_graphdriver_btrfs,containers_image_openpgp" ./pkg/background/build/...

2026-10-27 21:07:49 +08:00

..

source

chore: initial commit

2026-08-01 20:32:49 +08:00

api_test.go

feat(config): add tlsVerify option for builder api client

2026-08-20 14:50:29 +08:00

api.go

feat(config): add tlsVerify option for builder api client

2026-08-20 14:50:29 +08:00

cache.go

refactor(clients): propagate request context through registry clients

2026-10-03 16:20:36 +08:00

checker.go

refactor(builder): encrypt builder secrets with AES-GCM

2026-10-27 21:07:49 +08:00

config.go

feat(config): add tlsVerify option for builder api client

2026-08-20 14:50:29 +08:00

flow.go

refactor(clients): propagate request context through registry clients

2026-10-03 16:20:36 +08:00

init.go

chore: initial commit

2026-08-01 20:32:49 +08:00

tag.go

chore: initial commit

2026-08-01 20:32:49 +08:00