You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Just wondering if I'm a) using the tool correctly and b) if the average keyspace needed to be searched for an n-length string is known.
I'm running the program like this: ./vanity-ssh-keygen_0.3.6_linux-amd64 --matcher="ignorecase-ed25519" --key-type="ed25519" --output-dir="./discovered-keys" string
At first I entered a string 9 characters long, but after searching over 72 billion keys I gave up. Shortened it to 6 characters and just updated from 0.3.5 (which did the 72 billion keys) to 0.3.6. The recent version is also giving occasional errors about not being able to connect to localhost:4318/v1/metrics.
Do I have the arguments correct? I essentially want to find an ed25519 key with the given string, no matter the case of each individual letter. I also have not been putting the string in quotes, not sure if that's necessary or not.
The text was updated successfully, but these errors were encountered:
Hello there, You're using it correctly but I'm sorry to tell you that I found a bug in that matcher 😿.
Also make sure that the search string is in the base64 space.
Regarding time I recently found a 6 character string in about 20 million keys.
I will fix the bug and also invert the metric reporting so that it's turned off by default.
Aha, just tried again without that matcher and it found a match within a minute. I can't believe I left it running for like 4 days, heh. Oh well. Looking forward to the bug fixes!
Just wondering if I'm a) using the tool correctly and b) if the average keyspace needed to be searched for an n-length string is known.
I'm running the program like this:
./vanity-ssh-keygen_0.3.6_linux-amd64 --matcher="ignorecase-ed25519" --key-type="ed25519" --output-dir="./discovered-keys" string
At first I entered a string 9 characters long, but after searching over 72 billion keys I gave up. Shortened it to 6 characters and just updated from 0.3.5 (which did the 72 billion keys) to 0.3.6. The recent version is also giving occasional errors about not being able to connect to localhost:4318/v1/metrics.
Do I have the arguments correct? I essentially want to find an ed25519 key with the given string, no matter the case of each individual letter. I also have not been putting the string in quotes, not sure if that's necessary or not.
The text was updated successfully, but these errors were encountered: