-
Notifications
You must be signed in to change notification settings - Fork 117
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
sha256 sums for OVAs + download integrity #751
Comments
This is also the case for other uncompressed artifacts, like the live ISO and PXE bits. Hmm, another alternative is to have the installer append both SHAs. Then it's up to consumers of that URL whether to verify before decompressing, after decompressing, or even both. |
This also relates to coreos/fedora-coreos-tracker#773 - size validation would also immediately show an error except in actively malicious cases. |
Remember there are two things here: I think the fix is to openshift-installer - it should honor Something like:
to start |
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
/remove-lifecycle stale |
(filing this issue here, since it crosses a couple of repos)
We made the decision back in 2019 to not compress OVA artifacts as part of
cosa compress
One of the side effects of this was that the
meta.json
doesn't have anuncompressed-sha256
entry for the OVA:Consequently, the stream metadata for the RHCOS builds are also missing this entry:
Which in turn means that the
openshift/installer
code does not append any sha256 sum when generating URIs for the OVAs:https://github.com/openshift/installer/blob/6d778f911e79afad8ba2ff4301eda5b5cf4d8e9e/pkg/rhcos/builds.go#L50-L63
I believe this may contribute to problems like https://bugzilla.redhat.com/show_bug.cgi?id=2065849 where the download is not verified and then causes problems when vSphere tries to ingest the OVA.
So this is kind of a broad issue to discuss if there are improvements/changes we should consider for the OVA case.
sha256
entry for OVAs asuncompressed-sha256
?sha256
entry and replace it withuncompressed-sha256
?sha256
entry if there is nouncompressed-sha256
entry?The text was updated successfully, but these errors were encountered: