Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RedHad signature in https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/stable-virtio/virtio-win.iso is expired #57

Open
dmachaj opened this issue Mar 7, 2022 · 2 comments

Comments

@dmachaj
Copy link

dmachaj commented Mar 7, 2022

The direct links to both stable and latest point to virtio-win-0.1.215.iso at this time. The RedHat signature used to sign the drivers in that image expired on 1/25/2022. As a result I am unable to get the certificate installed as a root Trusted Publisher on a Windows client because it is rejected for expiry reasons.

Is there a new release available with a non-expired signature? Thank you.

@vrozenfe
Copy link
Collaborator

vrozenfe commented Mar 7, 2022

@dmachaj
You are right. Unfortunately, the RH signature is expired and we can not use it anymore for the driver signing purpose.
The good thing is that this problem should affect Win8/Win8.1/WS2012(R2) drivers only. All Win10+ drivers should be
attestation signed, which lets them to be installed even on UEFI platforms without any problem.

Currently we are planning to release test-signed drivers for Win8+ platforms and attestation signed drivers for Win10+
We will try to improve this situation as much as possible.

Best,
Vadim.

@dmachaj
Copy link
Author

dmachaj commented Mar 7, 2022

My immediate problem is that installing the drivers and integration tools will show the "Do you trust this publisher?" UI for Red Hat, even when running the installers in /quiet mode. That UI prevents them from installing from the command-line which is what I need.

Importing the certificate to the machine-scope TrustedPublishers list solves that problem. Because the certificate is expired the PowerShell Import-Certificate cmdlet will reject the certificate. However, certutil -addstore -f "TrustedPublisher" certificate.cer does not reject it, allowing the import to succeed.

Long story short - I have a viable workaround to accomplish my goal. It would be easier if the certificate was not expired, but it is not a total blocker.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants