From: Nicolas Vilz 'niv' <niv@iaglans•de>
To: git@vger•kernel.org
Subject: Re: git + ssh + key authentication feature-request
Date: Thu, 09 Feb 2006 01:43:09 +0100 [thread overview]
Message-ID: <43EA901D.3030008@iaglans.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0602081438390.2458@g5.osdl.org>
Linus Torvalds wrote:
> Create a "project" account on some shared machine, create the project(s)
> in that accounts home directory, and set the login shell for that
> project to "git-shell".
done..
> It _should_ all work perfectly fine. There are features you may want to
> add, like logging (but sshd does some of that for you) and various "admin"
> commands in addition to just plain push/pull. git-shell was really just a
> quick hack, and I don't know if anybody actually uses it.
I would like to use it.. i searched for something like scponly for ssh
just for git.. and I found git-shell.
as long as i can modify and setup git-repositories myself, i haven't
needed admin-commands, yet...
as mentioned in the thread, i still search for a posibility to tell git
to send my identify-file... and possibly set an alias for this command :)
ssh with bash for this account and the keys works... ssh with git-shell
does work, too... (What do you think I am? A shell?) but git with keys
and ssh transport, that is what i don't get working :)
Nicolas
next prev parent reply other threads:[~2006-02-08 23:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-08 22:42 git + ssh + key authentication feature-request Nicolas Vilz 'niv'
2006-02-08 21:58 ` Junio C Hamano
2006-02-08 23:23 ` Nicolas Vilz 'niv'
2006-02-08 22:45 ` Linus Torvalds
2006-02-09 0:43 ` Nicolas Vilz 'niv' [this message]
2006-02-08 22:56 ` Junio C Hamano
2006-02-09 0:14 ` Mark Wooding
2006-02-09 0:40 ` Junio C Hamano
2006-02-09 0:55 ` Mark Wooding
2006-02-09 0:33 ` Nicolas Vilz 'niv'
2006-02-08 23:50 ` Linus Torvalds
2006-02-09 1:16 ` Nicolas Vilz 'niv'
2006-02-08 23:55 ` Junio C Hamano
2006-02-09 1:06 ` Nicolas Vilz 'niv'
2006-02-08 23:35 ` Alan Chandler
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=43EA901D.3030008@iaglans.de \
--to=niv@iaglans$(echo .)de \
--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