Skip to content

should repository make unversioned root metadata available or not? #184

@jku

Description

@jku

small inconsistency with regards to root.json versions: 6.2.1. Writing consistent snapshots states:

an implementation must write both root.json and version_number.root.json because it is possible to download root metadata both with and without known version numbers.

It is not in fact documented that client could download root without a version (client workflow only downloads versioned roots). I can see how a Trust-On-First-Use (TOFU) client initialization could use this but that is not defined in the spec.

I guess either

  • TOFU initialization could be mentioned as a possibility (even if not recommended)
  • the requirement to offer unversioned root.json should not be there

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions