I'm experiencing another related issue for which I'm not able to find a secure solution:

The app I'm protecting is using ShellExecuteEx (mainly on PDFs). Since I have to
enable the "share virtual system to child processes", those PDFs will be opened
in processes that have access to the virtual box ...

Thank you, this worked for me!

I could swear that I have tested this already, but I believe I've chosen the "Advanced input"
feature instead of protecting the wrapper DLL with a separate Enigma project.

Best regards

But to clarify, why you can't just protect the executable you are running as a child process? What is the problem to do that?


Because there is only one executable file involved. There *might* be ways
to handle this by providing several *.exe with different file names side-by-side,
but Chromium ...

I've managed to put a tiny standalone test case together. Albeit tiny, the download would be quite large (17MB)
due to the dependencies.

Please let me know if you need it and how to send you the download link.

Alec, the protection/boxing is working perfectly. I had to check the "[x] Share virtual system to child processes"
option though. Standalone (w/out Enigma) the app is working as expected. The calls to enigma_ide.dll
fail softly as described below.

enigma_ide.dll is invoked via "node-ffi" which in ...

Hi Enigma Team,

While trying to protect an app written for node-webkit (a shell based on Chromium & Node.js
for developing desktop apps in HTML5) I found out that Enigma isn't exposing its API to
new child processes spawned from the same protected executable image:

app.exe:
--> CreateProcess("app ...