01 Configuration using config.yaml
What is the conf.yaml file?
The conf.yaml file is a file in the App-Data directory of Maltego Evidence and provides expert users with a variety of settings options. You can find the file under the following path:
%APPDATA%/Maltego Evidence/conf.yaml
Please be very careful when adapting the file and, if necessary, ask our support team before making any changes. The changes made should only be carried out by experts or on the instructions of the support team and can significantly change the behavior of Maltego Evidence.
How is the conf.yaml file structured?
The conf.yaml file is structured in YML format . It therefore makes sense to familiarize yourself with the peculiarities of YAML files before changing settings in the config file.
Which parameters can be changed?
In principle, all parameters can be changed, but the following are most likely to be used by expert users. If there is a "Yes" in the "Create new" column, the parameter is not present by default, but can be inserted to overwrite the specific default value.
| Path | Create new? | Explanation |
|---|---|---|
| services -> backend -> port | No | The port on which the backend is started. It is important that the corresponding value is also adjusted under services -> frontend -> env -> apiUrl after the colon. |
| services -> frontend -> port | No | The port on which the frontend is started. |
| environment -> mariaDB -> port | No | The port on which the MySQL database is to be started. Please also adjust under services -> backend -> settings -> database -> PORT. |
| services -> backend -> settings -> database | No | An alternative database can be connected to Maltego Evidence Desktop here. In addition to MySQL, Postgres and sqlite are also supported. You can read more information about configuring databases in the Django manual . |
| environment -> enableLog | No | You can change this value to "true". Each log message is then written to the file specified above it at startup. However, this slows down Maltego Evidence noticeably. |
| services -> runners -> settings -> chrome_options -> user_agent | Yes | In this value, you can overwrite the user agent that the runners specify in the browser. This can have a massive impact on the collection behavior. |
| environment -> backup_interval | No | Here you can specify the time interval at which backups are to be created (in minutes). |
| environment -> max_number_of_backups | No | Here you can specify how many backups should be kept by default. |
| environment -> backup_dir | No | Here you can specify the path to which Maltego Evidence should save the backups. |
| environment -> proxy | Yes | By default, Maltego Evidence checks for updates at startup and installs the signed update packages if required. If this process is to be carried out via a separate proxy, you can specify the corresponding proxy in this configuration. For example, "https://username:password@my-proxy-server.com:12345" |