Server
The Server configuration is managed via empire/server/config.yaml.
Once launched, Empire checks for user write permissions on paths specified in config.yaml
. If the current user does not have write permissions on these paths, ~/.empire
will be set as fallback parent directory and the configuration file will be updated as well.
suppress-self-cert-warning - Suppress the http warnings when launching an Empire instance that uses a self-signed cert.
api - Configure the RESTful API. This includes the port to run the API on, as well as the path for the SSL certificates. If
empire-priv.key
andempire-chain.pem
are not found in this directory, self-signed certs will be generated.
database - Configure Empire's database. Empire defaults to SQLite and has the ability to run with MySQL. For more info on the database, see the Database section.
SQLite - The location of the SQLite db file is configurable.
MySQL - The url, username, password, and database name are all configurable.
The defaults block defines the properties that are initially loaded into the database when it is first created.
plugins - Auto runs plugins with defined settings. This tells Empire to run a set of commands with the plugin at server startup.
directories - Control where Empire should read and write specific data.
logging - See Logging for more information on logging configuration.
submodules - Control if submodules wil be auto updated on startup.
Last updated