<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
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.<br>
<br>
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.<br>
<br>
If you see any remaining trouble, please let us know.<br>
<br>
Klaus<br>
<br>
<div class="moz-cite-prefix">On 16.10.2019 14:37, Ladar Levison
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:56a64cb6-0a15-dc9b-4a71-f73be9874c35@lavabit.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<p><font face="Helvetica, Arial, sans-serif">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.</font></p>
<p><font face="Helvetica, Arial, sans-serif">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.</font></p>
<p><font face="Helvetica, Arial, sans-serif">--<br>
</font></p>
<p><font face="Helvetica, Arial, sans-serif">L~</font></p>
<p>Oracle_VM_VirtualBox_Extension_Pack-5.2.34-133893.vbox-extpack:
OK<br>
Oracle_VM_VirtualBox_Extension_Pack-5.2.34.vbox-extpack: OK<br>
SDKRef.pdf: OK<br>
UserManual.pdf: OK<br>
VBoxGuestAdditions_5.2.34.iso: OK<br>
<b>VirtualBox-5.2-5.2.34_133893_el6-1.i686.rpm: FAILED</b><b><br>
</b><b>VirtualBox-5.2-5.2.34_133893_el6-1.x86_64.rpm: FAILED</b><b><br>
</b><b>VirtualBox-5.2-5.2.34_133893_el7-1.x86_64.rpm: FAILED</b><b><br>
</b><b>VirtualBox-5.2-5.2.34_133893_el8-1.x86_64.rpm: FAILED</b><b><br>
</b><b>VirtualBox-5.2-5.2.34_133893_fedora26-1.i686.rpm: FAILED</b><b><br>
</b><b>VirtualBox-5.2-5.2.34_133893_fedora26-1.x86_64.rpm:
FAILED</b><b><br>
</b><b>VirtualBox-5.2-5.2.34_133893_fedora29-1.x86_64.rpm:
FAILED</b><b><br>
</b><b>VirtualBox-5.2-5.2.34_133893_openSUSE132-1.i586.rpm:
FAILED</b><b><br>
</b><b>VirtualBox-5.2-5.2.34_133893_openSUSE132-1.x86_64.rpm:
FAILED</b><b><br>
</b><b>VirtualBox-5.2-5.2.34_133893_openSUSE150-1.x86_64.rpm:
FAILED</b><br>
VirtualBox-5.2.34-133893-Linux_amd64.run: OK<br>
VirtualBox-5.2.34-133893-Linux_x86.run: OK<br>
<b>VirtualBox-5.2.34-133893-OSX.dmg: FAILED</b><br>
VirtualBox-5.2.34-133893-SunOS.tar.gz: OK<br>
VirtualBox-5.2.34-133893-Win.exe: OK<br>
VirtualBox-5.2.34.tar.bz2: OK<br>
VirtualBoxSDK-5.2.34-133893.zip: OK<br>
virtualbox-5.2_5.2.34-133893~Debian~jessie_amd64.deb: OK<br>
virtualbox-5.2_5.2.34-133893~Debian~jessie_i386.deb: OK<br>
virtualbox-5.2_5.2.34-133893~Debian~stretch_amd64.deb: OK<br>
virtualbox-5.2_5.2.34-133893~Debian~stretch_i386.deb: OK<br>
virtualbox-5.2_5.2.34-133893~Ubuntu~bionic_amd64.deb: OK<br>
virtualbox-5.2_5.2.34-133893~Ubuntu~trusty_amd64.deb: OK<br>
virtualbox-5.2_5.2.34-133893~Ubuntu~trusty_i386.deb: OK<br>
virtualbox-5.2_5.2.34-133893~Ubuntu~xenial_amd64.deb: OK<br>
virtualbox-5.2_5.2.34-133893~Ubuntu~xenial_i386.deb: OK<br>
<br>
</p>
</blockquote>
</body>
</html>