>>>>>>>Hi All
>>>>>>>
>>>>>>>I know that there is no protection against crackers who have the skills to dump running executables from memory. However, I am curious if anyone has definitive knowledge of other tools that can directly crack ReFox XI. I have heard of UnFoxAll but not tried it. Is there a known attack / attack tool(s) against ReFox (besides memory dumping against which there is very little protection).
>>>>>>>
>>>>>>>Curious ...
>>>>>>
>>>>>>Is there a specific reason why you're focusing here on Refox? (The same question could be targetted at Molebox, for example.)
>>>>>
>>>>>Memory dumping attacks can be used against them all. I am simply investigating if there is a known and accessible attack against Refox XI, level III branding or whether the only current attacks are dumping the running app out of memory.
>>>>
>>>>Yes Jos, I understand, but why is the curiousity focussed on Refox only? (Personally, I'd be interested in eventual similar attacks against (the most recent version of) Molebox, because that's the package I'm using these days.)
>>>
>>>
>>>What I dont like about Molebox is that you need to include all the VFP dll's in the package. Why can't I just Molebox my VFP exe only and leave the dll out of it.
>>
>>But you can! Personally I see no advantage by including the runtime DLLs. My setup contains them, of course, but as separate files. And they are also NOT encrypted by Molebox.
>>
>>You might download Clickwork, run the setup and see what it creates. Only the main exe and the apps are encrypted by Molebox.
>
>If I add just my VFP exe to the executable field and only the same exe to the package box then my app does not run. What am I missing about Molebox that you can Molebox only your VFP exe and not add any dll files to the package?

I might say RTFM, but I won't. :)
I promise to answer this question this evening. At this moment I do not have access to the molebox source code I use.