Aditya Sirish

This matters for tags, commits, and trees. For tags and commits, we want to resolve to the replace target for signature checks as well as to identify underlying target commit...

A good first step is to route all `Get{Object}` requests through `gitinterface` so we have a single place to check for replace directives

It's more like instead of `file:foo/*`, we would say something like `file:foo/*;whenBranch=main` or so.

Thanks for opening the issue! My first thought was whether we'd be able to generalize delegation structures IRL, but on more reflection, I wonder if in practice we'll see repeated...

Related: https://github.com/theupdateframework/taps/blob/master/tap3.md

> But for this, they need to be authorized to sign the RSL entry for the policy namespace. This is not true anymore. The validity of a policy state is...

The RSL state can be used to infer snapshot properties (minus, possibly, the signer making the snapshot claim). It could be as simple as setting some constraints on what targets...

That does, however, require us to work out how targets can be removed when the delegated role is no longer necessary. This is one of a few examples we've encountered...

1) Added some scaffolding to support different algorithms. This isn't used yet though because we need to settle the data model for the hash mapping. 2) This should be compatible...

Closing as Git has early support for SHA-1 SHA-256 compatibility. We should reevaluate with support for other hash algorithms later.