> ## Documentation Index
> Fetch the complete documentation index at: https://help.freakhosting.com/llms.txt
> Use this file to discover all available pages before exploring further.

# How to Enforce V2 Signatures in Arma 3

> Protect your Arma 3 server from cheaters. Learn how to enforce file integrity using V2 signature verification and manage public bikey files.

## Integrity Check: VerifySignatures

By default, the Arma 3 engine is highly trusting of connected clients. To prevent malicious actors from joining your server with modified `.pbo` files (such as "One Hit Kill" weapon modifications or "Transparent Walls" foliage mods), you must enforce strict signature verification. This system ensures that every file on the player's computer is a bit-for-bit match with the official files signed by the mod developers.

<CardGroup cols={2}>
  <Card title="Difficulty" icon="gauge-low">
    Intermediate
  </Card>

  <Card title="Time" icon="clock">
    5 Minutes
  </Card>
</CardGroup>

***

## Enabling Enforcement

To activate signature checking, you must modify your `server.cfg` file.

<Steps>
  <Step title="Open server.cfg">
    In the [Game Panel](https://panel.freakhosting.com) File Manager, locate and open your `server.cfg`.
  </Step>

  <Step title="Set Verification Level">
    Find the `verifySignatures` property and set its value to `2`.

    ```cpp theme={null}
    verifySignatures = 2;
    ```
  </Step>
</Steps>

<Tabs>
  <Tab title="Level 0 (Disabled)">
    Verification is off. Anyone can join with any modified files. This is a severe security risk for public servers.
  </Tab>

  <Tab title="Level 2 (Strict)">
    The industry standard for MilSim servers. Every mod file must be signed and the server must possess the corresponding public key.
  </Tab>
</Tabs>

***

## The Key System: Managing .bikey Files

For a mod to pass the V2 check, your server must possess its **Public Key** (`.bikey`).

<Steps>
  <Step title="Locate the Mod Key">
    Open the mod folder on your local PC (e.g., `@ACE3`). Look for a sub-folder named `keys` or `serverkeys`.
  </Step>

  <Step title="Extract the .bikey">
    Find the public key file inside (e.g., `ace3.bikey`).
  </Step>

  <Step title="Upload to Server">
    Use the File Manager or SFTP to upload this file to the root `/keys/` directory on your FREAKHOSTING game server.
  </Step>
</Steps>

**Result:** Your server now "Trusts" any `.pbo` file that has been signed by the owner of that specific key.

***

<AccordionGroup>
  <Accordion title="Troubleshooting: Signature Mismatch Errors">
    If players are kicked immediately upon joining with a "Signature Mismatch" or "File not signed by a key accepted by this server" error, check the following:

    * **Missing Key:** You likely forgot to upload the `.bikey` file for one of the mods running on your server.
    * **Outdated Mod:** The player's local mod files may be outdated or corrupt. Instruct them to use the **"Repair Mod"** or **"Verify Integrity"** feature in the Arma 3 Launcher.
    * **Server Version:** Ensure the server's mod files are up to date via the Game Panel's Steam Workshop manager.
  </Accordion>
</AccordionGroup>

***

<Note>
  ### Need Extra Help?

  If you encounter any issues, our support team is ready to assist:

  * **Live Chat:** Quick assistance via our website.
  * **Support Ticket:** [Open a Ticket](https://freakhosting.com/clientarea/submitticket.php)
  * **Discord:** [Join our Community](https://discord.gg/freakhosting)
  * **Email:** [support@freakhosting.com](mailto:support@freakhosting.com)
</Note>

<Tip>
  ### Save on Your Hosting

  Ready to get a new server? Use code **KB20** at checkout for **20% off** your first month!
</Tip>

***

<div align="center">
  **Last Updated:** January 2026 | **Arma 3:** Perimeter secured.
</div>