Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

total keys not calculating correctly when using range #420

Open
digir0n opened this issue Oct 13, 2024 · 2 comments
Open

total keys not calculating correctly when using range #420

digir0n opened this issue Oct 13, 2024 · 2 comments

Comments

@digir0n
Copy link

digir0n commented Oct 13, 2024

Using the following command to scan range 0x70000000000000000 to 0x70010000000000000
./clBitCrack.exe --keyspace 70000000000000000:70010000000000000 1BY8GQbnueYofwSuFAT3USAhGjPrkxDdW9

clBitCrack reports total keys 549743230976 after scan finnished, but this can not be correct

From 0x7000000000000000 to 0x7001000000000000.
There are 16^16 (FFFFFFFFFFFFFFFF in hexadecimal) possible values.
16^16 = 2^64 = 18,446,744,073,709,551,616

@Anwma
Copy link

Anwma commented Nov 14, 2024

I have this same confusion, can someone please answer it for me

@Anwma
Copy link

Anwma commented Nov 14, 2024

Whether the software uses some acceleration technique that reduces the number of keys to find

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants