[vbox-dev] 5.2.34 hash failures

Klaus Espenlaub klaus.espenlaub at oracle.com
Thu Oct 17 14:41:23 GMT 2019

odd... this smells like we had unsigned rpm files reaching the
checksums/public files. Shouldn't be possible, since signing is done
earlier than calculating the checksums and updating the repos.

Either way, it's sorted (and the files served were always the right
ones, which is the most important thing). Confirmed to be fixed around
16 hours ago.

If you see any remaining trouble, please let us know.


On 16.10.2019 14:37, Ladar Levison wrote:
> It seems that several of the files in the 5.2.34 download directory
> don't match the provided SHA-256 hash. Only the RPM/DMG files appear
> to be invalid.
> I found this issue because yum failed to update itself properly via
> the el7 repo. It seems at a minimum, the el7 repo also has an invalid
> copy of the 5.2.34 rpm. I say invalid because the hash inside the
> primary.xml file doesn't match the rpm hash. I can't speak to whether
> the rpm is actually valid, and/or whether the signature is valid. See
> below.
> --
> L~
> Oracle_VM_VirtualBox_Extension_Pack-5.2.34-133893.vbox-extpack: OK
> Oracle_VM_VirtualBox_Extension_Pack-5.2.34.vbox-extpack: OK
> SDKRef.pdf: OK
> UserManual.pdf: OK
> VBoxGuestAdditions_5.2.34.iso: OK
> *VirtualBox-5.2-5.2.34_133893_el6-1.i686.rpm: FAILED**
> **VirtualBox-5.2-5.2.34_133893_el6-1.x86_64.rpm: FAILED**
> **VirtualBox-5.2-5.2.34_133893_el7-1.x86_64.rpm: FAILED**
> **VirtualBox-5.2-5.2.34_133893_el8-1.x86_64.rpm: FAILED**
> **VirtualBox-5.2-5.2.34_133893_fedora26-1.i686.rpm: FAILED**
> **VirtualBox-5.2-5.2.34_133893_fedora26-1.x86_64.rpm: FAILED**
> **VirtualBox-5.2-5.2.34_133893_fedora29-1.x86_64.rpm: FAILED**
> **VirtualBox-5.2-5.2.34_133893_openSUSE132-1.i586.rpm: FAILED**
> **VirtualBox-5.2-5.2.34_133893_openSUSE132-1.x86_64.rpm: FAILED**
> **VirtualBox-5.2-5.2.34_133893_openSUSE150-1.x86_64.rpm: FAILED*
> VirtualBox-5.2.34-133893-Linux_amd64.run: OK
> VirtualBox-5.2.34-133893-Linux_x86.run: OK
> *VirtualBox-5.2.34-133893-OSX.dmg: FAILED*
> VirtualBox-5.2.34-133893-SunOS.tar.gz: OK
> VirtualBox-5.2.34-133893-Win.exe: OK
> VirtualBox-5.2.34.tar.bz2: OK
> VirtualBoxSDK-5.2.34-133893.zip: OK
> virtualbox-5.2_5.2.34-133893~Debian~jessie_amd64.deb: OK
> virtualbox-5.2_5.2.34-133893~Debian~jessie_i386.deb: OK
> virtualbox-5.2_5.2.34-133893~Debian~stretch_amd64.deb: OK
> virtualbox-5.2_5.2.34-133893~Debian~stretch_i386.deb: OK
> virtualbox-5.2_5.2.34-133893~Ubuntu~bionic_amd64.deb: OK
> virtualbox-5.2_5.2.34-133893~Ubuntu~trusty_amd64.deb: OK
> virtualbox-5.2_5.2.34-133893~Ubuntu~trusty_i386.deb: OK
> virtualbox-5.2_5.2.34-133893~Ubuntu~xenial_amd64.deb: OK
> virtualbox-5.2_5.2.34-133893~Ubuntu~xenial_i386.deb: OK
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.virtualbox.org/pipermail/vbox-dev/attachments/20191017/015c2b9e/attachment.html>

More information about the vbox-dev mailing list