Discussion:
Kraken Base10 results
(too old to reply)
p***@openmailbox.org
2016-04-16 20:21:53 UTC
Permalink
Raw Message
Instead of getting results as Hexdecimals, I am getting results as
Base10.
Is that normal behavior? I gather that to decrypt the .cfile, results
need to be directly passed as hex to wireshark or other utils. It's not
a problem to convert it to hex but just another extra step.

I'm using the kraken fork hosted here:
https://github.com/joswr1ght/kraken


Here is the sample result to understand my query:


-------
Kraken> test

Cracking
001101110011000000001000001100011000100110110110011011010011110001101010100100101111111010111100000110101001101011
Found 16027103698477381980x @ 12 #0 (table:340)
Found 8050061555739560956x @ 23 #0 (table:372)


Should have got:

Found de6bb5e60617f95c @ 12 #1 (table:340)
Found 6fb7905579e28bfc @ 23 #0 (table:372)


-------

I'll try to see if I can just:

itoa (i,buffer,16); //;-)

Thanks.

Regards,
Spørgeren
Jan Hrach
2016-04-16 23:49:57 UTC
Permalink
Raw Message
Fragment.cpp:106:
snprintf(msg,128,"Found %016lux @ %i #%i (table:%i)\n", result, mBitPos, mJobNum, mAdvance);

My compiler/stdlib/whatever does not seem to understand %016lux too. Try %016lX.
Instead of getting results as Hexdecimals, I am getting results as Base10.
Is that normal behavior? I gather that to decrypt the .cfile, results need to be directly passed as hex to wireshark or other utils. It's not a problem to convert it to hex but just another extra step.
https://github.com/joswr1ght/kraken
-------
Kraken> test
Cracking 001101110011000000001000001100011000100110110110011011010011110001101010100100101111111010111100000110101001101011
-------
itoa (i,buffer,16); //;-)
Thanks.
Regards,
Spørgeren
_______________________________________________
A51 mailing list
https://lists.srlabs.de/cgi-bin/mailman/listinfo/a51
--
Jan Hrach | http://jenda.hrach.eu/
GPG CD98 5440 4372 0C6D 164D A24D F019 2F8E 6527 282E
p***@openmailbox.org
2016-04-17 20:02:57 UTC
Permalink
Raw Message
I checked the original Kraken source-code (not the fork) and they use
%016llx
Using this gives a warning during the build process but works anyways.
Results are printed in lowercase.

Using %016lX generates no warnings or errors and results are printed in
uppercase. Thanks again.

Maybe this has something to do with the case of 'X' 'x'

Regards,
Spørgeren
Post by Jan Hrach
mBitPos, mJobNum, mAdvance);
My compiler/stdlib/whatever does not seem to understand %016lux too. Try %016lX.
Instead of getting results as Hexdecimals, I am getting results as Base10.
Is that normal behavior? I gather that to decrypt the .cfile, results
need to be directly passed as hex to wireshark or other utils. It's
not a problem to convert it to hex but just another extra step.
https://github.com/joswr1ght/kraken
-------
Kraken> test
Cracking
001101110011000000001000001100011000100110110110011011010011110001101010100100101111111010111100000110101001101011
-------
itoa (i,buffer,16); //;-)
Thanks.
Regards,
Spørgeren
_______________________________________________
A51 mailing list
https://lists.srlabs.de/cgi-bin/mailman/listinfo/a51
Loading...