10 ms·
Microsoft should revoke the driver's signature via their next CRL update, so that it refuses to install (effectively making the drivers unsigned). It is acting
by Someone1234 12y ago
Microsoft should revoke the driver's signature via their next CRL update, so that it refuses to install (effectively making the drivers unsigned). It is acting maliciously and will break consumer's hardware, even hardware which doesn't contain any FTDI chips.
If FTDI have an issue with a company ripping off their IP then go sue that company. But what they're doing is catching consumers in the firing line, who will wind up with multiple dead USB devices. There's no reasonable way a consumer can know they are buying something with a fake chip and this could kill devices years old, which will be outside of warranty.
I am totally serious that Microsoft should step in. FTDI's driver is so defective that it is literally killing hardware, if they won't step in for this then what will they step in for?
- 0x0 12y agoIsn't the WHQL process supposed to vet for malware like this?
- Someone1234 12y agoThey may not be WHQL certified, per Wikipedia: > A company can choose to sign their own drivers rather than go through the WHQL testing process. These drivers would not qualify for the "Certified for Windows" logos, but they would install on 64-bit versions of Windows and install without a warning message on 32-bit versions of Windows Vista or Windows 7. However, it will not install without a warning message on Windows XP. If they are, I don't know enough about how rigorous Microsoft's certification process is now to comment. It used to be just looking for things that would cause kernel instability but it seems the standards have increase a lot since its exception.
- 0x0 12y agoBut they are pushed through Windows Update? Doesn't everything there have to be WHQL?
- rwmj 12y agoCorrect. To use the non-MSFT signed approach, the driver has to add the cert to the registry beforehand somehow (eg. using certutil -addstore -f TrustedPublisher), which obviously rules out a straight install using Windows Update.
- overgryphon 12y agoI would be surprised if WHQL tested drivers on counterfeit hardware.
- lotu 12y agoI'm sure you realize that the counterfeiters operate in such a fashion and in regions of the world that make sueing them impossible. Which suck because it means FTDI really has no options to enforce their IP rights that don't hurt consumers.
- scotty79 12y ago... thus they have moral right and obligation to damage the hardware belonging to other people because some other people don't recognize their "IP rights"? What's you point here?
- swamp40 12y agoNobody would fault FTDI for releasing new drivers that don't work with counterfeit parts. That alone would cause enough inconvenience to manufacturers to make sure they use legitimate parts. It's the (unethical) bricking of the parts that has everybody up in arms.
- tptacek 12y agoTangentially: people totally would fault FTDI for releasing drivers that don't work with counterfeit parts. See: Apple detecting and rejecting counterfeit iPhone cables.
- wolfgke 12y agoThe correct way is to detect counterfeit parts, display a huge warning and let the customer continue on their own risk. A similar process is used by the Linux kernel developers for non-opensource kernel modules: If you load them, the kernel becomes "tainted" and you won't get any support from the kernel developers if something goes wrong.
- cnvogel 12y agoYes, this would be smart. Probably just putting a message with priority "Error" in the windows event log would be enough to warn computer-literate users.
- geographomics 12y agoCan we be sure that FTDI has programmed their driver with malicious intent? It may be that this an accidental side-effect of using counterfeit hardware with a genuine driver. Without access to the source code or a well-reversed disassembly of the FTDI driver, and a good grasp of the logic used in the counterfeit chip, one cannot be certain about this. And surely not to the extent of urging Microsoft to revoke driver signatures.
- glibgil 12y agoI don't know if you can be sure, but almost certainly MS can.
- ryandrake 12y agoIt shouldn't matter what their intent was. If the new version of a network driver accidentally started DDOSing servers, it should also be pulled, regardless of whether the vendor did it on purpose.
- tlrobinson 12y agoIf the counterfeit FTDI chips are using FTDI's registered USB vendor ID (I assume they are, otherwise the driver wouldn't recognize them?) I think the blame falls solely on the counterfeit chip makers.
- wtallis 12y agoWhy? The counterfeits aren't seeking USB compliance certification, they're just trying to provide 100% compatibility. Are you saying that reverse engineering and spoofing for the sake of compatibility is wrong? Or do you think that USB vendor IDs are covered by some trademark?
- deelowe 12y agoSeems like there's a few people who don't seem to understand the difference between copyright, trademark, criminal and civil law (op above you included). The only law broken by the counterfeiters is trademark violation for printing the FTDI logo on their chips. That's it! Everything else they did was legal. Otherwise, Intel and AMD would be bricking CPUs right now. Reverse engineering is legal. Emulation is legal. Creating hardware that's compatible with another vendor's software is legal. Flashing your hardware with another vendors firmware is legal. Modifying hardware you purchased from a vendor is legal. Modifying software you purchased from a vendor is legal. etc... etc...