Three States Propose DMCA-Countering 'Right To Repair' Laws (ifixit.org)

Automakers are using the Digital Millennium Copyright Act to shut down tools used by car mechanics -- but three states are trying to stop them. An anonymous reader quotes IFixIt.Org: in 2014, Ford sued Autel for making a tool that diagnoses car trouble and tells you what part fixes it. Autel decrypted a list of Ford car parts, which wound up in their diagnostic tool. Ford claimed that the parts list was protected under copyright (even though data isn't creative work) -- and cracking the encryption violated the DMCA. The case is still making its way through the courts. But this much is clear: Ford didn't like Autel's competing tool, and they don't mind wielding the DMCA to shut the company down...

Thankfully, voters are stepping up to protect American jobs. Just last week, at the behest of constituents, three states -- Nebraska, Minnesota, and New York -- introduced Right to Repair legislation (more states will follow). These 'Fair Repair' laws would require manufacturers to provide service information and sell repair parts to owners and independent repair shops.
Activist groups like the EFF and Repair.org want to "ensure that repair people aren't marked as criminals under the DMCA," according to the site, arguing that we're heading towards a future with many more gadgets to fix. "But we'll have to fix copyright law first."

Comments

Great Idea and I live in MN

[oldgraybeard]

i have a 1999 Ford Expedition, great truck for the 2-3k I drive it a year. Had a cracked windshield replaced which leaked (they fixed it) but it got my Gem Module(General Electronics Module) and fuse box wet. Darn truck, kept draining the battery, most of the electric stuff did not work, no lights, flashers, turn signals, dash indicators, windows ;) lol, !. Got it to the dealer. They said my GEM Module was bad, and they would order one.

It would be 700.00 dollars up front and they had no idea when it would arrive. In fact they had one customer that has been waiting 7 months.

OK so I talk about getting one from the junk yard. But!!!! it needs to be programmed with the exact options my truck has and only Ford can do that and that is 500.00

I went home and just charged the battery everytime I wanted to drive the truck. And over time things dried out. All is good now.

I have been gathering every scrap of info so I can build a jig and write a program to dump the firmware from my electronic modules on my truck, since I am keeping it forever ;)

Corporate Stupidity

[GerryGilmore]

I used to work at Dialogic, which was then bought by Intel. In all my time there, new prospects/customers would invariably say: "This is really hard to configure (we had line resource cards, DSP resource cards, and various ways to map these resources together.) don't you guys have a card configuration utility?" Well, for Windows, yes. For Linux, no. "Too hard and no demand" says Engineering. So, taking the bull by the horns, I found the PCI ID codes for the various cards, wrote a utility to configure them, got approval from my manager to release it as open-source and all was well. Until...The head of Engineering at our division found out about it and lodged a formal internal complaint that I had "released Intel proprietary information" and was summoned to Parsippany to face legal. Fortunately, my manager's support and basic common sense prevailed, the Eng manager was sent packing with his tail between his legs and I flew home drunk as a skunk. The legal guy basically said: "when you expose a PCI ID to the OS, it's no longer proprietary - dumbass!". Point is that when information is documented and exposed in any way, it is not "proprietary" in the sense that it cannot be used, just not stolen and used inappropriately.