From: "Jonas H." <jonas@lophus•org>
To: git@vger•kernel.org
Subject: Implementing authenticated Smart HTTP - which URLs to secure
Date: Sun, 15 Jul 2012 15:43:15 +0200 [thread overview]
Message-ID: <5002C8F3.6080400@lophus.org> (raw)
Howdy!
I'd like to implement HTTP authentication for Git Smart HTTP using
Dulwich (a Python binding):
1) read-only if unauthenticated and write only if authenticated
2) read/write only if authenticated
I couldn't find any documentation on which URLs need be secured and what
response codes are expected in case the cloner/pusher is unauthenticated.
Is there any documentation on Smart HTTP workflow? The C sources
(vanilla Git and libgit2) didn't help me too much since I found it very
difficult to follow the code-flow... it's probably just abstracted too
well :-)
Thanks!
Jonas
next reply other threads:[~2012-07-15 13:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-15 13:43 Jonas H. [this message]
2012-07-15 20:49 ` Implementing authenticated Smart HTTP - which URLs to secure Shawn Pearce
2012-07-16 17:36 ` Jonas H.
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=5002C8F3.6080400@lophus.org \
--to=jonas@lophus$(echo .)org \
--cc=git@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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