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.
DescriptionCameron Meadors
2011-11-16 16:37:29 UTC
Description of problem:
I downloaded qxl_w7_x86.zip from the -13 build of qxl-win. I updated the driver on my win7 32bit guest by pointed devicemanager to the inf file from the zip. Driver information still says 6.0.0.12 from Oct 5 and it is not signed.
Version-Release number of selected component (if applicable):
qxl-win-0.1-13
How reproducible:
Only tried it on one guest so far
Steps to Reproduce:
1. Download zip
2. Update driver from device manager
3. reboot
Actual results:
driver installed is unsigned
Expected results:
driver installed is signed
Additional info:
I'm not sure what the problem is:
the version is 6.0.0.12 - that's correct. The qxl-win-0.1-12 is the unsigned driver, signed by a redhat certificate:
-rwxr-xr-x. 1 alon alon 6833 Nov 7 10:31 qxl-win-0.1-12/w7/x86/qxl.cat
while qxl-win-0.1-13 contains the new cat file, that's the only difference between the two packages. The cat file contains the signatures, not the executables (qxl.sys and qxldd.dll):
-rw-r--r--. 1 alon alon 7913 Nov 10 12:37 qxl-win-0.1-13/w7/x86/qxl.cat
Right clicking the cat file in qxl-win-0.1-13 shows it is signed by a Microsoft certificate. Haven't yet installed it, it requires removing the current 0.1-12 driver, since they are the same (and so no upgrade).
Alon
(In reply to comment #2)
> Tried win7 64 bit with qxl_w7_x64.zip with the same results: driver is not
> signed.
I can reproduce. I really have no idea yet how the cat file is related exactly, I'm trying to figure this out. Will update.
Alon
Tracked this to a git setting in brew builds - autocrlf and safecrlf are on.
The end result was that the line endings of the inf file were changed:
qxl-win/brew/qxl-win-0.1-13/w7/x86/qxl.inf: ASCII English text, with CRLF line terminators
But the original, and signed in the cat file, so must not be changed one, is:
signed_win_drivers_6/qxl/w7/x86/qxl.inf: ASCII English text
So a brew RFE is being created which this bug will depend on, but meanwhile you can take the zip files in qxl-win-0.1-13 and add the inf file from qxl-win-0.1-12, and it will install without warnings.
Alon
Hi Cameron,
did a new build using dos2unix, brew still broken - can you test, it's called qxl-win-0.1-14 (surprise :)
Alon
p.s. the way the bug title is set I can't possibly fix this ever - but I assume that's not what you want, just a whql signed version of qxl-win-0.1-12, which qxl-win-0.1-14 is.