Closed waelahmed-dev closed 2 years ago
I think there's some issue with your amass try running your garud using and check where you get stuck and then let me know will fix it then. Also please share your vps specs and env
Command:
$ bash -x /usr/bin/garud -d target.com
this is the result:
my vps specs: 2 GB RAM, 1 vCPU, 60 GB SSD Node.js
I don't think that it has an env, it's amazon lightsail instance Actually, the cpu usage is fixed at 100% while the tool is running, so does it require higher specs?
Yes it requires higher specs to work faster but the specs you mentioned here is okay. Try using Amazon EC2
instance I have no idea about Amazon Lightsail coz I have never run garud on it. Actually the issue is with the amass try commenting out the amass scans I'm pasting the line number and code below.
Run garud like this (use screen
to let it run in background)
$ env bash
$ garud -d target.com
Line 146
# amass enum -passive -d $DM -o .tmp/amass.list &> /dev/null
Line 153
# timeout 50m amass enum -active -brute -w ~/wordlists/subdomains.txt -d $DM -o .tmp/amassact.list &> /dev/null
This is my first time using the tool. I just get stuck at subdomain scanning, I tried to leave it for about 3 hours and it was still stuck at the same phase, even I can't cancelling it by hitting
ctrl + c
, it won't cancel until I close my vps windowAny ideas where is the problem? Thanks in advance.