Yeah seeing cracks for your software whilst at first you think...you
scums...then you think...cool...someoen wants it !
I was thinking about a program that I wrote that I was looking at to see how
easy it was to crack, and I remember I gave up cos. I was checking to see if
the program was reg. or not.
Esp. in the reports. EVERY report that was dodne did a check to see if the
program was reg. or not, and just about every proccess did the same, and it
was checking the reg. status in about 20-30 diff. places !!
Thats why I gave up trying to crack it.
This MIGHT be a good thing in some ways. IF you just have a generic routien
that you call to check if reg. or not, and do it in heaps of places, then
the cracker is likly to get board and give up, not cos. its too complicated,
but cos there would be some many place.
They wouldn't ness. know this straight awat either...
Just a though,
Jeremy Coulter
Application Developer
Application Development Centre
Compaq Computer New Zealand Ltd.
Phone: 64 3 371 5724
Fax: 64 3 371 5724
Mobile: 64 0212533214
E-mail: [EMAIL PROTECTED]
Personal Email: [EMAIL PROTECTED]
-----Original Message-----
From: Nahum Wild [mailto:[EMAIL PROTECTED]]
Sent: Friday, August 13, 1999 9:59 AM
To: Multiple recipients of list offtopic
Subject: RE: [DUG-OFFTOPIC]: Cracks
In this particular case you could perform some 'hack' checks of the
centralised regcheck function. A good one might be to pass it a code that
you know is not a valid regkey, so you expect it to return false - but if it
returns true then you know that its been hacked.
With just learning about this topic there seems to me to be lots of things
that I as a developer can do to protect my app from the casual cracker, but
nothing from a serious cracker. But then again if someone is trying to
crack my software its probably a good indication that its popular with lots
of demand!
Nahum
-----Original Message-----
From: Aaron Scott-Boddendijk [mailto:[EMAIL PROTECTED]]
Sent: Friday, 13 August 1999 09:43
To: Multiple recipients of list offtopic
Subject: Re: [DUG-OFFTOPIC]: Cracks
> If your code that checks to see if the regcode is valid or not is quick
> enough you could just refer to that function everytime you want to know if
> the app has been registered or not. That way there is no stored value
> indicating that the app has been registered. Would that help, I'm not
sure
> as I'm not particularly knowledgeable on this topic. :-)
This gives one centralised place to hack around so that it always returns
True.
The best registrations I've seen are program modules encrypted using using
high level encryption to match the registration. This does mean a large
distribution for keys and a slow loading with complicated code
It works by wrapping up the actual code for the key ingredients that make
the
Registered version better than the free version. The encryption stops
people
shipping the module with breaking the encryption or using the same
registration key... They can of course circumvent the encryption check and
ship an unencrypted version which is just going a step deeper into the code.
Place identification material in the module that is never used by the
application
but does identify the original registered owner of the module - that way you
can still trace it back to the source.
--
Aaron Scott-Boddendijk
Jump Productions
(07) 838-3371 Voice
(07) 838-3372 Fax
---------------------------------------------------------------------------
New Zealand Delphi Users group - Offtopic List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
---------------------------------------------------------------------------
New Zealand Delphi Users group - Offtopic List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
---------------------------------------------------------------------------
New Zealand Delphi Users group - Offtopic List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
