k0mpresd
|
|
« on: November 05, 2012, 09:56:13 PM »
|
|
|
would like to hear what you guys do, if anything, about protecting your tune. encryption boards, epoxy on the board, ect. the scrambler boards are useless as the data can just be dumped in bootmode. epoxy on the board i feel is useless to a point. its still pretty easy to defeat. so, is it even worth it to try to protect your work?
|
|
|
Logged
|
|
|
|
elRey
|
|
« Reply #1 on: November 05, 2012, 10:04:00 PM »
|
|
|
I've ask about immo functions so i could at least ask for vin and hard code that so tune compares my hard coded vin against immo chip vin. then if missmatch force limp mode.
not that secure
|
|
|
Logged
|
|
|
|
k0mpresd
|
|
« Reply #2 on: November 05, 2012, 10:16:44 PM »
|
|
|
exactly. pointless. dump eeprom, immo off, protection broken. i guess really there should be 2 points to discuss here. protection against cloning vs protection against just getting a read.
|
|
|
Logged
|
|
|
|
vwaudiguy
|
|
« Reply #3 on: November 05, 2012, 10:51:34 PM »
|
|
|
There have been a few instances that I tried to dump contents through the same scrambler board/chip and each time received a slightly different file, then trying again non-boot using Nef and getting another file.. I thought these scrambler/encryption boards could recognize boot mode then send bad data?
|
|
|
Logged
|
"If you have a chinese turbo, that you are worried is going to blow up when you floor it, then LOL."
|
|
|
k0mpresd
|
|
« Reply #4 on: November 05, 2012, 11:11:00 PM »
|
|
|
i got bad data in the bootloader part one time. just patched the bootloader with one from the same file # and it was fine. i just considered it a fluke. only time ive had a problem reading them.
|
|
|
Logged
|
|
|
|
vwaudiguy
|
|
« Reply #5 on: November 05, 2012, 11:17:15 PM »
|
|
|
just patched the bootloader with one from the same file # and it was fine.
Can you explain this?
|
|
|
Logged
|
"If you have a chinese turbo, that you are worried is going to blow up when you floor it, then LOL."
|
|
|
k0mpresd
|
|
« Reply #6 on: November 05, 2012, 11:18:53 PM »
|
|
|
0>ffff in hex.
|
|
|
Logged
|
|
|
|
SVSPORT
Full Member
Karma: +9/-0
Offline
Posts: 104
|
|
« Reply #7 on: November 06, 2012, 03:27:05 AM »
|
|
|
I think there is no protection on the bench, if there is a pro tuner. I prefer to lock the OBD for "small" tuners...
|
|
|
Logged
|
|
|
|
Bische
|
|
« Reply #8 on: November 06, 2012, 03:31:48 AM »
|
|
|
I think there is no protection on the bench, if there is a pro tuner. I prefer to lock the OBD for "small" tuners... How is that done?
|
|
|
Logged
|
|
|
|
prj
|
|
« Reply #9 on: November 06, 2012, 04:20:35 AM »
|
|
|
How is that done?
Disable the upload service... But that won't save it from anyone who is serious about reading it. What I do on older ECU's, is I add an additional checksum algorithm and modify some values in the ECU (for example MAF calibration), to calculate this checksum and then use an offset for every value. I don't store the checksum anywhere, only the offset. And if anyone modifies my file, the MAF will stop working. If they even manage to strip all my ASM logic from the file, then the MAF will still not work because the actual calibration is "wrong" and needs the offset. I do this for a couple of maps... so people don't touch my base tunes. As for copy protection - you are never going to achieve this. But I think some clever things can be done to prevent someone taking your tune, making a couple changes to it and passing it as their own.
|
|
|
Logged
|
|
|
|
k0mpresd
|
|
« Reply #10 on: November 06, 2012, 10:56:35 AM »
|
|
|
I think there is no protection on the bench, if there is a pro tuner. I prefer to lock the OBD for "small" tuners... yes, nothing has ever stopped me from getting a read. this is the main reason i was wondering what other people's methods were. really i feel like things are just more of a deterrent than an actual protection.
|
|
|
Logged
|
|
|
|
k0mpresd
|
|
« Reply #11 on: November 06, 2012, 10:59:41 AM »
|
|
|
i really feel like the best method would be the epoxy on the board, top and bottom since bootpin is on flash, cpu, and ram. most people are too scared to heat it to remove it. and some sort of software run-around like prj describes + lock file to the eeprom. at least then you have to break down 3 doors and at the most you would be able to clone the file and never modify anything.
|
|
|
Logged
|
|
|
|
Snow Trooper
|
|
« Reply #12 on: November 06, 2012, 11:21:42 AM »
|
|
|
I prefer to just do good enough custom tunes that they don't copy over well. And I change weird obscure stuff that i can reference and know when people do copy.
|
|
|
Logged
|
cartoons? 6A 61 72 65 64 40 76 6C 6D 73 70 65 63
|
|
|
jpi512
Newbie
Karma: +3/-0
Offline
Posts: 14
|
|
« Reply #13 on: November 07, 2012, 08:28:53 AM »
|
|
|
hello............. its hard to me explain my method in english........... in this moment i use a combination of a glue and sodium bicarbonate, that convert in a few seconds in a rock.......
in second way, in this moment im talking with a programmer that offer me in a solution. first step is encript some maps, this force to cloner to use "complete file".if use it..... then a few minutes/hours. the car stop, and erase flash eprom and eeprom.......... what do yo think?
jpi512
|
|
|
Logged
|
|
|
|
lulu2003
Full Member
Karma: +11/-1
Offline
Posts: 242
|
|
« Reply #14 on: November 07, 2012, 08:59:10 AM »
|
|
|
nice thoughts!
physical (glue) protection agains boot mode or BDM means you are only able to write by OBD?
there won't be a 100% secure way, I think, unless you want to be able to re-write.
I like the Idea by prj but wouldn't it be easier to change some hardware that belongs to the software calibration. easiest way would be like a resistor between ECU and a sensor (e.g. MAP/MAF) and change the according maps. That would confuse 99% of tuning related people and copy paste will not work, and you know that probably even less than 1% really know what they can read.
Same applies to very custom tunes.
|
|
« Last Edit: November 07, 2012, 09:08:52 AM by lulu2003 »
|
Logged
|
|
|
|
|