11 ms·
FTDI removes counterfeit-bricking driver from Windows Update
- Someone1234 12y agoGood for them. I mean that. If they want to redesign their driver so it fails to work with non-genuine FTDI chips, go for it. Nobody will judge them. Heck if they want to show a message that informs the user they're using a fake, that's fine too. I think most people seemed to agree that bricking fakes was too far (and also could be considered illegal in some countries/areas). It also negatively impacted innocent parties (e.g. consumers who purchased generic goods, which happened to contain fake FTDI chips). Plus if you're in the business of bricking things, it is too easy to make a mistake and brick your OWN stuff. I mean software bugs are common, and it is best to stay away from a set of them which indefinitely makes chips malfunction. PS - I wonder if Microsoft got in touch and essentially told them "we will pull your driver from Windows Update unless you do it first. It won't return until it is fixed." We know from the previous thread that Microsoft was looking into this.
- blatherard 12y agoAccording to the update at the end of this ars technica article (http://arstechnica.com/information-technology/2014/10/windows-update-drivers-bricking-usb-serial-chips-beloved-of-hardware-hackers/ http://arstechnica.com/information-technology/2014/10/window...) which indicates Microsoft involvement: "Microsoft has given us a statement: Yesterday FTDI removed two driver versions from Windows Update. Our engineering team is engaging with FTDI to prevent these problems with their future driver updates via Windows Update."
- bri3d 12y agoWhat I don't understand is why they don't make the messaging more clear. In their pre-bricking drivers, FDTI caused the counterfeits to fail in confusing and counterintuitive ways, rather than just telling the user that the chip is fake. As a user, if my device stops working randomly, my first thought is certainly not "there was a counterfeit chip in the supply chain for this hardware and the drivers must be rejecting it!" A little bit more user notification around "you have a counterfeit FTDI" or, even better, a tool to find out if your FTDI is fake would be a lot better than "oh, you can tell if the chip is fake because it will only work properly with drivers before 2.08.14, otherwise it will randomly crash!" Prolific do the same thing, but their drivers at least fail to start with a common error code which is easy to Google.
- fixermark 12y ago""" As a user, if my device stops working randomly, my first thought is certainly not "there was a counterfeit chip in the supply chain for this hardware and the drivers must be rejecting it!" """ Yep. Believing the consumer cares about your product as much as you do is a line of thinking that's easy for engineers to fall into when their lives and livelihoods depend on the product. It's why smart companies employ someone with the capacity to sit in a more objective position to evaluate the market and public perception.
- DigitalJack 12y agoI don't think that is very straight forward. It's easy to know how your device will operate in various conditions. counterfeits can fail in a million unpredictable ways.
- bri3d 12y agoFTDI have code which can tell with some high degree of certainty (at least enough that they trusted it to brick devices!) that a chip is fake. They've used this code to make counterfeits intentionally unpredictable in the last few versions of their driver, rather than simply stopping the device with an error code (like Prolific do) or notifying the user or client library (like all of these vendors should be doing). So, for FTDI at least, it should be very straightforward to do something other than intentionally making fakes of their devices behave unpredictably.
- robostac 12y agoThey might not have the ability to do that - I could quite easily see the bit of code that can tell if its fake being the same code that bricks the device. Maybe all the real ftdi chips will reject a PID of 0 (as it's invalid), while the fake ones accept it.
- bri3d 12y agoTheir drivers prior to the bricking drivers (everything after 2.08.14) caused the fake devices to fail, where previously they hadn't. Whether or not that behavior was intentional, there is clearly an exploitable property of the fake devices which can determine that they are fake without bricking the device. FTDI should use it rather than playing these games. Their reaction to the discovery of the bricking issue on Twitter and elsewhere yesterday strongly suggests that it was anything but an "oh shit, our driver bricks some of those crappy fakes" moment.
- wpietri 12y ago> and also could be considered illegal in some countries/areas Is there some country where it's legal to break somebody's property because you have a beef with a third party? Certainly in the US if somebody produced a virus that did this nobody would even blink at a federal prosecution. That FTDI slipped a bit of text into a document nobody reads doesn't strike me as relevant. If a piece of malware also popped up an innocuous dialog with a terms link and a user clicked ok, nobody sane would say that the malware-writer was legally in the clear. If FTDI doesn't end up prosecuted over this, I think it's less about the relevant laws and more about how prosecutors view people with money and status who commit crimes in pursuit of profit. Versus, of course, somebody like Aaron Swartz, who not only failed to wear a suit, but was engaged in a political act against the status quo. Crime that improves profits is currently more acceptable than crime that harms profits.
- cstross 12y agoIn the UK this looks like a clear criminal offence under the Computer Misuse Act -- currently carries a maximum 10 year prison sentence.
- wpietri 12y agoWhat's your opinion there on the odds of prosecution for something like this? I have the (possibly media-driven) notion that the UK has a stronger tradition of public service. But then you also have a more explicit class dynamic.
- technomancy 12y ago> Certainly in the US if somebody produced a virus that did this nobody would even blink at a federal prosecution. https://en.wikipedia.org/wiki/Sony_BMG_copy_protection_rootkit_scandal#Legal_and_financial_problems https://en.wikipedia.org/wiki/Sony_BMG_copy_protection_rootk... to be specific
- Igglyboo 12y agoGood, destroying a device you legally purchased is unacceptable, whether you knew it was a counterfeit or not. It's not their job to police that kind of stuff. Failing to work with counterfeit devices is completely fine and would have been a much better approach than straight up bricking them.
- kstrauser 12y agoAnd that's assuming it's actually counterfeit. Can you imagine the storm if "isCounterfeit()" turned out to be less than 100.000000% accurate?
- serf 12y agoYeah, but looking at the physical differences between the chips it's probably not something that difficult to ensure. The counterfeit chips are built in a totally different fashion, with different size and materials, on a different process tech. http://zeptobars.ru/en/read/FTDI-FT232RL-real-vs-fake-supereal http://zeptobars.ru/en/read/FTDI-FT232RL-real-vs-fake-supere...
- joezydeco 12y agoBut that's impossible for something like a Windows driver to determine. The only way the FTDI driver could determine if the chip counterfeit was a slight difference in how the counterfeit chips handled a certain EEPROM write. And the counterfeiters will be sure the next revision of the chip takes care of this corner case.
- sliverstorm 12y agoSure, the driver doesn't know the manufacturing process. His point is the chips are simply so different, there are bound to be obvious ways for the driver to tell.
- joezydeco 12y ago
- Karunamon 12y agoThere should be lawsuits. I really hope a class action gets started with people who were bitten by this. I'm serious. This kind of behavior needs to be nipped in the bud and made a massive example of, or else we will see it in the future.
- jerf 12y agoWe do not want to set a precedent whereby a company responds to customer feedback, and then gets hit by a huge lawsuit anyhow. That just incentivizes companies to dig their heels in, because it means there's no change in outcome between speedily responding and trying to stay the course, at which point staying the course is the only sensible choice. There's a time and a place for mercy, and giving positive feedback to the company for rapidly reversing course. They ate their crow; save the nuclear escalation for a company that refuses to.
- drzaiusapelord 12y agoThey have already damaged my equipment. I don't give two shits about hurting a corporation's feelings. They've already hurt my physical items. Once they've gone down that path, it's now an actionable tort. I can't believe their legal team approved of this. They need to be made an example of.
- deleted 12y ago[deleted]
- jameshart 12y agoWhat specific piece of equipment was affected? (not doubting - just curious, as I've not come across specific examples of people being affected by this driver)
- drzaiusapelord 12y agoThis guy in /r/sysadmin claims 35 devices nuked: http://www.reddit.com/r/sysadmin/comments/2k6wjk/fyi_ftdi_deployed_a_driver_update_through_windows/ http://www.reddit.com/r/sysadmin/comments/2k6wjk/fyi_ftdi_de...
- Alupis 12y agoSeems a lot of the posts on that thread are from HN visitors, many may not even have the equipment/chip in discussion. While it's great FTI reversed their decision (I'd hate to see this sort of thing become wide-spread), it's a little off-putting that so many non-users of the chip could force a company into something.
- smilekzs 12y agoWere we to wait for the real users to notice, it would have been too late.
- Alupis 12y agoNo, but suppose this was another scenario, such as automatic product bagger/sealers and some counterfeit part was being bricked by the original manufacturer. I doubt anyone outside of the warehouse/manufacturing industry would care, nor would anyone outside that industry have any real right to care. In the FTI situation, I'm indifferent, but I just don't like the "crowd mentality" thing where people get stirred up about things that only a few hours ago, they had no idea even existed.
- HeyLaughingBoy 12y agoThe company I work for uses (genuine) FTDI USB-Serial converters in our $500,000 medical instruments. I have full confidence in our Supply Chain Management people, but mistakes happen. If we were to send out a field upgrade to the instruments, as happens periodically, and some of them had the counterfeit chips, then suddenly there are patients all over the world, many in Emergency Rooms or Intensive Care, that can't get their test results because instruments are down. This can affect many, many people not in a particular industry, depending on where the device is embedded. As soon as I heard about this, I notified our senior design EE so he could pass the information on if necessary. This is not to be taken lightly.
- Alupis 12y agoThe scenario you present is a little "doomsday". You'd have to replace all of your deployed product's chips with cheap counterfeit ones for this to happen -- and you say you have complete confidence in your supply chain. My warehouse has a couple Sharp Max baggers w/ counter and sorter, which are just as expensive as your medical instruments. The electronics check to ensure you are using only the Sharp brand parts, otherwise the machine refuses to work. Most printer cartridges won't work in printers unless they are the name-brand cartridge (printers read the chip on the cartridge). Neither permanently damage the counterfeit parts, but it doesn't matter much if you can't use the counterfeit part you just bought (thinking you were going to save a buck or two). Frankly, I don't buy the argument that a lot of users didn't know they had bought counterfeit. For a device that retails for $15 and you got it new for $1.50, well, something is up. Perhaps a better way for FTI to go would be to detect the counterfeit when it's plugged in, then just refuse to do anything with it. (although this would allow someone to get a non-FTI driver to work)
- expr- 12y agoI disagree with the consensus. It's their driver, it operates in a specific way, perhaps responding to possible device output. Using it with non-compatible parts advertising themselves as compatible and any resulting behaviour, including unwanted, is the responsibility of the user. To play it safe, don't use any drivers with incompatible hardware.
- HCIdivision17 12y agoYou'd be right if this weren't just a chip buried in a device. To properly implement that, we'd need to be able to safely scan and verify devices on the chip-level. That's not really an option. The end user is only ever going to be informed by the driver telling them it's invalid; in this case the notification is the silent crippling of the gizmo, with no feed back or diagnostics. As many have noted, all that's needed is an alert for the user that the driver's incompatible. That way the user can take rectification measures, be it getting new compatible chips/devices, or using unofficial drivers.
- kabdib 12y agoAlerting the user from a driver is a bad, bad thing. I believe it is not allowed by WHQL certified drivers. (It's also non-trivial to do in a Windows kernel driver. You can't call MessageBox(), you can't process user input, you can't even get a context to draw on the screen. Basically you have to rely on a user-mode helper app that gets launched at boot time, which is one of the reasons you see so many device-tweaking utilities for graphics cards and sound cards).
- HCIdivision17 12y agoOh absolutely. To me, it's just choosing the lesser of two evils. Like, I'd rather go to jail and be inconvenienced instead of shot on sight, but I feel both are overkill for a parking ticket.
- JoeAltmaier 12y agoThat's reasonable, until they start deliberately destroying my property. Then its a civil case. Do we have any evidence either way, deliberate or accidental?
- mwill 12y agoIt's interesting watching this play out with reputable, legal companies. Something similar happened earlier in the year with Nintendo 3DS flashcards, however the software was not just disabling the flashcard, but would brick the users 3DS. Their response was essentially, "Yeah? What are you going to do about it?" and promising to replace the 3DS of anyone who could prove they were using a legitimate card.
- nnnnni 12y ago...which is a really great way to get budding hobbyist programmers to move to a different piece of hardware.
- mwill 12y agoOr try to, anyway. At the time they were the only functioning solution (They may still be? I'm out of the loop now) and everything else on the market were clones of their cards. It was almost like a hostage situation with the community, a lot of people hating on the company, while hyping up their next update.
- deleted 12y ago[deleted]
- sliverstorm 12y agoHonestly I doubt Nintendo cares about selling consoles to game pirates. They, like everyone else in that business, make their money on game sales.
- jeff_tyrrill 12y agoI wanted to reply with a quick note to clarify to those quickly reading this post that it was the flash card maker, not Nintendo, adding the bricking code. Your post is accurate, but to those not already familiar with this incident (such as myself, until I searched for stories about it), a quick read will give the impression that this was Nintendo's doing, when it wasn't.
- jessaustin 12y ago
- userbinator 12y agoIt's also important to keep in mind that the driver bricked not only counterfeits that were illegally marked with FTDI's name, but legal clones (reverse-engineered reimplementations which are not marked as being from FTDI) that had the same slight difference in behaviour from the original.
- bri3d 12y agoThe reverse-engineered reimplementations / clones would have to have been programmed with an FTDI VID (or included modified FTDI drivers) in order for the FTDI drivers to claim them, so I'm not so sure about the "not marked as being from FTDI" bit.
- welterde 12y agoAs far as I know that's perfectly legal.. you are just not allowed to put the USB logo onto the device if you clone the VID from another vendor. And you seemingly can buy FTDI clones that are not marked as FTDI on the casing.
- wpietri 12y agoThat's an interesting question. Is the VID a signal of protocol compatibility? Or a brand name? In a way it's both, but since end users almost never see the VID, I suspect a lawyer would have an easy time that under the law it's more the former than the latter, and therefore not covered under trademark and related laws.
- welterde 12y agoEspecially since it's the only way to be compatible as far as I know (since (VID,PID) determines the driver that will get loaded for proprietary protocols). Also.. Can you even claim any special rights to a non-government registered trademark/brand name (one that is registered at a non-government entity - the USB Implementers Forum in this case)?
- nraynaud 12y agoThat's a good lesson for people always wanting the famous brands. FTDI chips are more expensive and not better than the other ones, they need a special driver and they are subject to counterfeiting. You take a no-name one, and you have a standard stuff. It's a stupid USB to RS232, not a rocket control system, there should be no famous brand, it's the lowest of the commodities. That said, I do have an FTDI USB to serial adapter (no idea of the authenticity), because I didn't know better or care, I needed to plug my MCU board to my computer and I bought the first one I found (and it's just used for debug, I never ever use serial in real life).
- learc83 12y agoWith the no name brands (at least the ones that aren't just using FTDI's drivers) you are more likely to have to install a driver.
- jws 12y agoThe FTDI chips and drivers also have the ability to toggle a few extra pins. If you are making a device this can be important enough to lure you away from just being a generic USB Communications Device Class profile. (Think a 'reset' function or a 'enter firmware update mode' function.) Given that as a consumer/purchaser I have no way of knowing if I have a counterfeit chip or if the next batch produced by a manufacturer will have them… I now have an incentive to avoid FTDI entirely when given a choice.
- nraynaud 12y agoGood remark. I didn't think about that, because I use a real USB chip for USB, I don't try to convert it to serial (I like the idea of having various communications going at once, the stall, etc.)
- sliverstorm 12y agoserial is your bread-and-butter on tiny low pin count underpowered IC's. The V8's of the micro-controller world are great, but sometimes you have just 2000mAh to get you through a year of operation.
- kabdib 12y agoTheir best course of action: - unbrick devices they bricked, so the chips will at least work with drivers other than theirs - log something to the windows event log about a clone device being detected It's their choice whether they should work with the clone device or not; I would hope they would choose to. I understand their reluctance, but people are going to be only slightly less mad about a device not working than a bricked device. It would be bad for their driver to pop UI warning about a clone device. Drivers that do this make life very, very difficult for devices attached to headless servers (also, I believe it's against the MS WHQL rules).
- cnvogel 12y agoWindows drivers can opt to mark the device they are responsible for as "non operational". https://en.wikipedia.org/wiki/Device_Manager#Error_Codes https://en.wikipedia.org/wiki/Device_Manager#Error_Codes I think it's the #43 I've seen from time to time: "Windows has stopped this device because it has reported problems." http://technet.microsoft.com/en-us/library/cc725873(v=ws.10).aspx http://technet.microsoft.com/en-us/library/cc725873(v=ws.10)... They get a special icon in "Device Manager", and, if I remember right, the statusbar-thingie that dances around while newly-connected devices are detected will put up a bubble with an error message.
- spc476 12y agoHow would they unbrick a device? By definition, to "brick" is to render the device inoperable. A friend of mine, in the course of his work, bricked a BMW [1]. It took an engineer, flown in [2] to fix the issue. [1] He worked at a company making automobile diagnostic tools for mechanics. He was reflashing the BMW when the power went out. That scrambled the on-board computer system enough to brick the car. [2] South Florida (Miami/Ft. Lauderdale area) I'm sure the German engineer wasn't all that upset.
- kabdib 12y agoTo misquote The Princess Bride: "This device isn't bricked. It's just mostly bricked. There's a difference." The device is still there, and it will talk, there's just no matching driver in the system for it now. So you add PID=0x0000 to your existing driver (I think this is just an edit to the INF file on Windows) and sniff the device to see if it's one you've likely (semi) bricked, and make the attempt. You own the VID, so this operation should be safe in your namespace. Brickness is a measure of the user's ability and motivation to restore a device. I've worked on systems where you have to unsolder really tiny devices in order to unbrick. It's a continuum of inconvenience, really. To most users, the evil FTDI driver made a brick because it was beyond their skill to do the repair (hey, you can write a driver for PID=0x0000 any time you want to, oaky?)
- muyuu 12y agoLooks like their boards have been HN-ed.
- wpietri 12y agoIs this an opportunity for someone to make an open-source driver that just works?
- poslathian 12y agoFor those of you with bricked FTDI chips, there is hope on linux: https://lkml.org/lkml/2014/10/24/44 https://lkml.org/lkml/2014/10/24/44
- isopede 12y agoThis is a counter patch which restores the broken PID. The original proposed patch is actually a parody Linux version which bricks FTDI chips. The real Linux patch which adds support for broken clones is here: https://git.kernel.org/cgit/linux/kernel/git/johan/usb-serial.git/commit/?h=usb-linus https://git.kernel.org/cgit/linux/kernel/git/johan/usb-seria...
- duskwuff 12y agoMaking the parody even funnier: It uses the exact same procedure to "brick" counterfeit devices as the Windows drivers did.
- hippich 12y agoIt mentions Windows, what about other OSes? Does linux/mac need driver? If no - why it works without driver on these OSes?
- Vendan 12y agoCause Linux has drivers that support it already, that are a part of the kernel. Not likely that FTDI'd manage to get the kernel devs to add bricking code like this. Kernel devs already added code to handle devices that had been messed up by the drivers, actually.
- hippich 12y agoThen why there is no open source driver for windows which works with non-genuine chips?
- Vendan 12y agoBecause windows drivers need non-trivial amounts of support in the form of driver development kit and driver signing. Then you run into issues with which driver to pull for the chip, cause now you are conflicting with FTDI's driver. Other chips that aren't clones do have their own drivers.