http://search.cpan.org/search?query=htaccess&mode=module
Better yet, use mod_auth_mysql in your Apache and manage
users, groups and passwords in a database table. This
should be a bit more secure than giving your web user
write access to a .htpasswd file.
so you give your webuser** write access (IE INSERT/UPDATE) to your
.htpasswd-ish table? :)
I do like mod_auth_mysql but his question wasin regard to htpasswd type
interaction. So while its ogod to recommend alternative methods its not
really "Better yet" :)
** ok technically its the user connecting via DBI. which now you have to
worry about the world getting the auth data from the script. Personally,
mod_auth_mysql does have many advantages but security is not really one
of them.
For security you run under suexec then 700 on scripts and 600 on files
will be "secure". Then with .htpasswd or mod_auth_myslq I am "secure"
and can use whichever fits my needs.
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
<http://learn.perl.org/> <http://learn.perl.org/first-response>
