+++ This bug was initially created as a clone of Bug #1113600 +++ Description of problem: In the Windows driver package you offer under http://alt.fedoraproject.org/pub/alt/virtio-win/latest/images/ viostor.sys and vioscsi.sys files for Win8\AMD64 are not properly signed. There is no way to automatically install those drivers. You always get security warnings. Take a look at the attached file. I can verify viostor.sys for Win7\AMD64 or Win8\x86 with signtool but not viostor.sys for Win8\amd64. viostor.inf and vioscsi.inf as well as any other .inf and .sys file can be verified just fine. The problem is only in viostor.sys and vioscsi.sys This problem affects virtio-win-0.1-74.iso as well as virtio-win-0.1-81.iso This problem is very similar to this one: https://bugzilla.redhat.com/show_bug.cgi?id=1012429 --- Additional comment from Ronen Hod on 2014-06-26 10:45:17 EDT --- Seems like build81 is not signed. Cole, is there a way to replace only this specific driver? --- Additional comment from Mike Cao on 2014-06-26 11:01:38 EDT --- I found some driver is not signed property by redhat certificate .Now I am trying to figure out which version the issue introduced --- Additional comment from Cole Robinson on 2014-06-26 11:11:23 EDT --- (In reply to Ronen Hod from comment #1) > Seems like build81 is not signed. > Cole, is there a way to replace only this specific driver? Yeah I can probably hack it together. But what build should I use? I'm interested to see what Mike finds, also I wonder about the mentioned RHEL bug --- Additional comment from Vadim Rozenfeld on 2014-06-27 05:56:03 EDT --- (In reply to Cole Robinson from comment #3) > (In reply to Ronen Hod from comment #1) > > Seems like build81 is not signed. > > Cole, is there a way to replace only this specific driver? > > Yeah I can probably hack it together. But what build should I use? I'm > interested to see what Mike finds, also I wonder about the mentioned RHEL bug We were trying to stabilize VS2013 build system in builds 81 and 82. Build 81 was partially broken, build 82 was much better. --- Additional comment from Mike Cao on 2014-07-03 00:07:17 EDT --- (In reply to Vadim Rozenfeld from comment #4) I can reproduce this issue on RHEL8-64 w/ virito-win-prewhql-86 block/scsi Based on above I think it is a driver bug 2 ways to reproduce it : 1)#certutil -addstore -f TrustedPublisher C:\autotest\redhat.cer #pnputil -i -a XXX.inf Actual Results: driver can not be installed smoothly 2)install the driver manually ,,click "driver details" in driver properties in device manager Actual Results : Digital Signer part shows Not digitally signed Expect Results : It should show "Red Hat Inc." Besides above matrix all drivers on windows 2008 is not digital signed as well
Vadim, just to clarify: given that this is reproducible with RHEL as well, I take that to mean that there's no internal virtio-win build that has this fix? If so I'll just wait for a fixed build and a ping to update the fedora drivers
(In reply to Cole Robinson from comment #1) > Vadim, just to clarify: given that this is reproducible with RHEL as well, I > take that to mean that there's no internal virtio-win build that has this > fix? If so I'll just wait for a fixed build and a ping to update the fedora > drivers Thanks Cole, Yes, it's it's a common problem reproducible on both - Fedora and RHEL. I'll try to fix it asap. Vadim.
*** Bug 1126912 has been marked as a duplicate of this bug. ***
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle. Changing version to '22'. More information and reason for this action is here: https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22
This should be fixed with the latest public ISOs