This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- FlexNet Embedded
- :
- FlexNet Embedded Knowledge Base
- :
- Binscope 2014 Failures seen in FlxComm64.dll, FlxConnect64.dll, and FlxCore64.dll
Subscribe
- Mark as New
- Mark as Read
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
Binscope 2014 Failures seen in FlxComm64.dll, FlxConnect64.dll, and FlxCore64.dll
Binscope 2014 Failures seen in FlxComm64.dll, FlxConnect64.dll, and FlxCore64.dll
Summary
Binscope 2014 Failures seen in FlxComm64.dll, FlxConnect64.dll, and FlxCore64.dllQuestion
We ran the BinScope-2014 tool against the 2018.02 FNE DLLs and observed DefaultGSCookieCheck failed.Apart from the DefaultGSCookieCheck, the following checks also fail:
ATLVersionCheck
ATLVulnCheck
CompilerVersionCheck
GsCheck
GSFriendlyCheck
GSFunctionSafeBufferCheck
RSA32Check
VB6Check.
Is this expected?
Answer
The checks failed as the ?pdb? file for the corresponding dll?s were not used. The results are as expected. If you run Binsope 2014 against the FNE 2018.02 kit for FlxComm64.dll, FlxConnect64.dll, and FlxCore64.dll, you'll get the expected results. In summary, the tests fail because you don't have our debug symbols.
No ratings