Can you instead of using the single FIR.bikey for all your addons, sign the addon's individually. This is frustrating for Server admins that want to use these mods that use a single key for all.
It creates issues with Signature checking and content control.

Consider how RHS and CUP do their signing. They sign their content individually for better content control and ease of implementation.

In short causes 2 problems:

1. In some cases the server using the newer updated signature checking method (V2), you can't "verify" correctly if you are trying to track down which key file supplied is out of date or causing an issue. Currently when I try loading FIR AWS, it's fine but as soon as I try loading F16 or AV8B2, or any of the other mods, I'm having a signature conflict and I'm not sure which key file is causing it and which one should be used. This is not the only mod that I'm seeing this with that uses 1 key for all.
   
2. Server administrators can not block usage of other mods from being loaded or suggested by ArmA Launcher based on Key. Suggests to player to load all mods they have installed using the same key instead of what's allowed or being used on the server.

Granted could go and create my own signatures based on V2 signing and sign the content that way but that is cumbersome should an update occur. Happens to often.

Please, create a bikey per addon you released.

Examples:

FIR_AWS.bikey
FIR_F16.bikey
FIR_AV8B2.bikey
FIR_A10.bikey
...etc.


So many server admins will thank you that use Signature checking and/or need to control content.

Thanks!! :)