have a problems with v2 sign.
Addons packed with cPBO and signed with DSUtils2 rejected by the server with wrong signature.
Addons packed with BinPBO and signed with DSUtils2 are good.. but some of addons wont work after BinPBO repack (even without binarize) - for example "celle" island... it says about missing \ca\celle\celle.wrp when I start the server.. also there is no island visible even in editor...
Also signs v2 for almost every old addons wont work without repacking with BinPBO
Maybe I missed something?
P.S. of course I placed .bikey file in arma2\keys directory.
Many pbos are packed with OFP/a1 tools that make the signature generation not possible / faulty.
The reason why Celle and other addons don't work after repack is because you need to apply the same pboprefix, for Celle this seems to be ca\celle
Perhaps better to ask the original authors to sign with v2.
A repack with mikero's tools should do the job.
The reason the wrp is not the in the pbo is the binpbo settings.
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.
Ondrej Spanel, BIS Lead Programmer
For newer engine versions it provides more information and security.by old servers and clients
For older versions you need the older signature files.