From: Matt McCutchen <matt@mattmccutchen.net>
To: Jakub Narebski <jnareb@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 2/2] gitweb: support hiding projects from user-visible lists
Date: Tue, 23 Dec 2008 20:40:31 -0500 [thread overview]
Message-ID: <1230082831.2971.45.camel@localhost> (raw)
In-Reply-To: <m3ljujg2eh.fsf@localhost.localdomain>
On Sat, 2008-12-13 at 14:02 -0800, Jakub Narebski wrote:
> Cannot you do this with new $export_auth_hook gitweb configuration
> variable, added by Alexander Gavrilov in
> dd7f5f1 (gitweb: Add a per-repository authorization hook.)
> It is used in check_export_ok subroutine, and is is checked also when
> getting list of project from file
>
> >From gitweb/INSTALL
>
> - Finally, it is possible to specify an arbitrary perl subroutine that
> will be called for each project to determine if it can be exported.
> The subroutine receives an absolute path to the project as its only
> parameter.
>
> For example, if you use mod_perl to run the script, and have dumb
> http protocol authentication configured for your repositories, you
> can use the following hook to allow access only if the user is
> authorized to read the files:
>
> $export_auth_hook = sub {
> use Apache2::SubRequest ();
> use Apache2::Const -compile => qw(HTTP_OK);
> my $path = "$_[0]/HEAD";
> my $r = Apache2::RequestUtil->request;
> my $sub = $r->lookup_file($path);
> return $sub->filename eq $path
> && $sub->status == Apache2::Const::HTTP_OK;
> };
$export_auth_hook would work, and it would have the nice (but not
essential) feature of including private projects in the list shown to
suitably authenticated users. The only problem is that my Web host
doesn't support mod_perl. Is there a practical way to accomplish the
same thing as the above example in a CGI script? I would like to avoid
reimplementing Apache authentication-checking functionality if at all
possible.
--
Matt
next prev parent reply other threads:[~2008-12-24 1:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4ba6b6c3fc183002407f322663d7ab53c1c28a91.1229202740.git.matt@mattmccutchen.net>
2008-12-13 21:16 ` [PATCH 2/2] gitweb: support hiding projects from user-visible lists Matt McCutchen
2008-12-13 22:02 ` Jakub Narebski
2008-12-13 22:05 ` Jakub Narebski
2008-12-14 2:34 ` Sending a threaded patch series with Evolution Matt McCutchen
2008-12-24 1:40 ` Matt McCutchen [this message]
2009-01-02 19:33 ` [PATCH 2/2] gitweb: support hiding projects from user-visible lists Jakub Narebski
2009-01-03 18:29 ` gitweb config with some public, some basic-authenticated repos Matt McCutchen
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=1230082831.2971.45.camel@localhost \
--to=matt@mattmccutchen.net \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).