Created attachment 912426 [details] output of signtool command in windows 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
(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 I would like to move this bug to RHEL7 for a fix.
block on windows7-64 works fine
In the future, taking a fedora bug and moving it to RHEL is not recommended: - We want to track this bug in both places that it's broken - The reporter and potentially other non RH people now have full access to a RHEL bug so have to be careful when talking about internal bits. In the future, please clone the issue to RHEL. I'll clone this back to fedora.
(In reply to Cole Robinson from comment #9) > In the future, taking a fedora bug and moving it to RHEL is not recommended: > > - We want to track this bug in both places that it's broken > - The reporter and potentially other non RH people now have full access to a > RHEL bug so have to be careful when talking about internal bits. > > In the future, please clone the issue to RHEL. I'll clone this back to > fedora. OK BTW this bug and 1110129 are dup
After further research ,this is a test scenario covered in test plan already and we have existing bug to track it https://bugzilla.redhat.com/show_bug.cgi?id=1110129 I shouldn't move this bug to RHEL component .. Mike
Okay, duping to 1110129 as according to comment #11, if that's wrong please reopen *** This bug has been marked as a duplicate of bug 1110129 ***