Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add embedded TUF root update mechanism #416

Open
jku opened this issue Feb 21, 2025 · 3 comments
Open

Add embedded TUF root update mechanism #416

jku opened this issue Feb 21, 2025 · 3 comments
Labels
enhancement New feature or request

Comments

@jku
Copy link
Member

jku commented Feb 21, 2025

Keeping the embedded TUF root updated (like in #414) is not required but it's useful as clients then download less on the first run.

The update itself is a little annoying to do though: how do you ensure the PR content is correct? I came up with this solution in sigstore-python (sigstore/sigstore-python#1301):

  • Makefile rule that
    • runs the client just enough to securely update the cached root
    • copies the cached root into the sources
  • Workflow that
    • executes the make rule on cron
    • files an issue if the root embedded in source changed

This has two uses:

  1. it files an issue if embedded root does not match current root
  2. gives maintainers an easy way to create a PR (or verify it)

Feel free to steal the relevant parts from sigstore-python

@jku jku added the enhancement New feature or request label Feb 21, 2025
@codysoyland
Copy link
Member

Thanks @jku, that's a great script. I was actually just thinking about writing something similar using tufie, but if this already works, I'm down for including it!

@haydentherapper
Copy link
Contributor

+1, this would be a great addition.

@jku
Copy link
Member Author

jku commented Feb 21, 2025

I was actually just thinking about writing something similar using tufie, but if this already works, I'm down for including it!

It will need some modification to switch the sigstore-python specific bits with sigstore-go ... but should be a good starting point.

At least I would use sigstore-go itself (and not some other client) to fetch the current root, that feels correct.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants