> i found than in some African countries the find_kc app not working. Kraken > gives me a lot of potential keys, but the find_kc application does not bring > a match ...
Maybe they are using randomization so you are not actually guessing the keystream. Is there any way to check it against a communication capture with known key? > Maybe i need to roll back more or less than 100 clocks in find_kc? You should always roll exactly the same amount as is the position of your fragment in your burst. This is a standard GSM-spec thing, I don't think it would be possible for the network to alter this. On 22. 04. 19 11:39, Max Parker wrote: > Hello all > i have strange problem with find_kc app > i found than in some African countries the find_kc app not working. Kraken > gives me a lot of potential keys, but the find_kc application does not bring > a match ... > Maybe i need to roll back more or less than 100 clocks in find_kc? > Has anyone met this behavior? > Thnaks > > -- > Best Regards, > Max > > _______________________________________________ > A51 mailing list > [email protected] > https://lists.srlabs.de/cgi-bin/mailman/listinfo/a51 > -- Jan Hrach | https://jenda.hrach.eu/ _______________________________________________ A51 mailing list [email protected] https://lists.srlabs.de/cgi-bin/mailman/listinfo/a51
