Talk:ArmA: Addon Signatures
Since OFPEC has the 'TAGS' database, i advise people to use these tags as identification for your keys. OFPEC Tags : http://www.ofpec.com/index.php?option=com_tags&Itemid=52 --Jerryhopper 15:22, 20 September 2007 (CEST)
Can public tags, be renamed and still work properly? --Jerryhopper 15:37, 20 September 2007 (CEST)
Sometimes I can't sign pbo file through command line use of DSSignFile.exe. It writes an error: "Error: Stored and calculated hash don't match". Everything works, if I use "sign" feature when packing into pbo in BinPBO util. --MessiahUA 23:23, 22 September 2007 (CEST)
I get the same thing as MessiahUA. It must be a bug, but does anyone know how to work around it? --ViperMaul 04:45, 10 October 2007 (CEST)
you need a proper 'prefix-header' file in your pbo you're trying to sign, so recreate the pbo with a proper header and try signing it again... well, that's what i did to resolve the same error and i haven't come across it since. Report back here if that didn't work. -- Sy 06:16, 10 October 2007 (CEST)
To be able to sign your addons, it's best to use the official BIS packing tools. Otherwise you may not be able to sign them --Maddmatt 15:40, 12 October 2007 (CEST)
To explain the compatibility: v2 signatures are extension of v1 signatures.
- v2 signature can be still understood by old servers and clients, but it acts the same as v1 signature there (no new enhanced checks done). This was done to facilitate the transition. When you release an addon which targets both 1.59 and older, you can release it with a single signature. - v1 signatures can be still understood by new versions, but they do not pass when extended test is required by the server (verifiySignatures=2).
The addons should be a lot better protected now with v2 tests, the addon modification should be detected faster and more often.
Should be merged into the article along how to create v2 signatures. --Kju 11:09, 16 May 2011 (CEST)