Four Servers - Signatures on two

[colinm9991 20]

I have four servers I am hosting dedicated which I am enabling signatures on after recently getting a lot of problems via the arma2oaserver.rpt file.

How would I allow ACE, CBA etc on one server, and no mods on another?

I understand that for this to work you put the keys in to the Keys folder in ArmA's main folder so that's what kind of confuses me.

If all keys are in one folder then wouldn't this be the case

Instead of what I want, which is this,

Where keys #1 #2 #3 and #4 are the different folders with keys required only for that server.

For example, Keys #2 would be ACE, ACEX, CBA, JayArmA2Lib_new etc.

[killswitch 19]

I'm not sure what the problem is. You are running four Arma servers. Therefore, if they are all hosted on the same machine (computer), you would have four separate copies of the Arma game installation and thus four different Keys folders. You then have something like in your second picture. The first server has the key files needed for the zombies. The second server, in another folder, has a set of ACE-related keys in its Keys folder and so on.

In other words: something like below. You have made four copies of the Arma game files in C:\games and named them accordingly. In each of them, there are the usual game data folders such as Addons, Common, Dta, Expansion and of course a copy of arma2oaserver.exe in each folder. Furthermore, each of them has a Keys folder you can customize:

C:\games\Zombie_Server\Keys     <-- Zombie-related .bikey files goes here
C:\games\ACE_server\Keys    <-- ACE keys
C:\games\I44_Server\Keys    <--- I44 keys
C:\games\Vanilla_Server\Keys   <-- The two stock BIS .bikey files only

Edited July 11, 2012 by Killswitch

[colinm9991 20]

Four game installations?

It is one installation, which is ArmA 2, Arrowhead, PMC and BAF (Though PMC and BAF are moved from the root folder to stop them loading full on servers)

The servers are on my fifth drive and I run them via batch by pointing to that drive, and depending which batch it is, it points to the certain folder (Example: ACE Server points to the ACE folder and reads the config files from there, but also stores logs and .rpt files)

All servers run the server from the expansion/beta folder which is saved on my third drive as are all of my modifications.

The game is on my main Solid State Drive.

[killswitch 19]

No, not four game installations. You just make several copies of the one installation.

[colinm9991 20]

No, not four game installations. You just make several copies of the one installation.

Ah, no. I don't do it that way.

Is that the only option I have?

[killswitch 19]

Is that the only option I have?

Yes...well, one could experiment with symlinks to minimize the amount of data that needs to be copied. Your goal is four server copies with different Keys folders. Edited July 11, 2012 by Killswitch

[colinm9991 20]

Ah, this is my first time hearing about symlinks.

I'll create 3 copies on my third drive and use them until I learn more about symlinks and how to work around that area.

[colinm9991 20]

Sorry for the double post.

I've done the above method of separate game folders for separate servers.

Now on the ACE server, with signatures enabled, upon joining the game I get this error

Warning Message: Files "E:\ArmA\@FOG\addons\carraigdubh.pbo", "E:\ArmA\@FOG\addons\carraigdubh_obj.pbo", "E:\ArmA\@FOG\addons\sg_ira.pbo" are not signed by a key accepted by this server. To play on this server, remove listed files or install additional accepted keys.

The server keys for carraigdubh and sg_ira are in both the modifications "Keys" folder and the arma 2 root folder Key's section, however the signatures are named "sg.bikey" instead of "sg_ira.bikey" so should that matter or not?

[colinm9991 20]

Sorry for the bump folks, still requiring assistance with the signature checks as stated above.

[killswitch 19]

Ask the addon authors for the correct v.2 .bisign and .bikey files for those addons. Unfortunately, it is not uncommon that addon makers fail to get their addons signed correctly... The .bikey files should be in "the arma 2 root folder Key's section", not in 'the modifications "Keys" folder'.

Edited July 15, 2012 by Killswitch

[colinm9991 20]

Ask the addon authors for the correct v.2 .bisign and .bikey files for those addons. Unfortunately, it is not uncommon that addon makers fail to get their addons signed correctly... The .bikey files should be in "the arma 2 root folder Key's section", not in 'the modifications "Keys" folder'.

The server runs on v1 signatures as the majority of addons are v1 still.

For the server the signatures in the root Keys section, however for clients the Keys are in the modifications Keys section which is read when they connect to the server.

[killswitch 19]

V. 2 .bisign files are backwards-compatible with v1 signature checking. Download the BIS signing tools from DSUtils_2 and use the DSCheckSignatures.exe tool to verify that the troublesome addons have correct signature files.

For your setup, that means running something like this in a command window (cmd.exe, "DOS prompt")

C:\path\to\DSCheckSignatures.exe E:\ArmA\@FOG\addons\ E:\ArmA\Keys

For the server the signatures in the root Keys section, however for clients the Keys are in the modifications Keys section which is read when they connect to the server.

The addon signatures (*.bisign files) should be where the addons are. The Keys folder on the server should have *.bikey files.

Edited July 15, 2012 by Killswitch