hi all!

my question is about making my ASP apps secure. secure in a sense that nobody should be able to copy my files (assume you have physical access to my server) and re-create the same environment on their servers and run my apps.

how can DLL files make ASP apps more secure? again, the question is not about seeing the code but about copying the DLL files.

That will be like Security and Permission settings in Windows2000 server?

__________________
webmaster @ http://kongtechnology.com

yep, it was the first thought i had too. but my question was not it. it's about the way you use DLL files in ASP. basically i'm concerned about this:

i'm developing an app for a customer. it's not meant to be online (but capable). the customer has Win2k. so i'm simply installing the IIS and the app a browser-based, blah blah blah... i think you got the point.

the customer has a physical access to the server (it's in his office). so i want to write such an app which, even if he does copy and paste into another machine, would not work.

any ideas?

This is like registering software lah?! Store an encrypted key in the registry and verify this in your app? Or maybe check against the Hard-drive's id (what do we call it?...)... Or check this out:
http://www.ggu-software.com/html/sof...k/index_e.html

__________________
webmaster @ http://kongtechnology.com

Hi,

I think what you are trying to do is not possible for the following reasons:

1. Your app is written in ASP. ASP is not compiled and anyone who has physical access to the files can modify it.
2. Even if you were to create a DLL, it's possible to copy that and install it on a different machine too.
3. A registry key can easily be reproduced.
4. If you were to check it with the hard-disk id, the application could be modified to reflect a new hard-disk (refer to point 1).