Let's assume your login is "foo" and you want to protect
~foo/public_html/protected/ using htaccess/htpasswd

In your public_html/protected/ directory, you place two files:

.htaccess which contains something like this:

AuthType Basic
AuthName "My Protected Stuff"
AuthUserFile /s/chopin/l/grad/foo/public_html/protected/.htpasswd
require valid-user


The second file is .htpasswd, and it looks like this:
username1:encrypted_password1
username2:encrypted_password2
...

To generate encrypted passwords, log into any CS Department Linux machine
and run

        /usr/bin/htpasswd  .htpasswd username

This will ask you for a password, then add a line (username:passwd) to the
.htpasswd file.

The .htaccess and .htpasswd files must be world readable, as the web
server runs as "nobody" and can't otherwise use these files.


Whenever someone will want to access something uder

        http://www.cs.colostate.edu/~foo/protected/file.html

they will get a box to enter their username and password, which will have
to match an entry in the .htpasswd file.


Be aware of the fact that this only protects against access by people
OUTSIDE the cs department. If a person has an account with the cs
department, they can read your files because you must make them world
readable so that Apache can serve them. If your files are not world
readable, you can't serve them to anyone, since Apache won't have
permissions to access them.