Re: Protecting Software w/ Software License Keys...
Re: Protecting Software w/ Software License Keys...
- Subject: Re: Protecting Software w/ Software License Keys...
- From: Jason Harris <email@hidden>
- Date: Mon, 17 Jun 2002 15:13:58 -0700
A cracker would completely ignore the whole public/private thing and find
the spot where the function that checks 'em returns YES or NO. And change
it so it always returns YES.
You could encrypt part of your code and when serialized, provide a value
that when hashed with the MAC gives the encryption key. But even then, a
hacker would take a properly serialized version, let it unencrypt the code,
and create a patch that replaces the encrypted code with the unencrypted
code.
It's just not worth the time you'd spend implementing this. Instead,
develop something that _can_ be cracked, but that will get the majority of
people to pay.
Jason Harris
Kyle Moffett Tried to Tell Me:
>
On Monday, June 17, 2002, at 04:09 PM, Erik J. Barzeski wrote:
>
>
> Hi,
>
>
>
> Besides, a cracker will get around this in a matter of days... And
>
> you're
>
> back to the same old "just try to get the honest people to pay" but in
>
> this
>
> case, I'd add "but don't piss them off with a cumbersome process."
>
>
How could a cracker get past this? The government uses public-private
>
key cryptography for confidential material. Are you saying that somebody
>
could get past confidential security in a matter of days, or is my system
>
missing some step or something.
>
_______________________________________________
>
cocoa-dev mailing list | email@hidden
>
Help/Unsubscribe/Archives:
>
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
>
Do not post admin requests to the list. They will be ignored.
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.