4 ms·
IF this is on purpose and can be proven so, it is most definitely illegal!
by dmitrygr 12y ago
IF this is on purpose and can be proven so, it is most definitely illegal!
- spiritplumber 12y agoAll they have to say is "We write our drivers to support our chips, if it messes with other chips that incorrectly identify as ours, that's just the way it went, it'd cost us extra to support them and why should we help our competitors". Practically impossible to prove otherwise.
- rainforest 12y agoThey have a track record of trying to fingerprint and screwing with counterfeits, so it would appear there's evidence the driver doesn't happen to disable counterfeits, but actively disables them. To me there's a fuzzy distinction (possibly not reflected in law) between software that breaks when you make it do stuff you didn't design, versus having it attack things you don't want it to work with.
- DannyBee 12y ago"All they have to say is "We write our drivers to support our chips, if it messes with other chips that incorrectly identify as ours, that's just the way it went, it'd cost us extra to support them and why should we help our competitors"." Buzz, thanks for playing. :) That won't get them out of discovery for various torts, and the discovery (emails, code, etc) is likely to show they did this on purpose. It's not practically impossible, it's trivially easy to disassemble and see if it does this on purpose. Then you argue it to a jury, and it's going to look really really bad for FTDI.
- Tomte 12y agoI wish German civil law had something like your discovery process. Over here the claimant probably would not be able to peek into the defendant's stuff. Especially if he can't specifically claim "on march 10th, Mr. Meier sent an email to Mr. Schmidt discussing topic X". A simple "hand over your mails about the matter at hand" would be ruled a "fishing expedition", not admissible as a motion to discover.
- deelowe 12y agoTo quote CTZ: "You should look up the word 'intent' in law."
- Zigurd 12y agoI wonder why this is voted down. The US has some severe laws against vandalizing computing devices and against unauthorized access. Why wouldn't these laws apply here?
- DannyBee 12y agoThere are a variety of laws that would apply here, and doing what they did, if done intentionally, is almost certainly cause for civil liability. They are not allowed self-help in the form of destroying other pieces of hardware. If they have a problem with counterfeit chips, the solution is customs/legal process/etc If they aren't happy with what that buys them, they should be pushing for legal change.
- ja27 12y agoIt's quite possibly a violation of U.S. Code 1030(a)(5)(A), a federal felony: (5) (A) [Whoever] knowingly causes the transmission of a program, information, code, or command, and as a result of such conduct, intentionally causes damage without authorization, to a protected computer; Now "protected computer" and the [ab]use of the Interstate Commerce Clause mean that the device with the FTDI would likely need to be connected to a network for this to apply. Plus I think they still need to show $5,000+ in damage, but it wouldn't be hard to reach that if the driver wrecked a prototype and delayed a product.
- snarfy 12y agoFrom their website: >The licence only allows use of the Software with, and the Software will only work with Genuine FTDI Components (as defined in the Licence Terms). Use of the Software as a driver for a component that is not a Genuine FTDI Component MAY IRRETRIEVABLY DAMAGE THAT COMPONENT. IANAL but I don't believe this disclaimer can possibly be valid. Personal property rights cannot be waived away with a disclaimer.
- Zigurd 12y agoIt amounts to an admission they are bricking clones on purpose.
- dsl 12y agoHow are your personal property rights being violated? If an ATI graphics card lied and claimed to be an nVidia card and the drivers cause it to overheat and catch fire, who is at fault? Should you be required to QA your drivers against counterfeit products? Edit: nobody has shown that the driver is intentionally writing the ID to 0, the counterfeit chip isn't even close to the same circuitry and could be screwing up a legitimate instruction.
- ctz 12y agoYou should look up the word 'intent' in law.
- revelation 12y agoThis isn't a misconfiguration issue, or that Linux bug that bricked certain SCSI devices. No, they are explicitly asking the counterfeit chip to rewrite its USB PID to 0, which renders it unusable. That's intentional and clearly malicious.
- cnvogel 12y agoHas this been proven by a corresponding packet dump listing "Write EEPROM, offset 0, 4 bytes: [0,0,0,0]? Or are they -sneakily- bricking the device by evoking an unintended reaction to a seemingly innocuous command? The former will be easy to prove, the latter.. probably not so much.