Eric, you could have a small loader program run which then would
load the rest of your binary as a dylib, using
NSCreateObjectFileImageFromMemory.
The problem is that one of the requirements of my project is that it
not require any recompilation of the wrapped program, which may have
been written previously by another company entirely. Otherwise
making the app load as a dylib that way would be a great solution.
Unfortunately, in my particular case, I have a very stringent set of
rules for what I'm supposed to accomplish:
1. The wrapped application can't be easily retrieved and used outside
the wrapper.
2. The wrapped application can't be required to be altered or
recompiled.
On Windows, this is done by loading the encrypted app into memory
from disk within the wrapper application, decrypting it, then
executing it, but it's not looking like that will work on OS X at
this point, so I need to come up with another solution, I guess.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/darwin-dev/email@hidden
