Anyone with a debugger and minimal knowledge of assembly can crack and patch
your executable in 15 minutes. I used to do it myself when I was 16. Instead of
wasting time on this, focus on making your application better.
-- ank
On 09/10/2012, at 12:15 PM, Alexander Bokovikov wrote:
>
> On Oc
Il giorno 09/ott/2012, alle ore 03:15, Alexander Bokovikov
ha scritto:
>
> On Oct 9, 2012, at 1:00 AM, Simone Tellini wrote:
>
>>
>> this is way overkill. You can simply write a simple utility to dump the
>> content of your resource in a C file:
>>
>> static char foo[] = {
>> 0x01, 0
On Oct 9, 2012, at 1:00 AM, Simone Tellini wrote:
>
> this is way overkill. You can simply write a simple utility to dump the
> content of your resource in a C file:
>
> static char foo[] = {
>0x01, 0x02, 0x03,
> ...
> };
>
> You don't need to use assembly nor to create bogus functio
Il giorno 08/ott/2012, alle ore 04:23, Alexander Bokovikov
ha scritto:
> As a result, you'll have the address of the embedded information in the eax
> register. I.e. you just need to create the function declaration like this one:
>
> (void *) myFunc(void);
>
> and call it. Hope this code i
On Oct 7, 2012, at 1:00 AM, koko wrote:
> I want to make a static cocoa library that is an NSTableView and allots data
> is contained in the library.
> I want images in the rows of the table.
> Where would one get these images as their is no bundle where that can be
> stored?
> Or the question
On Oct 7, 2012, at 1:00 AM, koko wrote:
> I want to make a static cocoa library that is an NSTableView and allots data
> is contained in the library.
> I want images in the rows of the table.
> Where would one get these images as their is no bundle where that can be
> stored?
> Or the question
On Oct 5, 2012, at 22:18 , Jerry Krinock wrote:
> I know you can embed an Info.plist in a command-line tool, by specifying it
> in the Info.plist Build Setting. But the only non-executable thing I've ever
> seen embedded in a static library is a code signature.
A static library does not survi
On 2012 Oct 05, at 19:23, koko wrote:
> Or the question is where are resources for a static coco library stored?
I know you can embed an Info.plist in a command-line tool, by specifying it in
the Info.plist Build Setting. But the only non-executable thing I've ever seen
embedded in a static
