From: Mike Hommey <mh@glandium.org>
To: Dmitry Potapov <dpotapov@gmail.com>
Cc: git@vger.kernel.org, gitster@pobox.com
Subject: Re: [PATCH] Allow git-shell to be used as a ssh forced-command
Date: Fri, 17 Apr 2009 21:49:19 +0200 [thread overview]
Message-ID: <20090417194919.GA7611@glandium.org> (raw)
In-Reply-To: <37fcd2780904170924t61168a49uf1800098cdb1d730@mail.gmail.com>
On Fri, Apr 17, 2009 at 08:24:35PM +0400, Dmitry Potapov wrote:
> On Thu, Apr 16, 2009 at 11:10:56PM +0200, Mike Hommey wrote:
> > When using a forced-command, OpenSSH sets the SSH_ORIGINAL_COMMAND
> > variable to what would otherwise be passed to $SHELL -c. When this
> > variable is set, we use it instead of the contents of argv.
>
> It would be nice to provide some justification where it can be used.
> IOW, why do you want to have the force command where essentially
> you execute the original command as it were no force-command?
You're not executing any command, but only what git-shell allows.
This allows git-shell to be set as a forced-command for a specific
ssh key, for example.
Mike
next prev parent reply other threads:[~2009-04-17 19:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-16 21:10 [PATCH] Allow git-shell to be used as a ssh forced-command Mike Hommey
2009-04-17 16:24 ` Dmitry Potapov
2009-04-17 19:49 ` Mike Hommey [this message]
2009-04-17 21:00 ` Dmitry Potapov
2009-04-17 22:36 ` Mike Hommey
2009-04-17 22:41 ` Shawn O. Pearce
2009-04-17 23:44 ` Mike Hommey
2009-04-18 7:46 ` Matthieu Moy
2009-04-17 23:40 ` Junio C Hamano
2009-04-17 23:48 ` Tommi Virtanen
2009-04-18 1:24 ` Junio C Hamano
2009-04-18 6:31 ` Mike Hommey
2009-04-21 5:43 ` [PATCH v2] " Mike Hommey
2009-04-21 8:05 ` Dmitry Potapov
2009-04-21 9:46 ` Eygene Ryabinkin
2009-04-21 8:13 ` Junio C Hamano
2009-04-21 9:09 ` Mike Hommey
2009-04-21 11:16 ` Dmitry Potapov
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=20090417194919.GA7611@glandium.org \
--to=mh@glandium.org \
--cc=dpotapov@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).