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

Enhancement - Skip n/m keys, or -r rule-based-keycrack #76

Open
jamesyoungdigital opened this issue Nov 19, 2018 · 3 comments
Open

Enhancement - Skip n/m keys, or -r rule-based-keycrack #76

jamesyoungdigital opened this issue Nov 19, 2018 · 3 comments

Comments

@jamesyoungdigital
Copy link

Suppose we just want to either:

Have a crack at a keyspace, but don't care that much if we get it, Just speed it up a bit.

We are serious, and we know that brute-forcing one by one isn't going to work out. We need certain conditions, like skipping n out of m keys, like if we want to gather them in huge batches, and throw out n/m of them. E.g. Gather 1 trillion keys, and use n/m like 50000/100000 to exclude 50000 out of every 100000, maybe according to some kind of rule, instead of just the first 50000, maybe every 2nd key.

Another nice feature/enhancement would be only generating according to rules where we know what the private key will be like. So for example if I generated a gazillion private keys and they all started with 1111 .... then I could use -r 1111 which would specify some algorithm to only compute and try keys in the search space that start with the 1111 bit pattern. Or specify hex, -r 0x1 for tossing away keys that do not start with a 1 bit.

What do you think? Would it be terribly slow, considering it pre-computes then tosses some away, or can it easily just find a way in the case of -r 0x1 use something other than increment key by 1, and still be just as fast?

Thanks!

@brichard19
Copy link
Owner

brichard19 commented Nov 19, 2018

Some of this will be addressed in the next build:

There is a --keyspace option which let's you specify the keyspace.

--keyspace START:END or --keyspace START:+NUM_KEYS

It's a more compact replacement for the existing -s and -r.

There is also a new --stride option where you specify how much to increment by: --stride N so you can skip keys.

@jamesyoungdigital
Copy link
Author

Thanks heaps, I appreciate that.

I have something to share with you, if I could, in private. May I send you an email?

Or you could visit my profile where you can send me an email. I promise I won't hassle you, just a couple of questions and something to share.

... Ah yes, sorry I haven't tipped yet, I wasn't following the date correctly. I get paid today but I won't have BTC to tip until my pay hits my account tomorrow. Thank you!

@brichard19
Copy link
Owner

You can email questions to [email protected]. I really should put that on the main page since so many people ask.

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