Faraday-agent-dispatcher

Latest version: v3.4.1

Safety actively analyzes 634503 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 5 of 6

1.4.0

---
* A base_route can be added before the root of the server (e.g:
https://my.company.com/faraday/ as / of faraday)
* Add duration to bulk_create to be set correctly
* The new official executors are:
* [nuclei](https://github.com/projectdiscovery/nuclei)
* reports: local report consumed by faraday-plugins
* Add new flags for nmap executor: `-sC`,`-sV`,`-Pn`,`--script-timeout`,`--host-timeout`,`--top-ports`
* Fix bug nmap and nessus executors to execute with the dispatcher environment
* Fix nmap executor when http(s) scheme passed as target
* [Faraday][faraday] versions: 3.14.0, 3.14.1, 3.14.2

1.3.1

---
* Add proxy setup by HTTP_PROXY or HTTPS_PROXY environment variables
* Fix default report name with the nessus executor
* [Faraday][faraday] versions: 3.12.0

1.3.0

---
* An Agent can post data to multiples workspaces
* The `run` command tries to migrate the configuration to the latest version from
others as the `config-wizard` does
* Improve agent signal management and server disconnection, affecting the exit code
* The wizard page size can be customized (See:
`faraday-dispatcher config-wizard --help` )
* The new official executors are:
* burp
* crackmapexec
* Arachni executor generates reports in /tmp now
* Nmap executor updates use of nmap plugin (byte-string to string response)
* [Faraday][faraday] versions: 3.12.0

1.2.1

---
* Now the dispatcher runs the check commands before running an executor
* Fix error when connects with faraday fails when trying to access with SSL to not SSL server
* Fix error when connects with faraday fails when server does not respond
* Fix error when connects with faraday fails when SSL verification fails
* Fix error attempting to create an executor with a comma in the name
* Now the wizard ask if you want use the default SSL behavior
* Started the process of [documentation][doc]
* The new official executors are:
* arachni
* openvas
* zap
* Nmap executor now acepted multi target
* Fix W3af executor now uses python2
* Escape user-controlled executor parameters in order to prevent OS argument injection (not command injection)
* [Faraday][faraday] versions: 3.11, 3.11.1, 3.11.2

1.2

Not secure
---
* Now we have official executors, packaged with the dispatcher
* Fix error when killed by signal
* Fix error when server close connection
* Fix error when ssl certificate does not exists
* Fix error when folder `~/.faraday` does not exists, creating it
* The new official executors are:
* nessus
* nikto
* nmap
* sublist3r
* wpscan
* w3af
* [Faraday][faraday] versions: 3.11, 3.11.1, 3.11.2

1.1

Not secure
---
* The dispatcher now runs with a `faraday-dispatcher run` command
* `faraday-dispatcher wizard` command added which generates configuration .ini file
* Manage execution_id within WS and API communication
* The route of [Faraday][faraday] ws comunication change from / to /websockets
* Better error management, now shows error and exceptions depending on log levels
* Better management of invalid token errors
* Add ssl support
* [Faraday][faraday] versions: 3.11, 3.11.1, 3.11.2

Page 5 of 6

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.