You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
🔒 security(registries): route token-fetch requests through operator TLS settings
GAR, GitLab, Mau, DHI and public-ECR built their own token-fetch request
and called axios() directly, bypassing withTlsRequestOptions() — so the
credential exchange ignored the operator's cafile / insecure / client-cert
config and validated against the system trust store instead. A MITM with a
system-trusted cert could intercept the registry secret in the Authorization
header even when a private CA was configured.
- Promote BaseRegistry.withTlsRequestOptions from private to protected.
- Wrap each provider's token-fetch request with it (public-ECR branch only;
the private-ECR path uses the AWS SDK and is out of scope).
- Align Ecr to extend BaseRegistry (it was the only provider extending the
bare Registry, so it lacked the shared auth/TLS helpers).
0 commit comments