image-spec icon indicating copy to clipboard operation
image-spec copied to clipboard

Should the descriptor urls field be deprecated

Open sudo-bmitch opened this issue 1 year ago • 5 comments

With the deprecation of nondistributable layers, I'm curious if the descriptor urls field should also be deprecated. Are there existing uses of this field outside of nondistributable layers? If so, I'm curious if those uses break any clients or registries?

sudo-bmitch avatar Sep 06 '24 14:09 sudo-bmitch

I've personally used it for large layers that canonically exist elsewhere (so mirroring them to another registry doesn't add a ton of value for me), but it's also a bit of an unexpected privacy breach.

tianon avatar Sep 06 '24 18:09 tianon

I remember @jonjohnsonjr had some input on when we had this discussion about URLs field.

sajayantony avatar Sep 12 '24 17:09 sajayantony

url field as it is used currently is potentially dangerous if pointing to a malicious source. One suggestion was to move the url under annotations just to satisfy regulatory requirements should they arise.

rchincha avatar Sep 12 '24 20:09 rchincha

If it's content addressable (with a verified digest) how would a URL be malicious in a way that a registry hosted blob isn't?

sudo-bmitch avatar Sep 12 '24 20:09 sudo-bmitch

Privacy/tracking is the thing that comes to mind for me right away.

Another potential concern (theoretical) is that my registry provider may be taking measures to detect and block collision attacks (like GitHub does! ❤️), but this could be used to bypass that in a way that doesn't even notify the user it fetched content from an unexpected place (and not unexpected in the "my registry redirected me to S3 or somewhere else inside their trust boundary" way but rather in a "content author was able to redirect me to a malicious place").

tianon avatar Sep 12 '24 21:09 tianon