specification
specification copied to clipboard
theupdateframework
The Update Framework specification
This issue is asking for the standard to be clearer about how delegations and explicitly listed targets interact. It is possible that with a full understanding of how TUF is...
@trishankatdatadog summarised the steps for removing a delegation in https://github.com/sigstore/root-signing/pull/546#issuecomment-1319169899. We really should include that in the repository operations section of the specification. Copy/pasted here for ease of reference: >...
Generating test data for TUF clients is time consuming and error prone. It could be really cool to have a test data set to exercise clients and certify that they're...
**Issue Description:** To standardize the process for submitting issues and pull requests (PRs) in the `tuf-specification` documentation repository. Currently, there's no consistent format for these requests, which can lead to...
**Description:** This PR adds a new subsection to the `repository operations` documentation titled "Delegation removal." The new subsection outlines the steps required to remove a delegatee, including the deletion of...
WRT keyids, we currently say this: > **4.2. File formats: general principles** > KEYID: The identifier of the key signing the ROLE object, which is a hexdigest of the SHA-256...
Bumps [actions/setup-python](https://github.com/actions/setup-python) from 5.0.0 to 5.1.0. Release notes Sourced from actions/setup-python's releases. v5.1.0 What's Changed Leveraging the raw API to retrieve the version-manifest, as it does not impose a rate...
![dependabot[bot] avatar](https://avatars.githubusercontent.com/in/29110?v=4 "dependabot[bot] avatar"){kind=avatar}