Just get rid of the sid name
Just get rid of the sid name
Posted Aug 11, 2024 6:29 UTC (Sun) by NYKevin (subscriber, #129325)In reply to: Just get rid of the sid name by bluca
Parent article: Distinguishing Debian testing from unstable
You're already doing like 80% of the work. You need to have a standard "recipe book" for creating images (unless you're one of those "the sysadmin does everything manually" people, but those people mostly don't use images in the first place). All I'm suggesting is that you keep track of which recipe you used. It's one value, which is probably just an integer or UUID. Why is that difficult?
> Also, by self-identifying, metadata is automatically covered by cryptographic signature o f the artifact, so if this is used in a deployment system, it can be trusted, without the need to implement a sidecar metadata and its own out-of-band verification methods.
Pffft, that's ridiculous. As soon as you have two or more computers, and they're not all in the same physical trust domain (building, in most cases, or perhaps an entire physically-secured campus), you need certificates and signatures on absolutely everything that moves between them. If you rely on the image's signature, then the recipient has to blindly trust that you wanted this image, and not any other image, installed on this hardware. For that matter, the recipient also has to blindly trust that you wanted the installation to take place at all. What if some attacker calls InstallImageOnComputer (or whatever it's named) on all of your production serving instances at once? You'll have an outage, and it will be entirely your own fault for letting them do that.
So you have to sign a metadata sidecar anyway, and this is not a real objection.
