Breau.P 10 Posted September 26, 2019 I created my bikey with the Create Key option from DSUtil I sign my mod file with DSUtils choosing option force V2, I put my public key in my server Keys folder and check V2 in the config when users joins (me) it still says the mods are not sign by the server. I run check signatues from DSUtils and get Warning: Signature D:\Steam\steamapps\common\Arma 3\@mod\addons\modname.pbo.wasaaaa.bisign is deprecated! for each mod in my pack Is there another way to do this ? I havent sign mod since last year, also I read online there is a new V3 available from this forums ? but in the DSUtil there is only Force V2 on there. Thanks for any help Share this post Link to post Share on other sites
Dedmen 2590 Posted September 26, 2019 I don't know what you want. 1 hour ago, Breau.P said: I sign my mod file with DSUtils choosing option force V2 You are forcing it to use the old deprecated V2 signatures And the wonder that you get the 1 hour ago, Breau.P said: Warning: Signature X is deprecated! warning, while forcing the deprecated v2 signatures? Share this post Link to post Share on other sites
Breau.P 10 Posted September 26, 2019 ok so yes it make sense not to force V2. But if I don't force V2 there is only 1 as an option based off this https://community.bistudio.com/wiki/server.cfg it says 1 is deprecated but now 2 is deprecated .... so I just put 3 in the verifysignature ? does not mention it on the wiki which is probly out of date. Share this post Link to post Share on other sites
Dedmen 2590 Posted September 27, 2019 10 hours ago, Breau.P said: ok so yes it make sense not to force V2. But if I don't force V2 there is only 1 as an option What? No. v1 is not supported at all anymore. It should default to v3. 10 hours ago, Breau.P said: so I just put 3 in the verifysignature ? No. That has absolutely nothing to do with the config entry. As the wiki that you linked correctly says. Only 2 and 0 are valid. So if you want it enabled, set it to 2. Share this post Link to post Share on other sites