Install the 11.13.0 driver and take backup of C:\Windows\SysWOW64\WkWin32.dll and C:\Windows\System32\WkWin64.dll. We have to replace these DLL's with the 11.13.0 driver DLL's. The DLL's that we working with is wkwin32.dll and wkwin64.dll are placed in SysWOW64 and System32 folder. If we replace Wibukey (DLL) from 11.13.0.0 the dongle will be fetched the FLEXID from both versions. The FlexNet host ID of this machine is ""ĪLADDIN DLL Signature not matched! ] Answer Lmhostid - Copyright (c) 1989-2014 Flexera Software LLC.
With the latest Wibukey, the dongle will not be fetched from FNP 11.13.0.0 kit and throws below error.Ĭ:\11.13.0\圆4_n6-11.13.0.0_v6\圆4_n6>lmhostid.exe -flexid -long If the latest ( version 6.51) is installed from FNP 11.18.2 kit, then the backward compatibility will be supported from 11.14.0 onwards since the backward compatibility issue is fixed to include both the issuer names in 11.14.0. Since the signer name has changed from Verisign to Symantec, the security check that validates the dongle libraries? signatures will fail consequently, all current versions of FlexNet Publisher used with WIBU FlexNet ID 10 dongles will FAIL when end customers upgrade to the latest version of the driver. Wibu was unable to revert to the older version of the digital certificate as it was expiring and they could not get a Digital Certificate from Symantec that used the Verisign name.įlexNet Publisher verifies the dongle libraries against the digital certificate signer and issuer name to provide security and avoid spoofing of the dongle libraries (DLL) With the acquisition of Verisign by Symantec, the latest version of the Wibu dongle driver is now signed using Symantec digital certificate. [FlexNet Publisher 2016 R1 (11.14.0.0) and lower will not recognize FlexNet ID 10 dongle with the latest Wibu dongle driver installed (version 6.32) or the latest ( version 6.51).
FlexNet Publisher and Wibu Dongle Drivers support and backward Compatibility Question
0 kommentar(er)
