471,852 Members | 1,306 Online
Bytes | Software Development & Data Engineering Community
Post +

Home Posts Topics Members FAQ

Join Bytes to post your question to a community of 471,852 software developers and data experts.

PHB Request

Ok.. so this morning, PHB drops Licensing in my lap...

His requirements..
Enter a License key at install. (No problem, installsheild et. al. can do
that)
Only allow the application to run on the machine that it was installed on.
i.e., can't install on another machine with the same license key, or can't
move the application to another machine by copying the files etc.

Anyone have any ideas? Create a Registry Key with machine specific info in
it that the login page reads first? Encrypt something in the database?

This is classic ASP, SQL 2000. Using a .NET solution would be ok, we are
using a little .NET here and there for a couple of things, but we're still
learning it! :) All the source code will be installed on the end users
server.

And one other PHB request... use a component as a last resort.

Help!?!
Jul 19 '05 #1
2 1162
On Fri, 27 Feb 2004 12:37:24 -0500, "Bryan Harrington"
<ne**@psacake.com> wrote:
Ok.. so this morning, PHB drops Licensing in my lap...

His requirements..
Enter a License key at install. (No problem, installsheild et. al. can do
that)
Only allow the application to run on the machine that it was installed on.
i.e., can't install on another machine with the same license key, or can't
move the application to another machine by copying the files etc.

Anyone have any ideas? Create a Registry Key with machine specific info in
it that the login page reads first? Encrypt something in the database?
Use a dongle. :)
This is classic ASP, SQL 2000. Using a .NET solution would be ok, we are
using a little .NET here and there for a couple of things, but we're still
learning it! :) All the source code will be installed on the end users
server.

And one other PHB request... use a component as a last resort.


Ugh. You'd actually want a component, DLL or other method that
wouldn't allow prying eyes to decipher it.

The best method I'd think for a web app would be for it to phone home
and register itself. It grabs a serial or other key generated
uniquely and stored in a database, and the second time it phones home
your system won't authorize it.

Jeff
Jul 19 '05 #2
Well here's how to get the user's IP address:

Request.ServerVariables("REMOTE_ADDR")

And maybe you could use that somehow to limit access to the Web site to
be just from that machine.

Best regards,
J. Paul Schmidt, Freelance ASP Web Developer
http://www.Bullschmidt.com
ASP Design Tips, ASP Web Database Demo, Free ASP Bar Chart Tool...
*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!
Jul 19 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

4 posts views Thread by Nalaka | last post: by
3 posts views Thread by Joseph Geretz | last post: by
NeoPa
reply views Thread by NeoPa | last post: by
reply views Thread by YellowAndGreen | last post: by
aboka
reply views Thread by aboka | last post: by

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.