Dave,
In your htaccess file, I would imagine that you are pointing to a password
file via the AuthUserFile directive so as long as you have permissions to
edit that file, use the perl function crypt() to generate the password and
then just append it to the password file. Just remember to have th
you use the crypt lib and do a dual password entry. no confirmation is
needed if the two passwords match. Everything is handled by the perl
script, you don use htpasswd. Crypting is very straightforward.
[EMAIL PROTECTED] (in palo alto)
On Thu, 9 Dec 1999, dave_dunstan wrote:
> Hi gang, I hop
Did you try the Apache::Htpasswd module?
/prakash
dave_dunstan wrote:
> Hi gang, I hope this isn't too off-topic, I figure someone will know the
> answer right away. I (my client) wants to manage user permissions at a
> shared-hosting server. I'd certainly use .htaccess, except this particular
Hi gang, I hope this isn't too off-topic, I figure someone will know the
answer right away. I (my client) wants to manage user permissions at a
shared-hosting server. I'd certainly use .htaccess, except this particular
client wants a gui to do this sort of thing (a little form, a little cgi,
boom
