From Bohemia Interactive Community
|
|
| Line 17: |
Line 17: |
|
| |
|
| |NOTES= | | |NOTES= |
| ====DSCreateKey / DSCheckSignatures ver 2====
| |
| Copyright (c) 2007–2011 Bohemia Interactive a.s. All rights reserved.
| |
|
| |
| For more information about ArmA digital signatures system please visit http://community.bistudio.com/wiki/Armed_Assault:_Addon_Signatures
| |
|
| |
| This tool is released for addon makers in order to allow them to generate their own digital signatures (private and public keys) to be used for signing data packages for Arma 2 / Arma 2: Operation Arrowhead.
| |
|
| |
| ====DSCreateKey====
| |
|
| |
| Usage: DSCreateKey
| |
|
| |
| It will generate private and public keys (authorityname.biprivatekey authorityname.bikey ).
| |
|
| |
| Authority name is the name of signing authority, usually the author of addons to be signed. Using TAG is recommended practice. The name itself serves only to identify the group.
| |
|
| |
| IMPORTANT: Make sure to protect your private key well. Only public keys can be distributed with your content to public.
| |
|
| |
| ====DSCheckSignatures====
| |
|
| |
| Usage: DSCheckSignatures
| |
|
| |
| The utility will verify if all files in the given directory are signed by one of keys from the keys directory.
| |
|
| |
| ====DSSignFile====
| |
|
| |
| Usage: dsSignFile private_key_filename file_to_sign_filename
| |
|
| |
| The utility will generate signature for file using given private key.
| |
|
| |
| ====Signatures On Game Servers====
| |
|
| |
| It is recommended to configure game server to require version 2 signatures using server.cfg:
| |
|
| |
| verifySignatures = 2; //1 = sigVer1 allowed, 2 = at least sigVer2 needed
| |
|
| |
|
| |LICENSING= | | |LICENSING= |
Revision as of 12:28, 29 April 2011
