FTDI: Difference between revisions
m →Injecting Garbage Data (2016): added a space between Data and (2016) |
altered description and added a short description to the 1st paragraph. linked 'Windows' to the windows article on the wiki. |
||
| Line 5: | Line 5: | ||
|Type=Private | |Type=Private | ||
|Website=https://ftdichip.com/ | |Website=https://ftdichip.com/ | ||
|Description= | |Description=FTDI is a Scottish semiconductor company. | ||
}} | }} | ||
Future Technology Devices International Limited is a Scottish fabless semiconductor company. It has facilities Singapore, Oregon and China in addition to the UK.<ref>{{Cite web |title=Corporate Profile |url=https://ftdichip.com/corporate-profile/ |url-status=live |website=ftdi |archive-url=https://web.archive.org/web/20260621171519/https://ftdichip.com/corporate-profile/?__cf_chl_rt_tk=xx_mHq514bihUr.xCKRLH9bmtwvYu73_hY1atdHbGsQ-1782062119-1.0.1.1-WQOwQlZgtyn1B0PmjBZ6oqeoSu1iN0Jo0I3rCR5t8XA |archive-date=21 Jun 2026}}</ref>It specializes in USB and manufactures various integrated circuits ranging from USB Host Controllers to USB to UART converter chips, multipurpose converters with support for FIFO, JTAG, SPI etc in addition to UART. It also manufactures various cables and adapters, mainly for USB, RS232, UART and RS422.<ref>{{Cite web |title=Products |url=https://ftdichip.com/product-category/products/ |url-status=live |website=ftdi |archive-url=https://web.archive.org/web/20260621174420/https://ftdichip.com/product-category/products/?__cf_chl_rt_tk=Jx8.q6zAQBniNudpDDnV_jub4em4fnCp2__nEfG8Lnk-1782063860-1.0.1.1-OnsX3G.YXR45KXaY7pY6UbubVffzAUjkwKwz.i4f8v4 |archive-date=21 Jun 2026}}</ref> | |||
==Consumer-impact summary== | ==Consumer-impact summary== | ||
FTDI has employed aggressive measures such as bricking or injecting garbage data via undocumented features into users' chips that were determined to be clones or counterfeits by FTDI's drivers. This led to backlash and [[Microsoft]] removing FTDI's driver from Windows. Eventually, FTDI backed down.<ref name="brick">{{Cite web |date=25 Oct 2014 |first=James |last=Sanders |title=FTDI uses Windows Update to disable devices using counterfeit chips |website=techrepublic |url=https://www.techrepublic.com/article/ftdi-abuses-windows-update-pushing-driver-that-breaks-counterfeit-chips/ |url-status=usurped |archive-url=https://web.archive.org/web/20230307174533/https://www.techrepublic.com/article/ftdi-abuses-windows-update-pushing-driver-that-breaks-counterfeit-chips/ |archive-date=7 Mar 2023 |access-date=21 Jun 2026}}</ref><ref name="inject">{{Cite web |date=1 Feb 2016 |first=Brian |last=Benchoff |title=FTDI Drivers Break Fake Chips, Again |url=https://hackaday.com/2016/02/01/ftdi-drivers-break-fake-chips-again/ |url-status=live |website=Hackaday |archive-url=https://web.archive.org/web/20260621180710/https://hackaday.com/2016/02/01/ftdi-drivers-break-fake-chips-again/ |archive-date=21 Jun 2026}}</ref> | FTDI has employed aggressive measures such as bricking or injecting garbage data via undocumented features into users' chips that were determined to be clones or counterfeits by FTDI's drivers. This led to backlash and [[Microsoft]] removing FTDI's driver from Windows. Eventually, FTDI backed down.<ref name="brick">{{Cite web |date=25 Oct 2014 |first=James |last=Sanders |title=FTDI uses [[Microsoft Windows]] Update to disable devices using counterfeit chips |website=techrepublic |url=https://www.techrepublic.com/article/ftdi-abuses-windows-update-pushing-driver-that-breaks-counterfeit-chips/ |url-status=usurped |archive-url=https://web.archive.org/web/20230307174533/https://www.techrepublic.com/article/ftdi-abuses-windows-update-pushing-driver-that-breaks-counterfeit-chips/ |archive-date=7 Mar 2023 |access-date=21 Jun 2026}}</ref><ref name="inject">{{Cite web |date=1 Feb 2016 |first=Brian |last=Benchoff |title=FTDI Drivers Break Fake Chips, Again |url=https://hackaday.com/2016/02/01/ftdi-drivers-break-fake-chips-again/ |url-status=live |website=Hackaday |archive-url=https://web.archive.org/web/20260621180710/https://hackaday.com/2016/02/01/ftdi-drivers-break-fake-chips-again/ |archive-date=21 Jun 2026}}</ref> | ||
==Incidents== | ==Incidents== | ||
===Drivers Bricking Chips (2014)=== | ===Drivers Bricking Chips (2014)=== | ||
FTDI pushed an automated driver update via 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" 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]] 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" 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> | 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> | 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> | ||