PASSWORD COP--SSF PASSWORD PROTECTION

SSF When you're serious about password protection. But don't take our word for it, ask our CLIENTS!	SSF FAQ In all the following FAQs, the PATH for your member section is assumed to be /path1/public_html/members/. This is only an example path. You should change it to the actual member section path on your server. How do I set up the SSF system to execute automatically? What is the exact format of the line I need to add to my cron tabs? My system suddenly doesn't add any bad-members to the suspected list - Why? Can I change the images of the SSF system? Can I copy the SSF system from my old computer to my new one? Can I have more then one SSF system on the same computer?
	How do I set up the SSF system to execute automatically? Create a file in your crontabs directory. The file name has to be the name of the username that you want the cron job to execute from. For example, if you want to run a cron job as root, create (or edit) the file named root in your cron tabs directory. Don't forget that if a bad-member is detected, the cron job will delete it from your password file or database. In the case of deleting a member from your password file, a new file will be created. The new file will have the permission of read-write for the username that created it, so you want to check for permission problems. (add a chmod 666 to eliminate permission problems)
	What is the exact format of the line I need to add to my cron tabs? Most of the Unix systems out there will use the following format for the crontab files: `Minute Hour * * * path/file-name to execute > output` For example, to execute the SSF system every 10 minute use the following line `0,10,20,30,40,50 * * * * /path1/public_html/members/cgi/autoDelBad.cgi >/dev/null` To execute the SSF system every 15 minutes (the recommended setup) use `0,15,30,45 * * * * /path1/public_html/members/cgi/autoDelBad.cgi >/dev/null` If you are running few SSF systems on the same computer, it is recommended that you execute the different systems on different time schedules. For example: `0,15,30,45 * * * * /path1/public_html/members/cgi/autoDelBad.cgi >/dev/null 3,18,33,48 * * * * /path2/public_html/members/cgi/autoDelBad.cgi >/dev/null` Please check your system by looking at existing lines in your root cron tabs or by using the man page for cron.
	My system suddenly doesn't add any bad-members to the suspected list - Why? First check your member-section entry page to see that the SSF logo is visible. If you can't see the logo, your system is not protected at all (the SSF system is not running). To solve this problem add the following line to your main page: <IMG src=cgi/ssf.cgi><br><font size=2>PasswordCop Protection</font><br> Second, check your system yourself by logging in with the same user name and password from two different IP's. To do so just use two different computers in your office/home or call a friend. If you see the "X" over the SSF logo, the system is working and you should see a new entry in the suspected list. In this case everything is working fine and your system didn't detect any bad-members because no bad members are attacking your system. Third, check that the CGI directory is set-up with the right permissions so that the SSF system can add lines to its suspected bad member log. Check permission for the file named ssf-log.badMembers. In both cases the permissions need to be set-up so the SSF system can open the ssf-log.badMembers file for appending when SSF is executed by the web-server. In most cases you can change mode to 777 for the CGI directory and to 666 to the ssf-log.badMembers file. Still not working? --------- Contact us.
	Can I change the images of the SSF system? No, the images are hard-coded into the system. But if you have to, we can reinstall the system for a regular extra-system-price with your desired images.
	Can I copy the SSF system from my old computer to my new one? No, the shared memory segments as well as the exact PATH is hard-coded into the system. But if you have to, we can reinstall the system for a regular extra-system-price.
	Yes, the path is hard-coded into the system. The 2nd SSF system will have to be installed with a new-shared memory segment. Because of that you have to let us know that the new installation is on the same computer as an old installation. There are no real limits to the number of SSF systems on the same computer other than HD space and RAM.