All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Junio C Hamano <junkio@cox.net>
Cc: Linus Torvalds <torvalds@osdl.org>,
	Git Mailing List <git@vger.kernel.org>
Subject: Re: git-daemon --inetd
Date: Fri, 16 Sep 2005 09:54:00 -0700	[thread overview]
Message-ID: <432AF8A8.6070807@zytor.com> (raw)
In-Reply-To: <7vbr2tqwl0.fsf@assigned-by-dhcp.cox.net>

Junio C Hamano wrote:
> 
> Later exchanges between you and HPA appeared to me that we would
> need a chroot environment which has "enough stuff" and that this
> patch may not help him very much.  Am I mistaken?
> 

Well, building a chroot environment which supports execing is a bit of a 
pain, but it's fully doable.  mount --bind especially makes that quite 
feasible.  It's just more work.

> I think resolving user and group to numeric before you do
> chroot() might make the setting up of chrooted environment a
> little simpler; no need for supporting getpwnam and getgrnam
> there.  On the other hand it may not matter -- you can always
> give numeric uid/gid to begin with.

Yes, resolve the username first.

	-hpa

  reply	other threads:[~2005-09-16 16:54 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-15  6:04 git-daemon --inetd H. Peter Anvin
2005-09-15 16:03 ` Linus Torvalds
2005-09-15 18:30   ` H. Peter Anvin
2005-09-15 18:47     ` Linus Torvalds
2005-09-15 19:19       ` H. Peter Anvin
2005-09-15 19:40         ` Linus Torvalds
2005-09-15 21:44           ` Martin Langhoff
2005-10-22 13:45             ` Jon Seymour
2005-10-22 21:05               ` Linus Torvalds
2005-09-15 19:57         ` Junio C Hamano
2005-09-16  6:23     ` Junio C Hamano
2005-09-16  7:51   ` Junio C Hamano
2005-09-16 16:54     ` H. Peter Anvin [this message]
2005-09-16 17:30     ` Linus Torvalds
2005-09-16 18:23       ` H. Peter Anvin

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=432AF8A8.6070807@zytor.com \
    --to=hpa@zytor.com \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    --cc=torvalds@osdl.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 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.