stuck on puredns after generating permutation file :(

[yosif-qasim]

The issue :

The tool is stuck in running puredns it still shows the message " Generating permutation subdomains wordlists which might create a very big file " but after checking the running processes it shows that puredns is running but stuck with no new output being generated for over 6 hours

what i have tried so far :

• halting the process and resuming it
• changing the tactic to aggressive
• running the tool in sudo su
• running the same pure dns command the tool is trying to run (just changed the output files) - the tool worked smoothly and finished in 15 minutes
• as a temporary solution i just commented the command in the probing.yaml file and moved the finished puredns results to replace the incomplete files , the tool is running smoothly from here

/root/osmedeus-base/binaries/puredns resolve /root/workspaces-osmedeus/domain.com/probing/raw-domain.com.txt -r /root/osmedeus-base/data/mics/resolvers.txt --write nonwild-domain.com.txt --write-massdns dns-domain.com.txt  --write-wildcards wildcards-domain.com.txt --wildcard-tests 50 --rate-limit 2000 --bin /root/osmedeus-base/binaries/massdns

Thanks for helping in advance <3

[j3ssie]

It's probably because the thing you put in was really big. Think about trying to run the DNS resolve with that much of a subdomain, especially with your home network.

Try it with a different target or use some of the param flags to disable that feature in probing like
osmedeus scan -t sample.com -p 'enablePermutation=false' -p 'enableDnsBruteFocing=false'

Also, make sure you try with the latest install as I might update some new improvements.

[Green222]

Hey there,

Just wanted to comment that I've been experiencing the same thing.
I was testing multiple workflows for day (on Digital Ocean) but they're always all stuck without ever reaching the vuln scan phase. It seems to be stuck on the exact same step, the massdns bruteforce.

We have around the same size of subdomains, but same thing: if I run the exact same massdns command manually it works great in 10-20 minutes, but in hangs for days in the Osmedeus workflow.

I think there might be an internal issue because it runs fine manually.

No biggie, just my 2 cents.

[j3ssie]

I think the issue might happen with the puredns flag, I mistaken the rate limit flag for the trusted resolver. I've pushed the update already.
try to clean up the old setup with this command rm -rf ~/osmedeus-base ~/.osmedeus and run the install script again then

[Nader-abdi]

I think the issue might happen with the puredns flag, I mistaken the rate limit flag for the trusted resolver. I've pushed the update already. try to clean up the old setup with this command rm -rf ~/osmedeus-base ~/.osmedeus and run the install script again then

I have this problem too. I use the latest version, this problem occurs when the size of the input file increases.

Is there a solution for this problem?