From: Greg Brockman <gdb@MIT.EDU>
To: j.sixt@viscovery.net, git@vger.kernel.org, gitster@pobox.com,
avarab@gmail.com, jrnieder@gmail.com
Cc: Greg Brockman <gdb@mit.edu>
Subject: [PATCH 1/4] Allow creation of arbitrary git-shell commands
Date: Tue, 20 Jul 2010 01:16:09 -0400 [thread overview]
Message-ID: <1279602972-1264-2-git-send-email-gdb@mit.edu> (raw)
In-Reply-To: <1279602972-1264-1-git-send-email-gdb@mit.edu>
This provides a mechanism for the server to expose custom
functionality to clients. My particular use case is that I would like
a way of discovering all repositories available for cloning. A
client that clones via
git clone user@example.com
can invoke a command by
ssh user@example.com $command
Signed-off-by: Greg Brockman <gdb@mit.edu>
---
shell.c | 41 ++++++++++++++++++++++++++++++++++++++++-
1 files changed, 40 insertions(+), 1 deletions(-)
diff --git a/shell.c b/shell.c
index e4864e0..fe1fe73 100644
--- a/shell.c
+++ b/shell.c
@@ -3,6 +3,8 @@
#include "exec_cmd.h"
#include "strbuf.h"
+#define COMMAND_DIR "git-shell-commands"
+
static int do_generic_cmd(const char *me, char *arg)
{
const char *my_argv[4];
@@ -33,6 +35,20 @@ static int do_cvs_cmd(const char *me, char *arg)
return execv_git_cmd(cvsserver_argv);
}
+static int is_valid_cmd_name(const char *cmd)
+{
+ /* Test command contains no . or / characters */
+ return cmd[strcspn(cmd, "./")] == '\0';
+}
+
+static char *make_cmd(const char *prog)
+{
+ char *prefix = xmalloc((strlen(prog) + strlen(COMMAND_DIR) + 2) * sizeof(char));
+ strcpy(prefix, COMMAND_DIR);
+ strcat(prefix, "/");
+ strcat(prefix, prog);
+ return prefix;
+}
static struct commands {
const char *name;
@@ -48,6 +64,8 @@ static struct commands {
int main(int argc, char **argv)
{
char *prog;
+ char *prog_cpy;
+ const char **user_argv;
struct commands *cmd;
int devnull_fd;
@@ -77,6 +95,7 @@ int main(int argc, char **argv)
die("What do you think I am? A shell?");
prog = argv[2];
+ prog_cpy = xstrdup(prog);
if (!strncmp(prog, "git", 3) && isspace(prog[3]))
/* Accept "git foo" as if the caller said "git-foo". */
prog[3] = '-';
@@ -99,5 +118,25 @@ int main(int argc, char **argv)
}
exit(cmd->exec(cmd->name, arg));
}
- die("unrecognized command '%s'", prog);
+
+ if (split_cmdline(prog, &user_argv) != -1) {
+ if (is_valid_cmd_name(user_argv[0])) {
+ prog = make_cmd(user_argv[0]);
+ user_argv[0] = prog;
+ execv(user_argv[0], (char *const *) user_argv);
+ free(prog);
+ }
+ free(user_argv);
+ /*
+ * split_cmdline modifies its argument in-place, so 'prog' now
+ * holds the actual command name
+ */
+ die("unrecognized command '%s'", prog_cpy);
+ } else {
+ /*
+ * split_cmdline has clobbered prog and printed an
+ * error message, so print the original
+ */
+ die("invalid command format '%s'", prog_cpy);
+ }
}
--
1.7.0.4
next prev parent reply other threads:[~2010-07-20 5:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-20 5:16 Updated patch series for providing mechanism to list available repositories Greg Brockman
2010-07-20 5:16 ` Greg Brockman [this message]
2010-07-20 17:01 ` [PATCH 1/4] Allow creation of arbitrary git-shell commands Junio C Hamano
2010-07-21 15:11 ` Greg Brockman
2010-07-20 5:16 ` [PATCH 2/4] git-shell-commands: Add a command to list bare repos Greg Brockman
2010-07-20 17:42 ` Junio C Hamano
2010-07-26 23:28 ` Greg Brockman
2010-07-20 5:16 ` [PATCH 3/4] git-shell-commands: Add a help command Greg Brockman
2010-07-20 5:16 ` [PATCH 4/4] Add interactive mode to git-shell for user-friendliness Greg Brockman
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=1279602972-1264-2-git-send-email-gdb@mit.edu \
--to=gdb@mit.edu \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=j.sixt@viscovery.net \
--cc=jrnieder@gmail.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).