parcel-id should be fully qualified

[npmccallum]

/_i/{bindle-name}@{parcel-id}

It looks to me like the parcel-id field here is an unqualified hash. That is, it is up to the server to implicitly choose which hash algorithm to use. This should not be implicit as subtle security problems can arise from such configurations.

Wisely, because the parcel-id is always specified in the context of a bindle name, this problem is lessened somewhat. But in a content store digests should always be fully qualified (i.e. sha256:...).

[thomastaylor312]

This is a good point. Right now we only support sha256 but that will likely change to support more in the future. I'll mark this as an enhancement

[michelleN]

What would the concrete todo here be?

[thomastaylor312]

2 main things I think:

1. Change the protocol spec doc to account for this in the API
2. Update the code to implement the spec change