Timeline for Identification of RF hash algorithm
Current License: CC BY-SA 4.0
18 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Jan 14, 2019 at 8:27 | history | edited | fgrieu | CC BY-SA 4.0 |
Removed some broken remarks, while I repair them
|
Jan 11, 2019 at 14:36 | history | edited | fgrieu | CC BY-SA 4.0 |
Revised
|
Jan 11, 2019 at 14:28 | comment | added | fgrieu | @Babud Imre: indeed, CRCs are fine to protect message integrity against random errors, but not intelligent attacks. No affine function does. That standard cryptographic fact is sometime overlooked. I'm still puzzled: I reverse-engineered many 16-bit CRCs, but never found one that deviant! My guess is that it is (bad) custom crypto, or due to some alteration in the capture process (though I can't figure one with this effect) | |
Jan 11, 2019 at 14:16 | comment | added | 0x6261627564 | Thank you much for your time, I really appreciate that. I started to looking for the additional parameters of CRC algorithm with 0x1021 polynom again, but I accepted your answer because this 'lookup table' solve the problem easily. I would never have thought that it is possible to recreate the hash in such an easy way. In general it means if only few bits changes in a messages and/or the protected message is too short (like a CAN message) then we can easily manipulate any affine functions. According to my automotive experience it could be a serious hazard. I'll create additional logs. | |
Jan 11, 2019 at 13:42 | vote | accept | 0x6261627564 | ||
Jan 11, 2019 at 12:24 | history | edited | fgrieu | CC BY-SA 4.0 |
Polish
|
Jan 11, 2019 at 12:13 | history | edited | fgrieu | CC BY-SA 4.0 |
Polish
|
Jan 11, 2019 at 12:06 | vote | accept | 0x6261627564 | ||
Jan 11, 2019 at 13:42 | |||||
Jan 11, 2019 at 12:03 | history | edited | fgrieu | CC BY-SA 4.0 |
Polish
|
Jan 11, 2019 at 10:44 | history | edited | fgrieu | CC BY-SA 4.0 |
Add link to the data sheet (version 2.0). Polish definition of affine.
|
Jan 11, 2019 at 8:24 | history | edited | fgrieu | CC BY-SA 4.0 |
Polish
|
Jan 11, 2019 at 8:16 | history | edited | fgrieu | CC BY-SA 4.0 |
Polish
|
Jan 11, 2019 at 8:10 | history | edited | fgrieu | CC BY-SA 4.0 |
Polish
|
Jan 11, 2019 at 8:03 | history | edited | fgrieu | CC BY-SA 4.0 |
More
|
Jan 10, 2019 at 18:37 | comment | added | 0x6261627564 | Thank you very much for your effort. I read your post several times in the past few hours and after every iteration it gives me more and more details how can I reverse a CRC function. Awsome, I learnt a lot. :-) | |
Jan 10, 2019 at 18:20 | history | edited | fgrieu | CC BY-SA 4.0 |
Polish
|
Jan 10, 2019 at 18:15 | review | First posts | |||
Jan 12, 2019 at 1:37 | |||||
Jan 10, 2019 at 18:11 | history | answered | fgrieu | CC BY-SA 4.0 |