![]() Can confirm, GNS3 VM.ova found within GNS3.VM.VMware.Workstation.2.2.34.zip imports fine.Ī. I just tried it again for a sanity check. Just to be clear, you are saying that GNS3 VM.ova (sha256 hash d4b15a691c132522d1c88aa62487c0702826addee15b1be32e5f610fc1b6afab, extracted from GNS3.VM.VMware.Workstation.2.2.34.zip) imports fine with VMware Workstation while HAOS doesn't? Do you import it as zip file or ova (does it make a difference)? I also checked file endings, the both seem to be UNIX style. I am not advocating for one way over another, but I thought the above would be helpful to the discussion. Whonix uses SHA1 hashes within their OVA too, but they provide external SHA512 digests and sign the container with GPG. Here are some other examples of appliances currently shipped with a SHA1 digests in their manifests: VMWAre Photon OS (but they ship a cert within the ova!), turnkey linux appliances, blackarch linux, Bitnami (absorbed by VMWare) appliances, nixos. I imagine that the popularity of SHA1 manifests shipped with unsigned appliances - as opposed to SHA256 - is to provide better compatibility with older hypervisors while still allowing integrity verification, and security is not the goal. For the latter, it would need to be signed. I'm not sure if this is something you'd want to look into, but while researching the import issue, I saw some mentions (sadly I didn't save the link) that the hash manifest was in the OVA for security, but it really isn't, and can only be relied upon to verify the integrity of the downloaded file. One thing I noticed is that some OVA publishers also include a certificate to make it a signed appliance. VMWare products sometimes have very anachronistic components, so it was a short lived "aha" moment for me when I thought SHA256 was too "new" for Workstation. The workaround isn't lengthy or complicated, but it adds up. Yep, but in my case I use Workstation and ESXi extensively, so a fix would ease my workflow. That is an interesting find! I downloaded the file, and indeed it seems to use SHA256 sums, and even in the very same format as Home Assistant OS: That is what I assumed first, and if that would be the case I'd almost say let's push VMware to finally support a modern hash algorithm □ Many appliances still use SHA1 for the manifest file, and it made me wonder if perhaps VMWare Workstation only supported that, and not SHA256. However, the fact that even the latest VMWare Workstation doesn't work is not nice. I remember last time I looked at it that the person mentioned that Workstation didn't work, but since it wasn't a problem for him I did not further investigate (maybe that also was an old VMware Workstation version). Start to import into VMWare Workstation.Īnything in the Supervisor logs that might be useful for us?.Ova (for Virtual Machines) What version of Home Assistant Operating System is installed? Interestingly, they ship a separate OVA files for Workstation/Fusion and ESXi. I looked at the manifest of another project ( ) that ships OVA appliance files, and it uses SHA256 hashes, and the OVA imports into Workstation fine, so the same should apply to the HAOS one. ![]() There was an issue related to ESXi and the hash function on the nextcloud issue tracker nextcloud/vm#910 (comment) but this was dealing with ESXi and not Workstation, and with an older (5.5) unsupported ( ) release of the hypervisor. One such issue was #826 - since fixed/closed - dealing with ESXi import errors, but one commenter reported that this was not yet fixed in relation to Workstation (see #826 (comment) and #826 (comment)) ![]() I have searched existing issues to avoid posting a dup, and found some related discussion, but nothing that addresses this specific issue with VMWare Workstation.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |