BIsign/Bikey Not Passing Signature Verification

I recently signed a friend's addon using DSsignFile. I created the private key, bikey and signed all the PBO. Even though I have the exact versions on both client and dedicated server the server fails to verify the signatures and kicks the client whilst adding in the logs "Wrong Signature for addon".

How can this possibly the case if the PBOs, Bisign and bikeys are identical and created from the same private key? Is this a bug? I used ArmaTools.

try with this https://community.bistudio.com/wiki/DSCheckSignatures

if your friend's pbo is not make correctly signature wont work. ( old tools or problems inside pbo )

try with this https://community.bistudio.com/wiki/DSCheckSignatures

if your friend's pbo is not make correctly signature wont work. ( old tools or problems inside pbo )

I'm wondering if it's because the addons have been signed before by the original creator. With the permission of the original addon creator, my friend has simple re-skinned the original content and released a pack or other people's work with their permission.

I'm wondering if the PBOs can only be signed once to prevent hackers editing content and resigning it.

no, you can resign every pbo. simply bikey are not the same. 90% it's a creation fault with tool used or options

I'm totally stumped. I've opened and examined the bikeys in notepad and they're identical :/

*** Update ***

I found the problem. It was an Microsoft Office security feature blocking files that I had copied/pasted from the client to the server using the remote desktop. Problem now sorted :)