| 
How does the software work?
The password protection is file based.
The software works like a wrapper, it encrypts html file with
password and strong encryption algorithms, and give it a "login"
look. When the visitor input the password, it will use the password
to decrypt itself, and display the protected content.
Suppose you have a file "c:\webdesign\test.html",
and you want this file be password protected. First, please
launch the software, in step 1, select this html file, in step
2, define valid username and password, then click "next",
in the last step, click "lock" button. Then you will
get this file protected.
After protection, the file "c:\webdesign\test.html"
will be password protected, you can test this file on the local
hard disk by opening it with IE, and then you can upload the
file to your web server.
The original un-protected file will be backup as "c:\webdesign\test.html.PreLock".
After protection, you need only upload the protected file.
Please do NOT upload the .PreLock file, it's just a backup file,
and also, do NOT delete this backup file.
Please note, in the current version, the file to be protected
must be on the local hard disk. After protection, you should
upload the protected file to the web server.
You can save the current configuration to a project .prj file.
The .prj file will contain the information about the file list,
user/password list, options etc. So you can load the .prj file
to the software at a later usage.
Where should the software run? Local developing machine
or the web server? Which file should I upload to the web server
after protection?
The software runs on the local developing machine. You can
use the software to password protect html files on the local
computer, and after protection, you need only upload the protected
file to the web server or publish the protected file on a CD-ROM.
You need ONLY upload the protected file to the web server.
Please do NOT upload the *.PreLock file, it's just a backup
file. Do NOT upload the .prj file, it's just a file to save
the project configurations. And also you should not upload the
user/password list .csv file, it's still just a file to save
the user/password list configuration.
How secure is it?
Unlike other similar products on this market which always use
some home-made algorithms, we use strong industry standard algorithms.
So the protection is very secure.
|
