dade

Update as per the result of [this thread](https://twitter.com/0xdade/status/1323709284387942400) - Do not use NMAPDIR environment variable but instead use `~/.nmap/scripts` to achieve this. This will be both more reliable and easier...

The primary concern with this idea is that the agent container (which handles communication with the server and orchestration of the sub-components) now can control the entire docker api, which...

Heh, we do already base64 the images as part of the blob across the wire so that everything needed for a scan to be processed is included in a single...

The user-based agent enrollment is based on a community model of Natlas (e.g. natlas.io) where agents are indeed enrolled by individual users and when a user gets removed for whatever...

Whatever you have set for ELASTICSEARCH_URL is not a valid elasticsearch cluster.

Bumping this with a "reverse the sort order of results"

Temporary workaround can be a cron job on the host that does something like: ``` docker exec natlas_agent find /tmp -name aquatone-chrome\* -type d -mmin +60 -delete ```

This hasn't been touched in almost a year, but it looks like the best way to do this is going to be to make use of `nmap --script-help ` which...

Alternatively we should probably just hard fail the agent if we parse the `.nmap` file and get the strings: `NSE: failed to initialize the script engine:` as well as `/usr/bin/../share/nmap/nse_main.lua:821:...

I'll need to look into this further, it's generally not safe to blanket add the ProxyFix to all deployments because if there's no proxy involved then X-Forwarded* could be values...