Red Hat Bugzilla – Bug 833659
qxl driver in virtio-win-1.5.2 is not digital signed
Last modified: 2013-02-21 05:39:00 EST
Description of problem:
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.install win7 32 bit guests w/ -spice port=5910,disable-ticketing -vga qxl
2.install qxl driver in virtio-win-1.5.2.vfd
The driver is not digital signed
The driver *must* digital signed
Tried w/ virtio-win-1.5.1 ,seems did not hit this issue ,I think Bug 823482 cause regression
Can you confirm whether the driver is signed or merely not matching the signature in the .cat file? My fear is that adding CRLF characters to the .inf file caused the signaures to no longer match for QXL.
(In reply to comment #4)
> Can you confirm whether the driver is signed or merely not matching the
> signature in the .cat file? My fear is that adding CRLF characters to the
> .inf file caused the signaures to no longer match for QXL.
I did not get it .Do you mean I need to use signtool.exe to check whether sys is matching the .cat file ?
I just try to install qxl driver in device manager ,it prompts the driver is not digital signed .and after installation ,the manufacturer is redhat inc .
Actually performing a "dos2unix qxl.inf" it will then load.
Ok, I can put together another build that has that. We'll have to be careful in the future that what we submit to Microsoft has the correct CRLF terminators.
Before proceeding though I'd like an answer to this bug:
It proposes removing QXL drivers from virtio-win entirely.
(In reply to comment #8)
> Ok, I can put together another build that has that. We'll have to be careful
> in the future that what we submit to Microsoft has the correct CRLF
Ok. We should also not use autocrlf in the git repository to which the signed files are commited. Signed files cannot be changed, as this bug demonstrates.
According to comment #18 ,move status to verified .
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.