[senna]

I am wanting to add a link to my website that when someone clicks on it they have to enter a password to get to the link. How would I go about that?

Thanks,

Senna

[xgerryx]

There is a really basic bit of html code available here: http://www.sbrady.com/hotsource/javascript/passw.html

It is only basic and is easy get around but is alright for a privacy curtain type security.

[cnelson04]

If you looking for something PHP, heres my code here; http://www.visionstudios.be/phptut1.php its extremly easy to do and understand if you need any help PM me! -cnelson.

[hytechpro]

You do not specify which technology you hav used in your site

[Squashman]

Is it an Apache or IIS webserver?

[cnelson04]

If your server support PHP, then my script will work just fine. -cnelson.

[Eriksrocks]

A .htaccess/.htpasswd combination is even better and more secure than PHP.

.htaccess Authentication Generator
.htpasswd Generator

[namenotfound]

Originally Posted by Eriksrocks

A .htaccess/.htpasswd combination is even better and more secure than PHP.

.htaccess Authentication Generator
.htpasswd Generator

Depends on how the PHP is used to password protect

HTTP passwords are easier to crack with "brute force" methods than form passwords using certain "password crack" devices.

If you use PHP to password protect using a form to enter the password, it can be more secure then a .htaccess file that uses the HTTP method of entering the password.

In other words, this:



Is easier to crack than this:

[Squashman]

Originally Posted by namenotfound

Depends on how the PHP is used to password protect

HTTP passwords are easier to crack with "brute force" methods than form passwords using certain "password crack" devices.

If you use PHP to password protect using a form to enter the password, it can be more secure then a .htaccess file that uses the HTTP method of entering the password.

I disagree. I did some security testing for a new mail server for one of my clients and it was all web based. It was just as susceptible to brute force and it was using a Form for Username and password.

[namenotfound]

Ok, then I'm wrong.

It's just, I know a few "crackers" than spent years cracking into pornographic websites
They'd always complain about how hard it was to crack form-based passwords
But always seemed to be able to get into the other kind

[jiml8]

With a form-based password you have the option in the form to put in a counter or timer, thereby slowing down a cracker and locking them out after a handful ot tries for a period of time. With .htaccess/.htpasswd you are at the mercy of the server configuration (which often you do not control) to slow or limit the bad guys. For that reason, and no other, I would have to go with form based being more secure.