search

owasp-amass / amass

In-depth attack surface mapping and asset discovery
https://owasp.org/www-project-amass/
Other
11.75k stars 1.86k forks source link

Option to disable use of graph database. #797

Open nil0x42 opened 2 years ago

nil0x42 commented 2 years ago

Hi ! The way i use amass might be different from common behavior, but still, having a mandatory graph database is killing my disk IO.

In the past, i used -nolocaldb, which, despites triggering high RAM usage regularly was way better for my disk IO. Now, i need to use /dev/shm as -dir to force in-memory database.

But what i would like really, is ability to completely disable usage of graph database, even if that would make amass print duplicate entries (i use amass with -passive mode).

Would you consider adding a -nographdb option ?

nil0x42 commented 2 years ago

If it can be useful to someone, i bypass lack of nographdb option by using /dev/shm/ as amass directory:

mkdir -p "/dev/shm/amass"
rm -rf /dev/shm/amass/*
amass enum [options] -dir "/dev/shm/amass"

That way, a brand new indexes.bolt file will be created in shared memory each time i run amass, instead of ruining my disk i/o

molitona commented 2 years ago

you solved lots of shitting trouble for me!! thank you.