Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionNikos Skalkotos
2014-06-26 13:42:24 UTC
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.
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