Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
First Last Prev Next    This bug is not in your last search results.
Bug 1434314 - USB devices stop working when UsbDk installed in Win10 with secure boot
USB devices stop working when UsbDk installed in Win10 with secure boot
Status: CLOSED ERRATA
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: spice-usbdk-win (Show other bugs)
unspecified
Unspecified Windows
unspecified Severity unspecified
: ovirt-4.2.0
: ---
Assigned To: ybendito
SPICE QE bug list
: Reopened
Depends On:
Blocks:
  Show dependency tree / graph
 
Reported: 2017-03-21 05:16 EDT by ybendito
Modified: 2018-05-23 13:22 EDT (History)
9 users (show)

See Also:
Fixed In Version: v1.0.19
Doc Type: No Doc Update
Doc Text:
undefined
Story Points: ---
Clone Of:
Environment:
Last Closed: 2018-05-15 14:02:00 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: Spice
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:1543 None None None 2018-05-15 14:03 EDT

  None (edit)
Description ybendito 2017-03-21 05:16:06 EDT 
Description of problem:

UsbDk driver currectly signed by RedHat certificate only and does not function on Win10 with secure boot enabled. After installation of UsbDk on machine with secure boot connected USB devices stop working

Version-Release number of selected component (if applicable):

spice-usbdk-win-1.0-17

How reproducible:

100%

Steps to Reproduce:
1. Install UsbDk on Win10 machine with secure boot enabled
2. 
3.

Actual results:

USB devices do not work

Expected results:

USB devices work as expected


Additional info:
Attestation signing by Microsoft required for UsbDk.sys driver
Comment 2 Dmitry Fleytman 2017-04-20 04:09:36 EDT 
Fixed in v1.0.19 by adding attestation signature to Win10 binaries.
Comment 3 ybendito 2017-09-13 09:20:51 EDT 
Closing based on comment #2
Comment 4 ybendito 2017-10-16 10:31:36 EDT 
Moving to "Modified" as at the moment current release is 1.0.15. The problem fixed in 1.0.19
Comment 5 ybendito 2017-10-19 07:18:13 EDT 
Build of UsbDk 1.0.19
https://brewweb.engineering.redhat.com/brew/buildinfo?buildID=551835
Comment 8 Sandro Bonazzola 2017-12-12 08:50:24 EST 
This bug is in modified status but no patches are attached to it.
Can you please check if the fix is included in latest build and move to QE if so?
Comment 9 ybendito 2017-12-13 03:34:36 EST 
(In reply to Sandro Bonazzola from comment #8)
> This bug is in modified status but no patches are attached to it.
> Can you please check if the fix is included in latest build and move to QE
> if so?

USBDK modification are maintained in https://github.com/daynix/UsbDk
Testing of UsbDk 0.19 was done. Radek / Tomas, can you please update this BZ?
Comment 10 Radek Duda 2017-12-14 05:50:07 EST 
I performed test with spice-usbdk-win-1.0-17 on Win10 client with secure boot enabled. No connected USB device worked.

Then I installed spice-usbdk-win-1.0-19 all connected USB dwevices worked as expected. After connecting to rhel7.5 guest with remote-viewer (from virt-viewer-x64-2.0.msi installer) I was able to redirect USB flash disk to guest. So the fix must be included in spice-usbdk-win-1.0-19
Comment 17 errata-xmlrpc 2018-05-15 14:02:00 EDT 
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.

https://access.redhat.com/errata/RHBA-2018:1543
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.