You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We created an FMU3.0 Co-simulation using PythonFMU3. Unfortunately, when we unpack the FMU the source code is always visible to the user. This might cause problems in replicating the FMUs and violating the security of the FMU.
Is there any existing solution for this problem? We would be glad if we get support on this issue.
Best Regards
Raj Kumar
The text was updated successfully, but these errors were encountered:
As you are using another library, you might want to ask there.
However, see #221 for a possible solution. However, I have no idea if this can be reverse-engineered easily.
Another approach would be to store the python script as a string variable in the shared library, but this requires per-instance compilation of the native library, which is not wanted for PythonFMU. But one could create a custom solution using e.g. https://github.com/Ecos-platform/fmu4cpp.
Encryption could be another solution, with the key available as an environment variable or similar. But these things are out of scope of this library. Nevermind, this would not work.
Hello Everyone,
We created an FMU3.0 Co-simulation using PythonFMU3. Unfortunately, when we unpack the FMU the source code is always visible to the user. This might cause problems in replicating the FMUs and violating the security of the FMU.
Is there any existing solution for this problem? We would be glad if we get support on this issue.
Best Regards
Raj Kumar
The text was updated successfully, but these errors were encountered: