checksum 8's

slugworth

Senior Member
Messages
336
I noticed on a key posted last night the last checksum 8 was wrong and the key still worked.I figured the receiver doesn't use the 2 checksum 8's and they can be any bytes.I entered the key as xx xx xx 00 xx xx xx 00 where xx are the correct keys and the channel still popped in.
 

dale_para_bajo

Well Known Member
Messages
646
I guess it will depend in the internal implementation of CSA inside of your receiver. Yes many has posted here that in many situations checksum or parities are been ignored by receivers . Instead internal algorithm may repair broken keys.

Same happens in Tanb3rg where by Tanb3rg rules last byte should be 01 but instead most keys posted have 00.
 

kebien

Well Known Member
Messages
1,329
dale para abajo......is correct.
Some receivers and emulators calculate the checksums regardless what's the user input.
Some other receivers do not,so you need to input the correct ones.
 

Motogato

Senior Member
Messages
327
add crypt8 and key with wrong checksum to CSA_B8hxFFh_crypt8_cw6_cache.bin

search key again and you have a valid key with correct checksum.
 

dijitalxyz

Member
Messages
90
I guess it will depend in the internal implementation of CSA inside of your receiver. Yes many has posted here that in many situations checksum or parities are been ignored by receivers . Instead internal algorithm may repair broken keys.

Same happens in Tanb3rg where by Tanb3rg rules last byte should be 01 but instead most keys posted have 00.

maybe this key 00 or key 01 for using

our provider ask to "T 26C5 01 keys is missing"
81 70 28 ED 26 00 00 26 C5 E9 1F 33 4F CC 92 3F 24 21 94 24 92 9E 74 8A FD F3 B3 EA 07 65 81 61 3D 8F 25 C2 C6 56 E6 84 2A EF 78
 
Last edited:
Top