Quote from: o_e_l_e_o on Today at 11:53:22 AM

Quote from: despo4helpo on March 21, 2023, 02:23:47 PM

1. My passphrase is all lowercase or all uppercase. If it's all lowercase, then possibly, the first letter of the passphrase OR first letter of each word is proper case. It would have been a pain to do that on the Ledger though so I am hoping it's all lower or upper case. Is there any way to run only those combinations, or do I need to try each casetype as a separate run?

Separate runs. There is no straightforward way to tell it to change the case of your entire token file.

You can put multiple tokens on a single line, and it will only try one from each line, such as:

Code:

Token token TOKEN
Code code CODE

However, there is no way to say "If you pick the lowercase token from the first line, pick the lowercase token from all the other lines too". So you will simply have to make a token file with everything in lowercase, and once exhausted change everything to uppercase, and so on.

Quote from: despo4helpo on March 21, 2023, 02:23:47 PM

2. I'm relatively confident there are certain words, and even the order, and use + in front of those. The other words are in the middle but I'm not certain how the "relative anchor" works.

If you are certain a word appears somewhere, but you don't know where, then use +
If you know the exact position of a word, for example "This is definitely the fourth word", then use + ^4^
If you have three words you think WordA comes first, WordB somewhere later, and WordC later still, then you would use something like this:

Code:

+ ^r1^WordA
+ ^r2^WordB
+ ^r3^WordC

This fixes these word positions relative to each other. WordB will never be tried before WordA, but there could still be other words between WordA and WordB.
If you have three words and you know they are consecutive, then combine them in to a single line like this:

Code:

+ WordA%sWordB%sWordC

The %s will be replaced by a single space.

Quote from: despo4helpo on March 21, 2023, 02:23:47 PM

3. Complicating things more, I may have replaced a's with @, s with $ etc. I have the custom-typos map but that becomes way too many combinations. I think I did it only for the first a or s in a word and not all. I.e., Emb@rra$s

Combine these on the same line to try only one of them at a time. Example:

Code:

Embarrass Emb@rrass Embarra$s Emb@rra$s

Thank you! I'm glad to see you're still active here. I've seen so many posts from you while helping others over the years. Thanks for clarifying about the relative anchors; it's much clearer now!

Do you suggest any other commands to use to reduce the number of variables?
I'm using the latest version of btcrecover.