Currently, the signed binaries folder includes the bits, signed with md5, which is not accepted by our security team as a good signature - so, if there is an option to take it for 12.1.20121.1010 and 13.2.20132.1000?Thanks in advance!BR, Eugene
Hello ,
Thank you for posting. Actually, we more recently upgraded to a 256 digital signature version. We didn't have a 256 signing key back for version 12.1 and 13.2.
But I can request our engineering service team to sign your specific versions 12.1.20121.1010 and 13.2.20132.1000 with the new digital signature to share with you .
May I know which product you are using?
Sincerely,Divya JainAssociate Software Developer
oh, thanks Divya - that would be awesome! I am asking about that specifically for Quest InTrust product
Thank you for the update. i have created a private case CAS-201916-M4Z6L2, through which I will provide you the signed assemblies.
-Divya
we use WPF
Hello,
The 'Quest InTrust' product, might be your product into which you are using out WinForms or WPF assemblies.
So may i know if you are using WPF assemblies or WinForm ? in other words , Which netadvantage product you are using ?