Page MenuHomeFeedback Tracker

Latest DSSignfile produces wrong signatures
Assigned, WishlistPublic

Description

The latest DSsignfile utility from Steam seems to have problems with at least one addon that I have been working with and produces bisign files that don't work and are rejected by Arma 3 as incorrect.

An earlier version of the same addon seems to work OK.

After lots of tries I eventually used an older version from arma2.com that was linked to in the forums, and the bisign file produced was correct.

Filesize of the one that doesn't work is 227,328

Filesize of the one that works correctly is 188,416

Copies of bisign files produced by both versions are in the attached zip file and are noticeably different even when opened with notepad ++.

Not sure if it is just a few addons that exhibit the issue or all of them. {F26772} {F26773} {F26774}

Details

Legacy ID
3431501790
Severity
None
Resolution
Open
Reproducibility
Always
Category
Tools
Steps To Reproduce

Try and use DSSignfile on my pbo. If you need a copy of the pbo as well please let me know

Event Timeline

Bravo17 edited Steps To Reproduce. (Show Details)Aug 7 2015, 12:17 AM
Bravo17 set Category to Tools.
Bravo17 set Reproducibility to Always.
Bravo17 set Severity to None.
Bravo17 set Resolution to Open.
Bravo17 set Legacy ID to 3431501790.May 8 2016, 12:29 PM

Hello,

A copy of the given PBO is indeed needed to make some tests ;)

I've been unable to reproduce the issue. Something might be wrong with the authority.
Can you test with a new authority?

It looks like you have to produce a new private key when moving to the new dssignfile, since old private keys produce totally different bisign files when used with the new dssignfile, and vice versa.

Steps I took:

  1. Produce new private key using older version of dscreate
  2. make bisign using that key and old dssignfile
  3. make bisign using that key and new dssignfile.
  4. compare bisign files, they are different.

also:

  1. Produce new private key using newer version of dscreate
  2. make bisign using that key and old dssignfile
  3. make bisign using that key and new dssignfile.
  4. compare bisign files, they are different.

I see, fact is the signature tools which should be used for Arma 3 are in Arma 3 Tools.
The ones provided by BI Tools 2+ are not supposed to be compatible with Arma 3.

I have just tried again with some new authorities and a different pbo, and the files that the new version produces do not seem to work on our server, whilst the ones produced by the old version do work.

Confirmed, a lot of pbo's signed with the newest arma 3 tools fails with ".bisign is wrong. Err 0x20. Test FAILED!", pls fix this ASAP!

We've tested the data contained into newpbosign.zip and for us both old and new worked as expected.

What are you using to pack your PBOs?

I believe it is cpbo.exe, I have a "Create PBO" option on the right-click context menu.

CPBO is an old non-maintained community tool. Can you do a test with PBO packed via Addon Builder?