Configuration

Configuration

RAVEN C2 is configured primarily through the server.properties file located in the project root, along with optional runtime CLI flags (see Command Line Arguments).

server.properties

This file controls the core runtime behavior of the C2 server, such as bind address, port, and protocol settings. Edit it before starting the server to persist your configuration across runs.

Tip: Keep a backup of your working server.properties before making changes, especially in production red-team environments, so you can roll back quickly.

Typical Settings Covered

While exact keys depend on the version in your checkout, configuration in this file generally maps to the same settings exposed as CLI flags:

Setting Area	Description
Bind address	Interface/IP the C2 server listens on
Port	Port used by the Web Panel / listener
TLS / mTLS	Whether mutual TLS is enforced for agent connections
Protocol mode	Single-protocol vs multi-protocol (Meterpreter-compatible) handling

For the authoritative list of current keys, always check the server.properties file shipped in your cloned branch, since it is the source of truth and may evolve between releases.

Precedence

When both server.properties and a CLI flag are provided, CLI flags override file-based configuration for that run. Use server.properties for persistent defaults, and CLI flags for one-off overrides or scripted deployments.

Recommended Workflow

1. Clone the repo and locate server.properties in the project root.

2. Set your bind address and port for your engagement environment.

3. Enable mTLS if agents will authenticate via certificates (-T, --mtls).

4. Start the server and confirm it binds correctly:

   java -jar target/raven.jar -S 0.0.0.0 -p 5000

5. Adjust and restart as needed — most settings require a server restart to take effect.

See Also

• Command Line Arguments
• Certificate Management
• Security Features