Of course you can come up with a licensing mechanism, but don't think for a
minute that it's really secure. The article I mentioned really opened up my
eyes to that (so I gave up my quest to design a licensing library). It
could always be "secure enough", though. In reality, you have to weigh out
the possibility of someone thinking that it's worth the time to hack into
your bytecode to steal your application. If you don't think that your users
will take the time (or it won't happen often enough to worry about), then
it's no big issue. Your licensing scheme is probably just fine.
-----Original Message-----
From: Scott Hofmann [mailto:shofmann@xxxxxxxx]
Sent: Friday, August 11, 2006 9:00 AM
To: 'Steven Fahlbusch'; users@xxxxxxxxxx
Subject: RE: [cinjug-users] Product Keys
Thanks Steve, you are correct in your assumptions - it is not a
client/server type app. The type of solution you mention is along the lines
of the level we need.
Still interested in hearing any other suggestions that might be out there.
- Scott
> -----Original Message-----
> From: Steven Fahlbusch [mailto:sfanda@xxxxxxxxx]
> Sent: Friday, August 11, 2006 8:01 AM
> To: Scott Hofmann
> Subject: Re: [cinjug-users] Product Keys
>
> Greetings Scott
>
> I'm assuming that this is a simple (no reflection on the
> program - just talking structure here) client application
> (like say a text editor, or the like) and not a client /
> server, web app or web services app.
>
> If the above is correct, then a simple way of handling is to
> generate a key that is a hash of some sort of the MAC address
> - this key can be stored in a simple text file (like
> license.txt). On startup of your app, you regen the hash and
> compare if not a match - request that they contact you.
>
> -steve
>
>
> --- Scott Hofmann <shofmann@xxxxxxxx> wrote:
>
> > Hello everyone,
> > I'm involved in a software product being developed in Java and
> > wondered if anyone here has had any experience with product
> keys and
> > registrations? I'm hearing from the developer that to do
> > registration:
> >
> > "From my research online, it looks like the only truly
> secure way is
> > to have a license server. The software would then connect to the
> > license server to ensure that it is legitimate. However,
> this seems
> > like an expensive solution as it requires *much* more
> development work
> > in addition to having another server to maintain."
> >
> > Sooo... I'm trying to identify ways others are doing their product
> > keys or have heard of doing them. We really do not need a
> truly secure
> > key.
> > The product will sell for under $50. What we need we think
> is just a
> > simple solution that help to:
> >
> > - Keep people honest and not feeling to free about passing along
> > copies to other.
> > - Being able to provide support to those who truly purchased the
> > product.
> > - Most likely we would not trouble ourselves with those
> people who are
> > dishonest and feel the need to find loop hole in software
> product keys
> > in order to use it anyway.
> >
> > Any advice or thoughts on this topic would be helpful.
> >
> > - Scott Hofmann
> >
> >
>
>
> __________________________________________________
> Do You Yahoo!?
> Tired of spam? Yahoo! Mail has the best spam protection
> around http://mail.yahoo.com
>
>
---------
You may unsubscribe from this mailing list
by sending a blank email addressed to:
users-unsubscribe@xxxxxxxxxx
--
Find additional help by sending a blank email
addressed to:
users-help@xxxxxxxxxx
|