git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Antonio García Domínguez" <nyoescape@gmail.com>
To: BJ Hargrave <bj@bjhargrave.com>
Cc: Ryan Phillips <ryan@trolocsis.com>, git@vger.kernel.org
Subject: Re: git-http-backend and Authenticated Pushes
Date: Tue, 9 Mar 2010 20:23:48 +0100	[thread overview]
Message-ID: <2b8265361003091123g780a9b36g5ec641d465c7df02@mail.gmail.com> (raw)
In-Reply-To: <64E1366D-31FC-4E0D-9F7D-35E6387E2EC1@bjhargrave.com>

Hi BJ,

> LocationMatch will not match against the query string which is where the service name is. To match against the query string, you would need to do something like:

Oops, you're right. I'm actually matching the unparsed URL using a
regexp in a Perl authentication module, so I missed that Apache
detail. Your snippet looks good to me.

> But, I would think using <LimitExcept GET PROPFIND OPTIONS REPORT> to protect against "writing" to the repo without auth should be sufficient.

But that doesn't work for the smart HTTP method. Limiting by method is
OK for dumb HTTP (as we're basically just modifying files using
WebDAV), but the git-http-backend CGI only uses GET and POST, and
requires authentication depending not on the HTTP method, but what
service is being used.

Or so I think :-).

Cheers,
Antonio

  reply	other threads:[~2010-03-09 19:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-09 17:08 git-http-backend and Authenticated Pushes Ryan Phillips
2010-03-09 19:01 ` Antonio García Domínguez
2010-03-09 19:17   ` BJ Hargrave
2010-03-09 19:23     ` Antonio García Domínguez [this message]
2010-03-09 19:27 ` Shawn O. Pearce
2010-03-10  2:13   ` Ryan Phillips

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=2b8265361003091123g780a9b36g5ec641d465c7df02@mail.gmail.com \
    --to=nyoescape@gmail.com \
    --cc=bj@bjhargrave.com \
    --cc=git@vger.kernel.org \
    --cc=ryan@trolocsis.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).