SciChart® the market leader in Fast WPF Charts, WPF 3D Charts, iOS Chart, Android Chart and JavaScript Chart Components

0
0

Hello dear SciChart team,

Our customer has a new security program that starts on Dlls that are copied into a directory during runtime. At the moment has the customer the problem that this security program starts on an AbtLicensingNative.dll. This DLL is in the following directory:
% USERPROFILE% \ AppData \ Local \ SciChart \ Dependencies \ v.6.2.1.13304 \ x64.

For this reason the following questions:
Is this DLL safe?
Why is the dll only copied at runtime? Is there another solution for this?

best regards
Silvester

Version
v.6.2.1.13304
WPF WPF   Licensing   runtime
Share
  • You must to post comments
Filter
Sort by: Most Votes
0
0

Hi Silvester

Writing the files at runtime is the only way that this can be done right now, however you can specify where to write the files too and add an exception to anti virus software.

Try this code before any SciChart library code is called:

SciChart.Core.NativeDllLoader.DependenciesPath = "C:/Temp"; // Or a directory of your choice

Now instruct the user to set an exception in their antivirus for c:/temp

Please let me know if that helps,

Best regards,
Andrew

  • Silvester Schneidt
    Thanks Andrew for quickly info. I forwarded your response to the customer. They answered me that their main concern is that such dlls are digitally signed. Then the DLLs are accepted by the safety program. I’ve looked at the DLL on my computer and it actually doesn’t have a digital signature. Is it possible or is it planned to sign the licensing dll at some point? Best regards Silvester
  • Andrew Burnett-Thompson
    Hi Silvester, I can look into that for you. Are you able to try the suggested solution? It may take us some time to investigate and deploy a signed version of the C++ dlls.
  • Nassim Tinkicht
    Hi Andrew! I encountered the same issue. In my case, this dll is blocked by Device Guard on Windows 10. Unfortunately, there is no Directory-based exclusion policy with Device Guard. As I understood, this dll is generated at the runtime, which makes any Hash-based exclusion impossible. Also, the fact that this dll isn’t signed makes it worst. Did you plan to do anything about it ? Right now we are obliged to rollback to 5.3 version. And we can’t upgrade to 6.3 because of this. Really problematic…
  • Andrew Burnett-Thompson
    Hi Nissim, are you an active support-subscription customer? If so it might be good to setup a call with our dev team and try to understand more about the problem. If we can replicate your security setup and understand the problem more clearly (difficult to do I know), we can come up with some solutions. Please contact us by emailing sales [at] scichart.com. Mention this conversation as another staff member might pick it up, we can schedule a call and get it seen by our dev team. Then — we can find a solution :) best regards, Andrew
  • You must to post comments
Showing 1 result
Your Answer

Please first to submit.