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.
DescriptionYvugenfi@redhat.com
2023-01-30 09:57:05 UTC
Description of problem:
When submitting virtio-win-prewhql driver for attestation signing on the MS Hardware partners portal, the attestation singing fails during the validation stage with the following error:
"Error 1303 in viorng.inf, line 102 : Found legacy AddReg operation defining co-installers (CoInstallers32).
Failed INF validation. INF did not pass Desktop validation (InfVerif /k).
"
Version-Release number of selected component (if applicable):
The test was done with virtio-win-prewhql-0.1-232, but this is MS portal feature - so it will fail with all our previous versions.
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
Currently, our cab file (the archive with driver binaries) has all the drivers together. Therefore, attestation signing for all the drivers will fail, although the problem is only in virtio-rng driver.
The keyword relates to the usage of the co-installer in virio-rng driver used to register cryptographic provided in Windows.
Hi Yan，
Do you think running a window guest whql test to verify the bz is enough at this moment? Or any other suggestions?
Thanks
Menghuan
Comment 5Yvugenfi@redhat.com
2023-06-25 06:15:02 UTC
(In reply to menli from comment #4)
> Hi Yan，
>
> Do you think running a window guest whql test to verify the bz is enough at
> this moment? Or any other suggestions?
>
>
> Thanks
> Menghuan
Hi Menghuan,
I am already tested that attestation signing works.
Submitting virtio-rng for WHQL certification also a good idea.
Other than that, I don't think something is needed.
Best regards,
Yan.
Thanks a lot Yan.
Based on comment5 and I tested a win2016 rng whql with build 238, the result is pass, so change the status to verified.
Comment 7Yvugenfi@redhat.com
2023-06-26 06:30:21 UTC
(In reply to menli from comment #6)
> Thanks a lot Yan.
>
> Based on comment5 and I tested a win2016 rng whql with build 238, the result
> is pass, so change the status to verified.
Sorry Menghuan,
Can you test that the submission of the driver to MS Hardware portal succeeded as well?
Thanks,
Yan.
(In reply to Yvugenfi from comment #7)
> (In reply to menli from comment #6)
> > Thanks a lot Yan.
> >
> > Based on comment5 and I tested a win2016 rng whql with build 238, the result
> > is pass, so change the status to verified.
>
> Sorry Menghuan,
> Can you test that the submission of the driver to MS Hardware portal
> succeeded as well?
Yes, my fault, I noticed you already tested that attestation signing works and I ignored to check it on my side.
Will work on it, change the bz to ON_QA first.
> Thanks,
> Yan.