DSutils v2 release (signatures)

[Kochleffel]

Yep. Every addon has to be signed again with the new tool to get a v2 signature.

The main question is how to achieve this - especially for addons that have their author left the scene.

Hint: Something along the lines of a community sign server - an automated system.

i resigned all mods for our community with V2 Key´s and gave out the serverkey´s aswell.

i wont waste time with waiting for author.

[GregRUS]

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.

[.kju [PvPscene]]

Use eliteness/makepbo.

Many pbos are packed with OFP/a1 tools that make the signature generation not possible / faulty.

[Sickboy]

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.

[.kju [PvPscene]]

A repack with mikero's tools should do the job.

The reason the wrp is not the in the pbo is the binpbo settings.

[Suma]

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.

[Defunkt]

- 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.

This makes me wonder why all BIS pbo's now have two keys/signatures?

[.kju [PvPscene]]

by old servers and clients

For newer engine versions it provides more information and security.

[Sickboy]

For newer engine versions it provides more information and security.

But Suma just explained that v2 keys work fine on older versions of the game too, so seems a valid question to ask why there are double signatures for original files.

[.kju [PvPscene]]

For older versions you need the older signature files.