You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Somewhat of a continuation of #876, now that WSL 2 has support for USB (given the WSL kernel is compiled with USB options enabled) a device can be connected using USBIP, or similar software. Of course, checkra1n does not work because, like a VM, the hypervisor or virtualization software still has to use Windows drivers to access the USB device. Running the checkm8 exploit in this environment does not work either, producing:
*** checkm8 exploit by axi0mX ***
****** stage 1, heap grooming
Found: CPID:8960 CPRV:11 CPFM:03 SCEP:01 BDID:00 ECID:0000020E8E49A434 IBFL:1C SRTG:[iBoot-1704.10]
ctrl transfer ERROR: 2 3 USBError(32, 'Pipe error')
# An endless stream of identical time outs, only showing one
ctrl transfer ERROR: 128 6 USBError(110, 'Operation timed out')
Performing USB port reset.
Caught exception during port reset; should still work.
****** stage 2, usb setup, send 0x800 of 'A', sends no data
ERROR: No Apple device in DFU Mode 0x1227 detected after 5.00 second timeout. Exiting.
Other people have reported success running a fork of the exploit with libusb-win32 drivers installed and controlling the device while in DFU mode. I'm probably misunderstanding the functionality of libusb-win32 (I assume it is used instead of the Windows drivers, correct me if I'm wrong), but if this would give checkra1n the necessary control over the USB stack, how much modification would be required to make checkra1n work? Is it worth considering, is it easier to just make custom drivers for windows, or is this not possible at all? Given the requirements to run WSL with a custom kernel and to enable USB access, this would be more difficult than just booting Linux from a USB stick, but it'd be nice to know if it's possible.
The text was updated successfully, but these errors were encountered:
I had a look around regarding WSL2 and USB, and ended up here: microsoft/WSL#5158
Basically there is no USB passthrough, and tunneling USB to the Windows API leaves us exactly where we started.
So, gonna mark this issue as invalid - good idea, but unfortunately based on wrong assumptions.
Somewhat of a continuation of #876, now that WSL 2 has support for USB (given the WSL kernel is compiled with USB options enabled) a device can be connected using USBIP, or similar software. Of course, checkra1n does not work because, like a VM, the hypervisor or virtualization software still has to use Windows drivers to access the USB device. Running the checkm8 exploit in this environment does not work either, producing:
Other people have reported success running a fork of the exploit with libusb-win32 drivers installed and controlling the device while in DFU mode. I'm probably misunderstanding the functionality of libusb-win32 (I assume it is used instead of the Windows drivers, correct me if I'm wrong), but if this would give checkra1n the necessary control over the USB stack, how much modification would be required to make checkra1n work? Is it worth considering, is it easier to just make custom drivers for windows, or is this not possible at all? Given the requirements to run WSL with a custom kernel and to enable USB access, this would be more difficult than just booting Linux from a USB stick, but it'd be nice to know if it's possible.
The text was updated successfully, but these errors were encountered: