Avoid deploying in $HOME/.fmxlinux/

[Mathieu]

Is it possible to avoid deploying libfmux.so in $HOME/.fmxlinux/ dir ?
This behaviour can be considered as a security risk, because the app loads library that resides in a users dir.

I would prefer that my installer deploys manually libfmux.so in a specified dir and that my app loads that library from that specified dir (e.g. same dir as the dir of the current program).

[Eugene Kryukov]

Why do you think this is a secure risk ?

[Mathieu]

This is a report of one of our customer which is at the same time an IT security company :

“The app deploys library in user directory $HOME/.fmxlinux/libfmux-1.39.so. This behavior can be considered as a security risk because the app loads code that can be modified by user. Besides, this force us to reduce the security policy of some of our workstation that prevent this kind of manipulation. Can you put this library in a standard place ?”

That seems relevant to me.

[Mathieu]

Is there any workaround to be able to load libfmux.so from the same dir as the current program?

I think it was the previous behavior (as to say, around version 1.25), wasn't it?

[Eugene Kryukov]

We are trying to find good solution. For now, you can copy FMUX.Api.pas from FMXLinux’s sources to you project dir and change LoadLib as you need.

[Mathieu]

Here is a fix that could be integrated in your source if you find it relevant : if the macro FMUXLIB_LOCAL is defined, fmxlinux loads the lib from the program directory.

You can find the diff and the FMUX.Api.pas from 1.41 version in the attached files.

[Eugene Kryukov]

Thx for the patch, we are preparing our own also. Please do not publish any part of sources next time on public forum.

[Mathieu]

Ok, sorry for that. I forgot the code was available only when we have the licence. So how can we send you some peace of code ?

[Eugene Kryukov]

Just email to [e-mail]