[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [cobalt-users] Webalizer Password Protected Directories
- Subject: Re: [cobalt-users] Webalizer Password Protected Directories
- From: Lillith Lesanges <lillith@xxxxxxxxxx>
- Date: Fri Apr 5 06:30:39 2002
- List-id: Mailing list for users to share thoughts on Cobalt products. <cobalt-users.list.cobalt.com>
On Friday, April 5, 2002, at 06:59 AM, Chris Broomall wrote:
Any ideas why Webalizer 2.01.6-3 on my RaQ4r only password protects the
stats for sites that have FrontPage extensions enabled? On every one of
the sites where FrontPage Extensions are disabled, the stats show up for
anyone without prompting for the admin's password.
I'd start by taking a look at the .htaccess file in the
/home/sites/site*/web/stats/ directories. Compare them to the values in
/etc/group and see if there's some problem. (Just looking shouldn't void
any warranties. :grin:)
I'm having a slightly -different- issue. We have clients for whom we are
both hosting and designing. Consequently, those clients don't have any
admin user/pass. They still want to look at their stats, though.
I dislike the idea of creating a global 'reports' user (only one password,
etc) and adding it to everyone's .htaccess. Of course, I want to
integrate this to the /etc/cron.daily/webalizer.pl so that it is
automatically generated when we add a new virtual site. :) I've also got
a constraint that the per-site reports user needs to be something that
nobody has to look up (ie, not 'siteXX' since i'm the only one who knows
that). We regularly have domain names that are longer than 12 characters,
so the domain name by itself is insufficient, though truncating it would
be ok.
I suspect that this is an impossible set of constraints, but does anyone
have any brilliant ideas on how I can implement this?
Lillith K. Lesanges
Sysadmin/Programmer, MIS, Inc.