Anthony Baratta wrote:

> Rob Napier wrote:
> >
> > But unfortunately does not address our desire to give our users
> > password-protected web pages that aren't readable by every other user
> > on the system. Since I personally use this feature (I have password
> > protected pages that are for me and my friends and aren't the business
> > of just any other user on the machine), and help admin the box, the
> > subject has my full attention :)
>
> OK...here's a thought of the top of the head.
>
> How about setting up the Apache Service to belong to each user's
> personal group id?? That way the Apache service can read the group
> permissions but no one else can??

Well perhaps only for those users who really need the extra security, this
could
get out of hand real quick;)

How about a simple setgid cgi that authenticates against the htpasswd,
htgroup files, then
dumps the pages from secure storage? This could probably be done in less
than 20
lines of perl, or similarly simple C. This may not be as fancy as the
apache module,
but it would not be dependant on apache version.

It's also quite possibly a smaller setgid code path. (Though this depends a
great deal on
the apache module.)



-- 
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.

Reply via email to