Live data from Hacker News

FTDI removes counterfeit-bricking driver from Windows Update

eevblog.com

11–20 of 131 posts

Re: FTDI removes counterfeit-bricking driver from Windows Update

#11
Seems 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.

Re: FTDI removes counterfeit-bricking driver from Windows Update

#12
I 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.

Re: FTDI removes counterfeit-bricking driver from Windows Update

#13
post #7

There 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.

We 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…

No, this isn't "responding to customer feedback". The code they published was pretty much illegal - imagine your garage destroying your car because it's the wrong brand! Their reasoning should be (and probably was) "by fixing this fuck-up ASAP, we'll only get a class-action lawsuit by 10K customers, instead of by 100K".

Re: FTDI removes counterfeit-bricking driver from Windows Update

#14
post #7

Earlier quoted context omitted.

We 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…

They 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]

Re: FTDI removes counterfeit-bricking driver from Windows Update

#15
post #11

Seems 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.

Were we to wait for the real users to notice, it would have been too late.

Re: FTDI removes counterfeit-bricking driver from Windows Update

#16
post #7

There 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.

We 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…

Bluntly? Fuck 'em. The only reason they "responded" apparently is because Microsoft tapped them on the shoulder, by way of yanking their updates until it gets fixed, and then only because someone publicly connected the dots as to what was going on.

There is an untold amount of bricked gear out there. Those people are entitled to replacements and compensation for their time spent dealing with this malfeasance.

Re: FTDI removes counterfeit-bricking driver from Windows Update

#17
post #10
post #9

Earlier quoted context omitted.

Maybe they should reach out to affected parties and help them replace their destroyed equipment.

They really should. Class actions are an inferior mechanism for both parties anyhow. The lawyers sitting in the middle will make it so it's radically more expensive for the company, and the odds of the supposed "winners" of the class action suit will probably get uselessly small vouchers for service rather than actual replacement.

Class actions are less about compensation and more about forming big enough sticks to beat misbehaving corporations about the head with.

Re: FTDI removes counterfeit-bricking driver from Windows Update

#18
post #9
post #7

Earlier quoted context omitted.

We 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…

Maybe they should reach out to affected parties and help them replace their destroyed equipment.

No equipment was destroyed by the old driver: the old driver set a word in the firmware of counterfeit devices to zero. All that needs to happen to reverse what some comment-writers are calling "bricking" is to set the word back to its original value. The new version of the driver could probably do that.

Re: FTDI removes counterfeit-bricking driver from Windows Update

#19
post #7

Earlier quoted context omitted.

We 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…

They 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.

What 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)

Re: FTDI removes counterfeit-bricking driver from Windows Update

#20
post #12

I 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.

You'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.

Post reply on HN