> Hi Danny, it seems like no one else will reply, I
thought that there were
> more people using projectors out there.
>
> >This all sounds like overkill to me - you're going
to end up locking out
> >people who have a legitimate right to use the
software. What exactly is
> it
> >that you think they might be doing? How is your
software protected in
> the
> >first place? How do they register it? (Is it
registered with a key? Is
> that
> >key stored in the registry somewhere? etc). Does
it have an online
> element?
>
> I just wanted to be sure that it was at least a bit
hard to crack, and I
> wanted
> to learn about security in projectors.
> Currently after the user has payed a license an
automatic license key is
> sent
> to the user's email. That license key is generated
accoding to some
> information
> about the user by a php script. After that, the user
can put his name and
> serial in
> the soft and it just unlocks and starts running as
full version. It's
> not super secure because it just generate 2 different
files with the
> license inside. Someone
> could just copy the files to his folder and he will
have a full version.
> I don't know how to fight against that.
Well, with that level of security, I don't think there's a
lot of point
putting in the kinds of protection you're talking about: if
anyone wants to
steal your software, they can.
> I don't know if use something like an online
activation as Norton
> antivirus does. If you know of a good way please let
me know. Also I
> don't know much about how to modify the register and
if it's a good
> method either.
If you're willing to force users to have online access (and
be limited to
one machine), then Macromedia's method isn't a bad way to
go: maintain a
database of registered users, assign one key to each, then
don't allow more
than one activation per key. As far as I'm aware, that's the
only 100%
secure way to protect against key sharing.
A less intrusive method might be to have the software
contact you whenever
it's run and tell you what key is being used. You could
maintain a 'hotlist'
of keys that you either know are compromised (because you've
found them
online) or are pretty sure have been shared because they're
being used more
often than one would expect.
Finally, you could just keep an eye out for keys being
shared online (maybe
run a periodic automatic Google search for all the keys on
your database)
and if you find one, contact the user and tell them that
they have given out
their key and you're suing them for thousands of dollars.
Otherwise, I'd stick with your existing method and wait and
see. I don't
think these things are really a big issue for anything but
the most
commercially successful software. Sharing can even help your
business by
increasing the number of people exposed to the game and
encouraging 'buzz'.
>
> >on checkForHack
> >global myCommunicationObject
> >tCheck=myCommunicationObject.amIOK()
> >end
>
> Thanks for that idea, I added that to my code a bit
modified to work
> better.
> I don't know if someone can get the handlers name or
properties of my
> communication object? Hope not!
>From an exe with debugplaybackenabled=false, definitely
not.
Danny
_______________________________________________
dirGames-L mailing list - dirGames-L nuttybar.drama.uga.edu
http://nuttybar.drama.uga.edu/mailman/listinfo/dirgames
-l
|