libwdi
badusb2-mitm-poc
libwdi | badusb2-mitm-poc | |
---|---|---|
7 | 1 | |
1,737 | 275 | |
- | - | |
0.0 | 0.0 | |
2 months ago | almost 8 years ago | |
C | Python | |
GNU General Public License v3.0 only | GNU General Public License v3.0 only |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
libwdi
-
Porting USB applications to the web. Part 1: libusb
They probably use WCID, which is a mechanism for devices to tell Windows that they are compatible with the generic WinUSB driver. Zadig is useful for older versions of windows, non-WCID devices, and when you want to override that auto-specified driver.
Here's more information from the author of Zadig: https://github.com/pbatard/libwdi/wiki/WCID-Devices
-
I need help with my saber files uploading to my saber
If you do that'll bring you here where you'll find everything you ever wanted to know about WCID.
- SDR Software for Windows Surface RT for ARM 32 bit
- Can’t get avrdude to work
-
Bluetooth Passthrough: Easier libusbK driver swapping with a config file and batch script.
Using this config files from zadig's github page, it (in my case) got all the correct settings from the start and all I need to do is click replace driver. Place the zadig.ini files in the same directory as your zadig.exe. You might have to choose the correct device.
-
Convert old USB1.0 bulk to serial.
USB descriptors are supported only up to 8.1 according to your link. And libwdi/zadig is useful links for me, thank you very much! I'll be used ones in my other projects. But I don't need to new USB driver in Windows due to I'll get much more problems with put all together in LabView. I want to use standard WIndows USB-Serial that always present and directly supported via VISA. The NI-VISA isn't using specific protocols for USB. The VISA is just an intermediate level for most of the serial protocols in the NI ecosystem. I'm operating low-level USB packets, commands, responses in the same manner as in C for example but from LabView. But I have to generate the specific INF file which needs for recognition of VISA for each one of the specific instances with a unique USB PID/UID. The problem is mandatory signing such INF files in Windows10 and I'm looking for any way to avoid this.
badusb2-mitm-poc
-
Convert old USB1.0 bulk to serial.
Well you could try performing some man in the middle but apart from that I think your best choice is to use some sort of pre built USB stack or maybe an FTDI with custom hardware.
What are some alternatives?
uhubctl - uhubctl - USB hub per-port power control
UsbDk - Usb Drivers Development Kit for Windows
libusb - A cross-platform library to access USB devices
SDRPlusPlus - Cross-Platform SDR Software
PS5-Camera-Firmware-Loader - A cross-platform utility for loading custom firmware onto the PlayStation 5 camera, written in Rust
OctoPrint-FirmwareUpdater - OctoPrint plugin for flashing pre-compiled firmware images to a 3D printer.
reactos - A free Windows-compatible Operating System
uMTP-Responder - Lightweight USB Media Transfer Protocol (MTP) responder daemon for GNU/Linux
webusb - Connecting hardware to the web.
file-system-access - Expose the file system on the user’s device, so Web apps can interoperate with the user’s native applications.
standards-positions
d2x-cios - A custom IOS for the Wii and Wii-U console, i.e. an IOS modified to add some new features not available in the official IOS.