From: Francis Galiegue <fg@one2team.net>
To: Alexander Gavrilov <angavrilov@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [RFC PATCH] gitweb: Support filtering projects by .htaccess files.
Date: Mon, 3 Nov 2008 17:54:00 +0100 [thread overview]
Message-ID: <200811031754.00545.fg@one2team.net> (raw)
In-Reply-To: <200811031943.30033.angavrilov@gmail.com>
Le Monday 03 November 2008 17:43:29, vous avez écrit :
> Some environments may require selective limiting of read access to
> repositories. While even dumb http transport supports it through .htaccess
> files, gitweb currently does not implement discretionary access control.
>
> This patch adds a configuration-contolled check that matches simple
> 'Reguire user'/'Reguire group' lines in the .htaccess files with the
> authenticated user name. Using group authentication requires specifying
> a path to the Apache group file in the configuration.
>
> Using htaccess has an additional bonus that the same authentication
> data can be used both for gitweb and the dumb http transport.
>
> Signed-off-by: Alexander Gavrilov <angavrilov@gmail.com>
It just seems to me that this is emulating functionality that multiple Web servers already provide...
What's more, knowledge about these Web servers are _much_ more widespread than knowledge about gitweb.
Why reinvent the wheel?
Just a thought,
--
fge
next prev parent reply other threads:[~2008-11-03 16:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-03 16:43 [RFC PATCH] gitweb: Support filtering projects by .htaccess files Alexander Gavrilov
2008-11-03 16:54 ` Francis Galiegue [this message]
2008-11-03 17:26 ` Alexander Gavrilov
2008-11-03 17:45 ` Francis Galiegue
2008-11-03 18:18 ` Jakub Narebski
2008-11-03 18:44 ` Francis Galiegue
2008-11-03 19:17 ` Jakub Narebski
2008-11-03 21:59 ` Francis Galiegue
2008-11-04 0:24 ` Jakub Narebski
2008-11-04 7:42 ` Francis Galiegue
2008-11-03 22:57 ` Jakub Narebski
2008-11-05 22:36 ` Alexander Gavrilov
2008-11-05 23:26 ` Jakub Narebski
2008-11-06 19:43 ` Alexander Gavrilov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200811031754.00545.fg@one2team.net \
--to=fg@one2team.net \
--cc=angavrilov@gmail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox