From: Andreas Ericsson <ae@op5.se>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 5/5] git-daemon support for user-relative paths.
Date: Sat, 19 Nov 2005 00:45:48 +0100 [thread overview]
Message-ID: <437E67AC.2010400@op5.se> (raw)
In-Reply-To: <7voe4hfssj.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano wrote:
>
> I think it might make sense to inserting something like the
> attached untested patch in your series, between library and
> upload-pack.
I'll run the clone/fetch/push test-suite again tomorrow, with this
applied. It looks good though.
> The validation done by path_ok() in git-daemon
> probabaly needs to lose alternate checks and validate only the
> path returned by enter_repo(). This would make writing
> whitelist by git-daemon administrator a bit more cumbersome,
Not necessarily. The repositories in the whitelist should be validated
(and possibly converted) using the path_ok() function. This will also
make it possible to catch typos and permission errors that are just
plain annoying for the admins.
In non-strict mode this isn't really a problem so long as all
whitelist-paths are absolute and doesn't contain any symlinks, although
we could use the chdir() + getcwd() thingie since we don't need the
ability to go back to where we started and that's what will be used
later when serving the repos.
--
Andreas Ericsson andreas.ericsson@op5.se
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231
next prev parent reply other threads:[~2005-11-18 23:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-17 19:37 [PATCH 5/5] git-daemon support for user-relative paths Andreas Ericsson
2005-11-18 0:49 ` Junio C Hamano
2005-11-18 10:18 ` Andreas Ericsson
2005-11-18 17:57 ` Matthias Urlichs
2005-11-18 20:41 ` H. Peter Anvin
2005-11-18 21:13 ` Junio C Hamano
2005-11-18 23:19 ` Junio C Hamano
2005-11-18 23:45 ` Andreas Ericsson [this message]
2005-11-21 9:28 ` Junio C Hamano
2005-11-21 9:49 ` Junio C Hamano
2005-11-21 11:10 ` Andreas Ericsson
2005-11-21 23:29 ` Junio C Hamano
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=437E67AC.2010400@op5.se \
--to=ae@op5.se \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.