-
Notifications
You must be signed in to change notification settings - Fork 164
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
Regex phrasing throws error #54
Comments
Also, it seems like long regex strings cause crashes. Output of the latter:
|
Scallion can not run the regexes on the GPU. It converts them to a list of strings in https://github.com/lachesis/scallion/blob/gpg/scallion/RegexPattern.cs. We simply did not implement ranges or repeating patterns. If your decent at C# it would be awesome if ya added those features. The other issue you mentioned is a practical bug. Scallion converts a regex to list of strings. If these strings are short (less then 7 or 8 characters) the strings are checked on the GPU. If the strings are long they are checked on the CPU. In your last example, Try the pattern In summary, Scallion was written to find longer patterns. The regex support was added to allow you to search for variations and increase your odds of finding a collision. If you are looking for a shorter pattern don't use regexes because scallion can easily find a short collision. That being said, scallion really should print out a warning if its going to try to check 55125 patterns on the GPU :P |
Hey, thanks a lot. I was looking to get either alphabetic or word-like results, but it seems that this isn't feasible without running many threads because the string list would be massive! I wasn't aware of this, thanks for clarifying. C# isn't something I'm experienced in, so sorry I can't help out. |
For your use case, if you only goal is to get a prefix which follows the pattern "consonant vowel vowel consonant vowel", you're probably better off using shallot, or using scallion with a shorter pattern and the "-c" option and then filtering afterwards. |
I think it's been mentioned before, but I can't find any specific documentation on it. Scallion throws an error when using ranges (i.e.
scallion [a-d]
) or repeating patterns (i.e.scallion [abcd]{3}
). This makes it annoying to find patterned addresses. For instance,scallion [abcd]{3}
needs to be writtenscallion [abcd][abcd][abcd]
to be considered valid.Either a note in the documentation explaining this or an update to the parser would be appreciated.
The text was updated successfully, but these errors were encountered: