News for hackers. Stuff that matters.
Re:Porting USB applications to the web. Part 1: libusb by tehbeard on Thursday January 20, 2022 @12:55PM (#30012224)
The OSS community has an easier time supporting it than when there's only a crappy windows binary blob?
Re:Porting USB applications to the web. Part 1: libusb by mschuster91 on Thursday January 20, 2022 @12:59PM (#30012302)
A crappy WebASM blob or heavily obfuscated JS blob is similar to a crappy windows binary blob, though.
Re:Porting USB applications to the web. Part 1: libusb by kitsunesoba on Thursday January 20, 2022 @01:47PM (#30012910)
Probably worse, because at least there’s well established tooling for reverse engineering Windows binary drivers, allowing for someone to eventually write FOSS drivers.
Re:Porting USB applications to the web. Part 1: libusb by RReverser on Thursday January 20, 2022 @01:56PM (#30013030)
I don't think it's worse because: 1) Wasm was designed to be easily decompilable / convertible to a text assembly representation by design, whereas for other platforms it requires fairly sophisticated disassemblers 2) Wasm can interact with the outside world (any I/O) only via explicitly defined import points, which are easy to intercept and/or replicate even if you don't know what's inside the binary itself.