-
Notifications
You must be signed in to change notification settings - Fork 31
Lost in the permutation logic #15
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
Comments
Hello! Let me take a look and get back to you. For context: ripgen intentionally reuses the logic that dnsgen uses so you'll often see duplicate results as a result. That said, it might be time to migrate towards generating high signal name patterns rather than just an excessively wide net. |
Hmm could you explain what you're looking for me to do here? Do you want it to generate less permutations? Is it not matching dnsgen exactly? |
@d0nutptr sorry for the poorly formatted issue. I am lost in the way ripgen uses permutations, right now it is generating way less permutations than dnsgen and the results are "exponential". like it might generate 20 permutation from a list of 1 host, but 3000 if the list of 10 hosts.
it is following some of the dnsgen logic for permutations but definitely not the same. This generates 0 results:
and in the other hand, dnsgen:
|
hello,
I am getting confused by the way ripgen generates permutations.
3 subdomains generated 23 permutations only.
it is not following the logic dnsgen has (also gives +1000 duplicate results, that's why I am using anew there). Every subdomain you add increases exponentially the amount of results ripgen gives
The text was updated successfully, but these errors were encountered: