Get source code from standalone application

I compiled an m-file into a standalone exe Windows file using deploytool and sent it to a customer. After the customer launched the exe file, it created some temporal local files in a hidden (but can be easily revealed in Windows) appdata user folder with some files in it. Amongst these files was an m-file with the same name as my source code. How it is possible? I thought making a standalone application prevents customers to reveal the source code.

[Dave Henning]

I am also curious about obscuring source information in my Windows .exe.

I built my Windows .exe using compiler.build.standaloneApplication(buildOpts)

There are folders and .m filenames in the MCR cache directory are the same as my source tree. However, the files themselves are not readable in either a text editor or a hex editor.

I tried turning on the ObfuscateArchive flag, but that didn't change this.

I tried converting some of the .m files to p-code, but that didn't really change anything. The filenames still showed up in the cache.

Then, instead of using the compiler.build.standaloneApplication() function, I called mcc directly. When I did this, I didn't see anything at all in the MCR cache. Could it have been somewhere else?

When we distribute our .exe we want as little source information revealed as possible. I would prefer not to use mcc, but I will if that's the best approach.

What do people recommend?

Thanks,

Dave

Answer 1

[Walter Roberson]

My understanding is that the .m files will have the help information (leading comments). I could certainly be wrong on this point.