ARMA 3Security settings help protect your server from modified files, unauthorized mods, and duplicate players. Configure these settings to maintain server integrity.
Configuring Security Settings
- Navigate to the Wabbanode Control Panel and Stop your server.
- Click the Settings tab and select Arma 3 Server.cfg.
- Locate or add the security settings and make any desired changes.
- Click Save and Start your server.
Security Configuration
Add these lines to your server.cfg:
verifySignatures = 2;
kickDuplicate = 1;
allowedFilePatching = 0;
Settings Explained
verifySignatures
Verifies that addon files (.pbo) match their signature files (.bisign):
| Value | Description |
|---|---|
0 | Disabled - no signature verification |
1 | Accept both v1 and v2 signatures |
2 | Only accept v2 signatures (most secure) |
kickDuplicate
Handles players with duplicate IDs:
| Value | Description |
|---|---|
0 | Allow duplicate IDs |
1 | Kick players with duplicate IDs (recommended) |
allowedFilePatching
Controls whether clients can use the -filePatching launch parameter:
| Value | Description |
|---|---|
0 | Block all file patching |
1 | Allow headless clients only |
2 | Allow all clients |
Recommended Settings
Public Server (Maximum Security)
verifySignatures = 2;
kickDuplicate = 1;
allowedFilePatching = 0;
Development/Testing Server
verifySignatures = 0;
kickDuplicate = 1;
allowedFilePatching = 2;
Tips
- Use
verifySignatures = 2for public servers to prevent modified addons - Always enable
kickDuplicateto prevent impersonation - Only enable
allowedFilePatchingfor development purposes
Your security settings are now configured. Your server is better protected against unauthorized modifications and potential exploits.
