FTDI: Difference between revisions - Consumer Rights Wiki

Line 15:

===Drivers Bricking Chips (2014)===

FTDI pushed an automated driver update via [[Microsoft Windows]] Update that targeted the FT232 chipset. The update bricked chips it detected to be counterfeits or clones by setting their PID to 0. Because the chip itself is not something users usually purchase by itself, but rather buy devices which include it, many users were not aware their chip was counterfeit, yet were still affected. The update's INF file included a disclaimer which mentioned that the driver "MAY IRRETRIEVABLY DAMAGE THAT COMPONENT" referring to non genuine components. However, since it was installed through Windows Update, users were not able to see this file.

FTDI pushed an automated driver update via [[Microsoft Windows|Windows]] Update that targeted the FT232 chipset. The update bricked chips it detected to be counterfeits or clones by setting their PID to 0. Because the chip itself is not something users usually purchase by itself, but rather buy devices which include it, many users were not aware their chip was counterfeit, yet were still affected. The update's INF file included a disclaimer which mentioned that the driver "MAY IRRETRIEVABLY DAMAGE THAT COMPONENT" referring to non genuine components. However, since it was installed through Windows Update, users were not able to see this file.

Moreover even standalone chips, are reportedly difficult to tell apart from counterfeits and ensure you're getting genuine chips.<ref name="inject"></ref>

This sets a dangerous precedent, because if users start avoiding updates due to mistrust, they may end up vulnerable because of missed security updates.<ref name="brick"></ref>

@@ Line 15: / Line 15: @@
 ===Drivers Bricking Chips (2014)===
-FTDI pushed an automated driver update via [[Microsoft Windows]] Update that targeted the FT232 chipset. The update bricked chips it detected to be counterfeits or clones by setting their PID to 0. Because the chip itself is not something users usually purchase by itself, but rather buy devices which include it, many users were not aware their chip was counterfeit, yet were still affected. The update's INF file included a disclaimer which mentioned that the driver "MAY IRRETRIEVABLY DAMAGE THAT COMPONENT" referring to non genuine components. However, since it was installed through Windows Update, users were not able to see this file.
+FTDI pushed an automated driver update via [[Microsoft Windows|Windows]] Update that targeted the FT232 chipset. The update bricked chips it detected to be counterfeits or clones by setting their PID to 0. Because the chip itself is not something users usually purchase by itself, but rather buy devices which include it, many users were not aware their chip was counterfeit, yet were still affected. The update's INF file included a disclaimer which mentioned that the driver "MAY IRRETRIEVABLY DAMAGE THAT COMPONENT" referring to non genuine components. However, since it was installed through Windows Update, users were not able to see this file.
 Moreover even standalone chips, are reportedly difficult to tell apart from counterfeits and ensure you're getting genuine chips.<ref name="inject"></ref>
 This sets a dangerous precedent, because if users start avoiding updates due to mistrust, they may end up vulnerable because of missed security updates.<ref name="brick"></ref>