Skip to content

Conversation

@cmurphy
Copy link
Contributor

@cmurphy cmurphy commented Nov 19, 2025

In the setup scaffolding workflow, update Fulcio to use the Static CT
log TesseraCT instead of the Trillian-based ct_server.

This change avoids retrieving the Fulcio roots from the rootCert
endpoint, instead favoring using the known externally generated root,
which closer simulates the mechanism for distributing key material out
of band via TUF. This means the createctconfig job is not needed for
this CT log. The createtree job is also no longer needed because there
is no Trillian tree to manage.

Relates to sigstore/rekor-tiles#73

Summary

Release Note

Documentation

@cmurphy cmurphy force-pushed the tesseract branch 4 times, most recently from 14a0cb0 to edb6df6 Compare November 26, 2025 23:31
@cmurphy cmurphy marked this pull request as ready for review November 26, 2025 23:42
@cmurphy cmurphy requested review from a team as code owners November 26, 2025 23:42
@cmurphy cmurphy marked this pull request as draft December 1, 2025 22:36
@cmurphy cmurphy force-pushed the tesseract branch 2 times, most recently from 79defa5 to 7b77112 Compare December 11, 2025 00:47
@cmurphy
Copy link
Contributor Author

cmurphy commented Dec 11, 2025

This is now based on #1834 so that the Fulcio certs are generated externally and shared out of band between Fulcio and CT instead of relying on Fulcio's rootCert endpoint for distribution. All changes to createctconfig are discarded so that they don't affect the functionality of the ctlog Helm chart.

@cmurphy cmurphy force-pushed the tesseract branch 2 times, most recently from 0305629 to f91e284 Compare December 11, 2025 18:28
@cmurphy cmurphy marked this pull request as ready for review December 11, 2025 18:58
Copy link
Contributor

@haydentherapper haydentherapper left a comment

Choose a reason for hiding this comment

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

Can we leave a TODO or warning in the README that the ctlog section is now out of date?

Copy link
Contributor

Choose a reason for hiding this comment

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

Is this test still meaningful or can we just remove it? Testing that the CT log supports rotating trusted roots is testing the functionality of the CT server rather than the scaffolding setup. Also, now that we're recommending a manual process of applying a secret, we don't need to test that our custom jobs or scripts work.

Also means we can remove the verifyfulcio script

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yeah I don't think it's really meaningful, I'd love to remove it.

@cmurphy
Copy link
Contributor Author

cmurphy commented Dec 12, 2025

Can we leave a TODO or warning in the README that the ctlog section is now out of date?

I went ahead and updated it.

Copy link
Contributor

@haydentherapper haydentherapper left a comment

Choose a reason for hiding this comment

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

Looks great, love seeing a PR with lots of red! Up to you if you want to merge the other PR first and rebase or rebase this PR onto main.

In the setup scaffolding workflow, update Fulcio to use the Static CT
log TesseraCT instead of the Trillian-based ct_server.

This change avoids retrieving the Fulcio roots from the rootCert
endpoint, instead favoring using the known externally generated root,
which closer simulates the mechanism for distributing key material out
of band via TUF. This means the createctconfig job is not needed for
this CT log. The createtree job is also no longer needed because there
is no Trillian tree to manage.

Signed-off-by: Colleen Murphy <[email protected]>
@cmurphy cmurphy merged commit 97e0974 into sigstore:main Dec 12, 2025
40 checks passed
Sign up for free to 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.

2 participants