NefMoto

Technical => Tuning => Topic started by: NOTORIOUS VR on October 21, 2011, 07:44:26 AM



Title: Protecting read out via OBD
Post by: NOTORIOUS VR on October 21, 2011, 07:44:26 AM
So as far as I understand it there is a way to prevent reading out the tune via OBD.  Y"es I know you can still read it out via boot mode, but I think it would be nice to be able to "lock" in and make it more difficult for someone to just read out.

Has anyone figured out how to do this?



Title: Re: Protecting read out via OBD
Post by: RaraK on October 21, 2011, 10:49:37 AM
yes and no.

just obd read you can use "ecusafe" which just turns of obd read for SOME tools, not all.  You could also change the security string or seed key(havent tested this) as well.  which will prevent a read.

add no read into the file to block some tools as well.

unfortunately, official tools seem to get blocked by these methods, some clone tools have this bypassed  ::)



Title: Re: Protecting read out via OBD
Post by: NOTORIOUS VR on October 21, 2011, 11:59:13 AM
Wouldn't changing the seed key also prevent writing?


Title: Re: Protecting read out via OBD
Post by: judeisnotobscure on October 21, 2011, 12:30:30 PM
on mbox, change 088cb from 0f to 00

once u do this it can't be undone on the file as far as i can tell so save as... i did it once and had to use boot mode to make revisions even after changing it back. I probably couldn't write one from scratch though, so idk what to do now. lol  (sarcasm)


Title: Re: Protecting read out via OBD
Post by: NOTORIOUS VR on October 21, 2011, 12:43:33 PM
thanks!

what do you mean it can't be undone?  you can't change 088cb from 00 back to OF?


Title: Re: Protecting read out via OBD
Post by: judeisnotobscure on October 21, 2011, 12:46:54 PM
i changed it back to 0f and flashed the new file via boot mode it didn't seem to matter.
flashed a stock file and got obd read write back.  flashed file revised back from obd read rite off to on and no dice.
let me know if you get different results.


Title: Re: Protecting read out via OBD
Post by: phila_dot on October 21, 2011, 12:56:54 PM
Can you still connect with VCDS?

Do you know the name of the codeword or byte at that location?


Title: Re: Protecting read out via OBD
Post by: judeisnotobscure on October 21, 2011, 01:06:03 PM
yes, you can connect with vcds still.
I don' know the codeword though
change from 0f to 00


Title: Re: Protecting read out via OBD
Post by: NOTORIOUS VR on October 21, 2011, 01:36:19 PM
I'll update when I try it for sure.

Thanks again!


Title: Re: Protecting read out via OBD
Post by: Gonzo on October 21, 2011, 04:03:22 PM
I'm glad its working for you Josh  :P

Its not a codeword. Its a hack.

Not sure why NVR wants to do this though. Shouldn't all files be free?  :P :P


Title: Re: Protecting read out via OBD
Post by: judeisnotobscure on October 21, 2011, 04:27:11 PM
yup it works great... except you can't turn it off... useful for sure though.  ;)


Title: Re: Protecting read out via OBD
Post by: Gonzo on October 21, 2011, 04:32:22 PM
 ;)


Title: Re: Protecting read out via OBD
Post by: phila_dot on October 21, 2011, 04:49:00 PM
Just to confirm, writing over OBD is still possible?


Title: Re: Protecting read out via OBD
Post by: judeisnotobscure on October 21, 2011, 04:49:52 PM
no, blocks read and write... u must write via bootmode.


Title: Re: Protecting read out via OBD
Post by: Gonzo on October 21, 2011, 05:22:23 PM
No, josh is wrong. Only read is protected.

Write is fine. I never block off writing on my files.


Title: Re: Protecting read out via OBD
Post by: phila_dot on October 21, 2011, 05:32:21 PM
No, josh is wrong. Only read is protected.

Write is fine. I never block off writing on my files.

I don't have any need for this, but that would be a deal breaker for me.


Title: Re: Protecting read out via OBD
Post by: Gonzo on October 21, 2011, 06:45:53 PM
What do you mean? You want write blocked out too? Why?

Im not some jerk that locks up your ECU for fun. If you want to ovewrite my tune with something else I let people do it :)

This is what every company out there does BTW.


Title: Re: Protecting read out via OBD
Post by: phila_dot on October 21, 2011, 07:09:25 PM
No, not being able to write would make it worthless to me.


Title: Re: Protecting read out via OBD
Post by: RaraK on October 21, 2011, 08:48:36 PM
no, blocks read and write... u must write via bootmode.

Yea just read it block, i 2nd this, ive written over with kwp no problem.


Title: Re: Protecting read out via OBD
Post by: NOTORIOUS VR on October 21, 2011, 09:35:04 PM
Not sure why NVR wants to do this though. Shouldn't all files be free?  :P :P

If someone wants my files bad enough there are still ways to get it... but why should I make it easy for them :)


Title: Re: Protecting read out via OBD
Post by: Gonzo on October 23, 2011, 10:28:15 AM
Not sure why NVR wants to do this though. Shouldn't all files be free?  :P :P

If someone wants my files bad enough there are still ways to get it... but why should I make it easy for them :)
At least we share the same views on this aspect haha


Title: Re: Protecting read out via OBD
Post by: matchew on October 23, 2011, 10:48:06 AM
I read out a file only yesterday that had this byte changed. Didn't stop the file being read from the ECU at all.


Title: Re: Protecting read out via OBD
Post by: Gonzo on October 24, 2011, 11:31:03 AM
I read out a file only yesterday that had this byte changed. Didn't stop the file being read from the ECU at all.
There is more things you can change if you really want to block reading completely.


Title: Re: Protecting read out via OBD
Post by: NOTORIOUS VR on October 24, 2011, 12:28:31 PM
^^ would you mind sharing?


Title: Re: Protecting read out via OBD
Post by: judeisnotobscure on October 24, 2011, 01:46:59 PM
No, josh is wrong. Only read is protected.

Write is fine. I never block off writing on my files.
I was wrong... just having issues with one car only.
I'm going to double check a few other things  ;)


Title: Re: Protecting read out via OBD
Post by: infinkc on October 24, 2011, 06:02:28 PM
ecufix only changes this one byte also to protect the reading, doesnt affect writing to the ecu again.  yea it still can be read out if you know what you are doing. and also do not checksum after you change this byte. Yes you will get checksum errors if you try and verify the bin.


Title: Re: Protecting read out via OBD
Post by: Gonzo on October 25, 2011, 06:48:15 PM
ecufix only changes this one byte also to protect the reading, doesnt affect writing to the ecu again.  yea it still can be read out if you know what you are doing. and also do not checksum after you change this byte. Yes you will get checksum errors if you try and verify the bin.
Sounds like your WinOLS has the checksum bug  ;D


Title: Re: Protecting read out via OBD
Post by: pedrogbranco on November 18, 2015, 06:34:49 AM
what about scrambled files. files that even if you read you at least cannot interpret the contents without a key


Title: Re: Protecting read out via OBD
Post by: nyet on November 18, 2015, 10:38:43 AM
what about scrambled files. files that even if you read you at least cannot interpret the contents without a key

Waste of time.


Title: Re: Protecting read out via OBD
Post by: roman_tyk on December 23, 2015, 09:33:59 AM
Has anybody checked what is under such modification from a2l and funktionsramen??

0F=> 00


Seg0x202@808000:8B06             ; ---------------------------------------------------------------------------
Seg0x202@808000:8B06 00 09                       add     r0, r9          ; Integer Addition
Seg0x202@808000:8B08 0A 0B 0C 0F              bfldl   word_FD16, #0Ch, #0Fh ; Bit Field Low Byte
Seg0x202@808000:8B0C 0D 0E                       jmpr    cc_UC, word_808B28+2 ; Relative Conditional Jump
Seg0x202@808000:8B0C             ; ---------------------------------------------------------------------------


Title: Re: Protecting read out via OBD
Post by: hackish on December 23, 2015, 02:36:57 PM
Some processors support protection. PPC comes to mind. Not so sure nor confident about the ST10. If you really wanted to lock someone out you'd do this and re-implement the flash loader to take an encrypted bin. Unfortunately OEMs are starting to take advantage of protections like this.


Title: Re: Protecting read out via OBD
Post by: nyet on December 23, 2015, 02:39:10 PM
Some processors support protection. PPC comes to mind. Not so sure nor confident about the ST10. If you really wanted to lock someone out you'd do this and re-implement the flash loader to take an encrypted bin.

Nobody here (myself included) makes tunes so amazingly amazing that they warrant protection, IMO

Quote
Unfortunately OEMs are starting to take advantage of protections like this.

The VW emissions farce may change this.


Title: Re: Protecting read out via OBD
Post by: adam- on December 23, 2015, 04:42:40 PM
Nobody here (myself included) makes tunes so amazingly amazing that they warrant protection, IMO

Fuel, boost and timing, innit?


Title: Re: Protecting read out via OBD
Post by: hackish on December 23, 2015, 06:11:49 PM
Nobody here (myself included) makes tunes so amazingly amazing that they warrant protection, IMO

I think the ME7xxx series of stuff is old enough that the market is sufficiently saturated. Now if you had a good tune for a ME17 late model car, that would be worth protecting. Most often companies approach me to have intellectual property developed and protected against competitors. Patching roms to add new features previously not available in the stock strategy is really where its at and these sorts of things are more worth protecting.


Title: Re: Protecting read out via OBD
Post by: mister t on December 24, 2015, 01:03:54 AM
Nobody here (myself included) makes tunes so amazingly amazing that they warrant protection, IMO

Tell that to JHM, apparently their tunes are so amazing that their sales people can't even tell you which kind of parameters they calibrated, you know, 'blah blah blah... intellectual property... blah blah blah...  ::)


Title: Re: Protecting read out via OBD
Post by: Snow Trooper on February 05, 2016, 02:28:20 PM
I think the ME7xxx series of stuff is old enough that the market is sufficiently saturated. Now if you had a good tune for a ME17 late model car, that would be worth protecting. Most often companies approach me to have intellectual property developed and protected against competitors. Patching roms to add new features previously not available in the stock strategy is really where its at and these sorts of things are more worth protecting.

Last sentence is it.