Skip to content

fix(installer): installer-set SSL_CERT_FILE shouldn't read as a pre-set bundle to verify (client#631) - #632

Merged
LukasWodka merged 2 commits into
developfrom
fix/631-ca-trust-installer-set-message
Aug 6, 2026
Merged

fix(installer): installer-set SSL_CERT_FILE shouldn't read as a pre-set bundle to verify (client#631)#632
LukasWodka merged 2 commits into
developfrom
fix/631-ca-trust-installer-set-message

Conversation

@LukasWodka

@LukasWodkaLukasWodka commented Aug 6, 2026

Copy link
Copy Markdown
Contributor

Medium from the 2026-08-06 prod hop (scripts/lib/cluster.sh).

On the primary curl | bash Linux path, install.sh exports SSL_CERT_FILE from TRACEBLOC_CA_BUNDLE before launching install-k8s.sh, so wire_ca_trustalways saw it pre-set → took the kept branch → told the operator "keeping your pre-set SSL_CERT_FILE, make sure it includes your company's CA" for a variable the installer itself just set from that CA, and never reported the cosign/helm wiring.

Fix: a var already pointing at our CA ($ca, compared with -ef for file identity) is treated as wired (reports "Trusting your company's certificate for cosign, helm"). Only a genuinely different operator pre-set bundle takes the kept/verify branch. -ef is robust to relative/absolute/symlink path differences.

Closes#631.


Note

Low Risk
Small installer messaging/trust-branch logic change in cluster.sh with no security model change; manifest checksum updated accordingly.

Overview
wire_ca_trust no longer treats SSL_CERT_FILE / GIT_SSL_CAINFO as a foreign “pre-set bundle to verify” when they already refer to the same corporate CA file the installer resolved ($ca). The condition now also exports when the var is unset or when it is the same file as $ca (-ef, so path/symlink differences do not matter).

On the usual curl | bash path, install.sh exports SSL_CERT_FILE from TRACEBLOC_CA_BUNDLE before install-k8s.sh runs wire_ca_trust, so operators previously always saw the “keeping your pre-set…” hint and never the success line for cosign/helm wiring. Only a genuinely different pre-set bundle still uses the kept/verify branch.

scripts/manifest.sha256 is updated for scripts/lib/cluster.sh.

Reviewed by Cursor Bugbot for commit 3702084. Bugbot is set up for automated code reviews on this repo. Configure here.

…to verify' (client#631)
On the curl|bash Linux path install.sh exports SSL_CERT_FILE from TRACEBLOC_CA_BUNDLE
before launching install-k8s.sh, so wire_ca_trust always saw it pre-set, took the
'kept' branch, told the operator to verify their pre-set bundle (which the installer
itself just set), and never reported the cosign/helm wiring. Treat a var already
pointing at our CA (-ef) as wired; only a genuinely different pre-set takes 'kept'.

@cursorcursorBot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Fix All in Cursor

❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.

Reviewed by Cursor Bugbot for commit 4c60e0d. Configure here.

Comment threadscripts/lib/cluster.sh
…#631)
cluster.sh is a manifest-covered bootstrap file; its recorded sha256 was stale after
the wire_ca_trust change, so the verified curl|bash installer would reject it.
@LukasWodkaLukasWodka self-assigned this Aug 6, 2026
@LukasWodka
LukasWodka merged commit ebb392b into developAug 6, 2026
46 of 48 checks passed
@LukasWodka
LukasWodka deleted the fix/631-ca-trust-installer-set-message branch August 6, 2026 12:24
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

installer: pre-set SSL_CERT_FILE makes the CA 'kept your bundle' hint misleading; cosign/helm wiring not reported

2 participants

@LukasWodka@saadqbal