owasp-amass
Amass enum hangs with "Enumeration exceeded provided timeout"
Sometimes during an enum run it will not exit and "hang". Final entry in log is always "Enumeration exceeded provided timeout".
Same here—the timeout specified via commandline doesn't appear to work; I have to manually send a SIGKILL, not even SIGTERM will kill it
@dan-processbolt @eur0pa Are you still experiencing this with version 3.10.5?
seeing this also, i'm on version 3.10.5
another symptom is running amass enum from another shell hangs without any stdout or stderr until the prev process is killed (SIGQUIT worked). this is odd because running from another shell is a new process hierarchy (the 2 amass process have distinct session leaders) and i'd expect amass to not have any side-effects if the code adhere's to expected characteristics of processes in Linux (i.e. each is session id == process id so neither should effect the other)
@chrisdlangton A local graph database can only be accessed from one instance of Amass at any given time
I'm experiencing this on 3.13.2, on either the pre-built linux amd64 binary or building it using go.
Example command:
amass enum -v -d indeed.com -config amass0a.ini -o indeed-0a.txt -timeout 1
Even with only 1 minute timeout, it still hangs hard with no debug output, forcing me to kill -9 it.
@chrisdlangton A local graph database can only be accessed from one instance of Amass at any given time
maybe an artificial constraint of the application design, but OK..
I've actually found a neat trick, just firejail the amass install. Similar to a container, only far simpler.
I have some ideas for how this can be addressed. I'll see what I can do about it