How can I prevent my executable from extracting its code with .CTF??

I try to make an standalone executable for Linux with deploytool (matlab 2010b, MCR_7142). I also need to encrypt it by AxProtector of WibuSystems. Once is encrypted, after a few attempts to launch it(in which I obtained and error of CTF initialization), I found out that it worked when I deselected the "Embed CTF file in execuable" option in settings... The problem is that every time I launch the executable, a 'file_name_mcr' is created containing all the source code. This has no sense as I encrypt the executable for a reason. Is there any way to compile my executable without creating that folder? Thanks!

[OCDER]

Seems like an issue with DeployTool

https://www.mathworks.com/matlabcentral/answers/9345-ctf-file-in-standalone-application

Have you tried using mcc to compile your codes instead?

https://www.mathworks.com/help/compiler/mcc.html

[Isabel de la Peña Mesas]

I think that if the CTF was embedded in the application, the structure folder with source code wouldn't be created... But when I compile it with this configuration I receive an ERROR OF CTF INITIALIZAITON Is this normal? is it impossible to run the executable in OpenSuse with the CTF embedded (after encrypting it)??

Answer 1

[Ran Chen]

Hello, It might because of a corrupted 'MCR_CACHE_ROOT' that causing it fails to extract.

You may set the environment variable 'MCR_CACHE_ROOT' to another location or do a clean up at the default location.

In addition, you may not need to encrypt a standalone application, all MATLAB files are encrypted in the CTF archive using the Advanced Encryption Standard (AES) cryptosystem.

When you choose not to embed the CTF (eg. using '-C' flag in 'mcc'), it would result in CTF to be located at the same level as the application. Then, when running the application, CTF will be extracted at the current folder as you saw. This has no effect of how the encryption works for compiled application since the encryption is on the MATLAB programs but not the extraction mechanism.

[Isabel de la Peña Mesas]

The point is that we need to encrypt the executable and link it to a licensed key(that's why is encrypted by Wibu).

When encrypt, an error 'cannot find CTF archive' appears due to is looking for "<name_of_executable>???.ctf". This is, if the executable is called 'hola', the launcher is searching for "hola???.ctf", being ??? random characters.