I think the missed opportunity here is a license available for the low, low cost of $5 to continue using a counterfeit device...
Perhaps it's a break, then fix sort of thing.
how would that work on linux? linux has source-based code and you can't force a binary blob down (usually) and get away with it once the source is already out there.
you could stop the mac and windows users but linux lets users see and modify source code. the vendor can't threaten linux users. they probably knew this and so they (apparently) decided there was ONE 'fix' for all os's. and I use the word 'fix' in the most non-literal sense.
then again, a linux driver update to ftdi_sio.[ch] may be coming soon that allows the 0000 pid.
In which case it would be an easy matter to do a search in the driver for that serial number and mask it out.The driver is signed, if you change anything it will not work again.
In which case it would be an easy matter to do a search in the driver for that serial number and mask it out.
The driver is signed, if you change anything it will not work again.
Imagine instead of just bricking the device, you received a popup saying "Your product is counterfeit, please contact the manufacturer for RMA or purchase a license from FTDIStore.com." You'd still be annoyed, but you'd probably pay the $5 so that you can continue using the $30 device.
That way, the OEM still is forced to purchase genuine parts, the user can continue using their device, and FTDI still gets revenue from a missed sale.
In which case it would be an easy matter to do a search in the driver for that serial number and mask it out.
The driver is signed, if you change anything it will not work again.Quite naturally, there's a patch to disable that too, or resign with your own certificate (which you've installed as a trusted root.)
I'm wondering are these fools blaming FTDI are actually real users? or are they just trols paid by fake ICs manufacturers? it was entertaining to read the posts but come on they can't be real.
what wrong did I do by buying a device on amazon, fully believing that the items there won't be ebay-style fakes?
how is it right, in your view, to punish ME for this?
At least if I design a .. Prolific... part into my product, it's less likely to get wrecked by malware.
Oh crap. I bought a rs232 TTL converter from adafruit and it had the same exact issue. The PID used to reset to 0000.
Hackaday and EEVblog are reporting that the latest Windows update that include FTDI drivers brick any counterfeit FTDI chips. Adafruit requires it suppliers to only use genuine FTDI chips. However, no matter what it’s always possible counterfeit chips could be used when you purchase products from anyone, anywhere. We’re double and triple checking all our products and suppliers as an added precaution.
In case anyone was still wondering if this is intentional and malicious...
Straight out of their driver. Function/variable naming and comments mine.
what wrong did I do by buying a device on amazon, fully believing that the items there won't be ebay-style fakes?
how is it right, in your view, to punish ME for this?
I heard that one before, from a guy trying to smuggle elephant ivoryAt least if I design a .. Prolific... part into my product, it's less likely to get wrecked by malware.
you seem to missed the memo on prolific driver bsoding on purpose when it detects fake chip
Oh crap. I bought a rs232 TTL converter from adafruit and it had the same exact issue. The PID used to reset to 0000.
Might want to contact them about that, they have a statement on their website at the moment saying all of theirs are genuine.Hackaday and EEVblog are reporting that the latest Windows update that include FTDI drivers brick any counterfeit FTDI chips. Adafruit requires it suppliers to only use genuine FTDI chips. However, no matter what it’s always possible counterfeit chips could be used when you purchase products from anyone, anywhere. We’re double and triple checking all our products and suppliers as an added precaution.
what wrong did I do by buying a device on amazon, fully believing that the items there won't be ebay-style fakes?
how is it right, in your view, to punish ME for this?
I heard that one before, from a guy trying to smuggle elephant ivory
What did he use the FTDI IC for?
What did he use the FTDI IC for?
That's the whole point. He used a fake chip... or a fake elephant. Or something. Or the real elephant came back and trampled the fake ivory because it wasn't real.
You see?
In case anyone was still wondering if this is intentional and malicious...
Straight out of their driver. Function/variable naming and comments mine.
I wonder if Microsoft was aware of this practice and will they let it go on.
In case anyone was still wondering if this is intentional and malicious...
(disassembled code)
Straight out of their driver. Function/variable naming and comments mine.