Re: Script to change .htaccess password?
Tim Bunce (Tim.Bunce@ig.co.uk)
Tue, 2 Jan 1996 17:11:13 +0000
> From: dougm@osf.org (Doug MacEachern)
>
> >> From: dougm@osf.org (Doug MacEachern)
> >>
> >> I have written a little set of modules that can do this sort of thing. If
> >> there is enough interest, I'd be willing to clean them up and release them.
> >> There's the HTTP::Admin base class, with Text, DBM, and SQL sub classes. It
> >> looks something like this:
> >>
> >> #simple case:
> >> $admin = new HTTP::Admin::DBM { Path => $path, Group => 'www' };
> >> $admin->add_user($username, $password);
> >> $admin->add2group($username);
> >>
> >> (UserFile and GroupFile default to ".htpasswd" and ".htgroup")
> >
> >This'll be useful but the functionality of the module is nothing to do with
> >the HyperText Transfer Protocol (HTTP) and so using that module category name
> >is a poor idea.
> >
> >Perhaps HTTPD (for daemon) would be better so long as the code is independent
> >of the type of the server. If the code will only work for a certain type
> >of server, such as NCSA, and you have no plans to support others then it
> >should be named after that server.
>
> Yes, I agree, HTTPD is better category. I thought about using it before,
> but I wasn't sure about introducing a new category. The code currently
> works with NCSA and Apache, I haven't tested it with any other servers. I
> would like to support as many servers as possible, but let's say it works
> with a handfull of the dozens servers out there, what would be an
> appropriate naming scheme?
Umm, how about a module called
HTTPD::UserAdmin
with subclasses as needed?
> >I'm sure these will be useful - especially if you take the time to
> >discuss the module interfaces and functionality with others first.
>
> Where would be an appropriate place for this discussion? I was also
> thinking about an HTTPD::Access module to parse HTTPD access files and
> implement access control, along with a few others that may be of little or
> no interest to people on this list.
Ideally comp.infosystems.www.authoring.cgi but it looks hard to 'discuss'
design issues there. The libwww-perl@ics.uci.edu might be happy to cover
this even though it's not using the libwww-perl library (I've CC'd this
to them for comment). Perhaps there are some other mailing lists that I
don't know about. Comp.lang.perl.misc is always a good bet for perl issues.
In the meantime I've added HTTPD::UserAdmin and HTTPD:Access to the Module
List, let me know if you want any changes:
HTTPD::
::UserAdmin adpO Management of server user and group files DOUGM +
::Access cdp Management of server access control files DOUGM +
Tim.