cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Backward compatibility for HASP dongles broken starting FNP-11.16.0

Backward compatibility for HASP dongles broken starting FNP-11.16.0

Symptoms:

Starting FNP-11.16.0, (shared HASP dongle driver and dll's are for version 7.61) the dongle dll's will not be backward compatible for FNP-11.13.1 and older version of clients.

Diagnosis:

 

FNP Toolkit Version

HASP dongle driver (Signed by Thales)

HASP Dll's (Signed by Flexera)

Comments:

====================================================================

v 11.13.1

Version: 6.56

Digest Algorithm: SHA1

VeriSign Class 3 Code Signing 2010 CA

Version: 7.1

Digest Algorithm: SHA1

VeriSign Class 3 Code Signing 2010 CA

 

v 11.14.0

Version: 7.41

Digest Algorithm: SHA1

VeriSign Class 3 Code Signing 2010 CA

Version : 7.4

Digest Algorithm: SHA 256

VeriSign Class 3 Code Signing 2010 CA

FNP-14155
FNP-14401
FNP-11607

Microsoft will soon require SHA-2 (SHA256) signing:
http://social.technet.microsoft.com/wiki/contents/articles/32288.windows-enforcement-of-authenticode...

FNP kept signing 'dll's' with VeriSign to maintain the backward compatibility.

 

In addition to that code wise a check was added (to source code) which allows 'VeriSign' as well as 'Symantec' Issuers during authentication - so that when in future we move from VeriSign to Symantec - backward compatibility is maintained.

v 11.15.1

Version : 7.60

Digest Algorithm: SHA1

DigiCert EV Code Signing CA (SHA2)

Version : 7.6

Digest Algorithm: SHA 256

VeriSign Class 3 Code Signing 2010 CA

 

v11.16.0

Version : 7.80

Digest Algorithm: SHA1

DigiCert EV Code Signing CA (SHA2)

Version : 7.61

Digest Algorithm: SHA 256

Symantec Class 3 SHA256 Code Signing CA

Switched from "VeriSign" to "Symantec"


As enhancement done in FNP-11.14.0 was not in FNP-11.13.1 and earlier, hence once we moved to "Symantec" for signing dll's, those client will fail to detect the dongle - if using v11.16.0 version shared dll's.

 

 Workaround:

For Flex-enabled clients build with FNP toolkit v11.13.1 and older, to have them working seamlessly in a mixed client version environment (v11.14, v1.15 and later), use the latest version (or as provided with latest GA FNP toolkit) dongle driver, but at most the HASP dll's from FNP-11.15.1 toolkit.

Was this article helpful? Yes No
No ratings
Version history
Revision #:
2 of 2
Last update:
‎Jun 17, 2020 04:15 AM
Updated by:
 
Contributors