fix: include the approved public CA bundle in release images
All checks were successful
Mostovik Backend CI/CD / Tests and lint (push) Successful in 4m22s
Mostovik Backend CI/CD / Build linux/amd64 release images (push) Successful in 2m53s
Mostovik Backend CI/CD / Deploy and verify internal main (push) Has been skipped
Mostovik Backend CI/CD / Deploy dev (push) Successful in 2m55s
All checks were successful
Mostovik Backend CI/CD / Tests and lint (push) Successful in 4m22s
Mostovik Backend CI/CD / Build linux/amd64 release images (push) Successful in 2m53s
Mostovik Backend CI/CD / Deploy and verify internal main (push) Has been skipped
Mostovik Backend CI/CD / Deploy dev (push) Successful in 2m55s
This commit is contained in:
@@ -119,3 +119,7 @@ readiness remains separate from enablement.
|
||||
session behind a default-off setting and a dev-only host compose flag after
|
||||
explicit user consent — cost if wrong: only SPB gains this extra trust;
|
||||
MOEX/system/main trust remains unchanged, certificate verification stays on.
|
||||
- Ruling: whitelist exactly the existing public Russian CA bundle in Docker
|
||||
context and fail release image builds if it is missing — live image omitted
|
||||
it under the generic PEM exclusion — cost if wrong: this public bundle is
|
||||
shipped in web/worker; all other PEM/keys remain excluded.
|
||||
|
||||
Reference in New Issue
Block a user