Xref: utzoo sci.electronics:19474 rec.autos.tech:23491 Newsgroups: sci.electronics,rec.autos.tech Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!caen!news.cs.indiana.edu!ux1.cso.uiuc.edu!mrcnext!khan From: khan@mrcnext.cso.uiuc.edu (Scott Coleman) Subject: Hacking Car ECUs Message-ID: Sender: usenet@ux1.cso.uiuc.edu (News) Organization: University of Illinois at Urbana References: <1991Apr14.224844.3126@coral.bucknell.edu> <02~_0R|@warwick.ac.uk> Date: Sat, 20 Apr 1991 15:24:04 GMT Lines: 28 esupg@warwick.ac.uk (Andrew Bargery) writes: >However, my personal favorite to ensure your car is there when you get back: >(I don't know if any one has actually tried this...) >With the increased use of ECUs in cars, why not have the software encoded by a >DES algorithm? Unless you know the password, it's going to be >just-a-little-tricky to hot wire :-) This doesn't stop someone with a towtruck, however. :( Speaking of hacking engine computers, what sort of development system would one have to have in order to make such changes? Even with a long extension cord, using a desktop PC as a development system is a little difficult. ;-) I can see using a portable, but portables have funky expansion slots (when they have expansion slots at all!) which means you can't plug in the usual logic analyzer type expansion cards. Has anyone out there actually put together a portable development system? Or are all these mods made by hauling the PC out to the garage workbench? -- Scott Coleman tmkk@uiuc.edu University of Illinois at Urbana-Champaign "If a software computer consultant believes her gonads are ruled by the moon, then none of us is safe." - Karla Jennings