{"thread":{"id":"3268","subject":"git + ssh + key authentication feature-request","startedAt":"2006-02-08T21:58:26Z","lastAt":"2006-02-09T01:16:18Z","messageCount":15,"participants":["Nicolas Vilz 'niv'","Junio C Hamano","Linus Torvalds","Alan Chandler","Mark Wooding"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"15732","messageId":"7vhd79o6m5.fsf@assigned-by-dhcp.cox.net","threadId":"3268","inReplyTo":"43EA73C3.2040309@iaglans.de","subject":"Re: git + ssh + key authentication feature-request","fromName":"Junio C Hamano","fromEmail":"junkio@cox.net","sentAt":"2006-02-08T21:58:26Z","receivedAt":"2006-02-08T21:58:26Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Nicolas Vilz 'niv' writes:\n\n> I would like to ask if it is possible to use ssh keys to authenticate\n> via ssh on a git repository via git-pull/git-push. Since ssh supports\n> them, wouldn't it be nice to use them in git, too?\n\nPlease read what has been discussed within the last couple of\nweeks at least. I could say the last couple of months but I\nknow that is asking too much ;-).\n\nhttp://thread.gmane.org/gmane.comp.version-control.git/15462\n"},{"id":"15730","messageId":"43EA73C3.2040309@iaglans.de","threadId":"3268","inReplyTo":null,"subject":"git + ssh + key authentication feature-request","fromName":"Nicolas Vilz 'niv'","fromEmail":"niv@iaglans.de","sentAt":"2006-02-08T22:42:11Z","receivedAt":"2006-02-08T22:42:11Z","isPatch":false,"sender":{"key":"niv@iaglans.de","avatar":"https://gravatar.com/avatar/e4d43a32d721241212d4edb1d2210327e28423c913071b4bfeeaa0ce15296110?d=mp&s=160"},"body":"Hi guys,\n\nfirst of all, great work.\n\nI just discovered git and i like it.\n\nI would like to ask if it is possible to use ssh keys to authenticate \nvia ssh on a git repository via git-pull/git-push. Since ssh supports \nthem, wouldn't it be nice to use them in git, too?\n\nThe layout would be following:\n\nyou have a system user with a git-shell and several keys in \n.ssh/authorized_keys ... these are the keys of your contributors. They \nare allowed to login and work with the repository.\n\nI haven't found a posibility to get this. Maybe I haven't discovered it, \nyet...\n\nSincerly\nNicolas\n"},{"id":"15735","messageId":"Pine.LNX.4.64.0602081438390.2458@g5.osdl.org","threadId":"3268","inReplyTo":"43EA7D57.7040409@iaglans.de","subject":"Re: git + ssh + key authentication feature-request","fromName":"Linus Torvalds","fromEmail":"torvalds@osdl.org","sentAt":"2006-02-08T22:45:34Z","receivedAt":"2006-02-08T22:45:34Z","isPatch":false,"sender":{"key":"torvalds@linux-foundation.org","avatar":"https://avatars.githubusercontent.com/u/1024025?v=4"},"body":"\n\nOn Thu, 9 Feb 2006, Nicolas Vilz 'niv' wrote:\n> \n> in my case it would be only one system-user which has full access to several\n> repositories. At this time, the users which use that account, have to give a\n> password, which isn't that bad... it would be easier and more secure for me,\n> not to give a password, but ask the users for the ssh pubkey..\n\nThat is very much part of how the whole git-shell usage was envisioned.\n\nCreate a \"project\" account on some shared machine, create the project(s) \nin that accounts home directory, and set the login shell for that \nproject to \"git-shell\".\n\nThen you ask people who are part of the project to send in some ssh key \nfor that project. Then add those keys to the authorized_keys2 file for the \nproject, and voila, you all your participants can pull and push into it \nbut do not get any other access to the machine.\n\nIt _should_ all work perfectly fine. There are features you may want to \nadd, like logging (but sshd does some of that for you) and various \"admin\" \ncommands in addition to just plain push/pull. git-shell was really just a \nquick hack, and I don't know if anybody actually uses it.\n\nIn other words, it hasn't exactly been tested,\n\n\t\tLinus\n"},{"id":"15736","messageId":"7v4q39o3xs.fsf@assigned-by-dhcp.cox.net","threadId":"3268","inReplyTo":"43EA7D57.7040409@iaglans.de","subject":"Re: git + ssh + key authentication feature-request","fromName":"Junio C Hamano","fromEmail":"junkio@cox.net","sentAt":"2006-02-08T22:56:15Z","receivedAt":"2006-02-08T22:56:15Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Nicolas Vilz 'niv' writes:\n\n> in my case it would be only one system-user which has full access to\n> several repositories. At this time, the users which use that account,\n> have to give a password, which isn't that bad... it would be easier\n> and more secure for me, not to give a password, but ask the users for\n> the ssh pubkey..\n\nI do not know where you are getting the password idea.\n\nThe conclusion of that thread is that it is not worth trying to\nco-mingle more than one physical developer into one home\ndirectory, and does not have much to do with use of password or\npublic key authentication.\n\nThat thread describes:\n\n - you can use ssh public key authentication for developers;\n\n - you do not have to give them full shell access by using\n git-shell;\n \n - HOWEVER you cannot tell each developers apart if you add one\n key per developer to the same $HOME/.ssh/authorized_keys file.\n\nThe last point is not about git at all, but comes from how ssh\ndaemon operates. It roughly goes like this:\n\n - The client says \"I am me at the remote host, use this public\n key to prove that to the other end\". Often you do not have\n to give -l and -i but when you fully spell out the command\n line, it would be something like:\n\n\t$ ssh -l me -i identity-file remote.host.example.com\n\n Your client sends \"me\" and the public key to the remote end.\n\n - The ssh daemon running on the remote site says, \"Hmph, let's\n see if you are really \"me\" as you claim.\" It does the\n following things:\n\n 1. Look \"me\" up from its user database (be it /etc/passwd,\n NIS or LDAP) to find out the user's home directory.\n Let's say the \"struct passwd.pw_dir\" says it is\n \"/home/me\".\n\n 2. Check to see if /home/me/.ssh/authorized_keys exists, all\n the elements in the path to the file is secure (e.g. if\n /home/me/.ssh can be modified by somebody other than\n \"me\", what is in authorized_keys is not trustworthy).\n That means /home/me/.ssh/authorized_keys must be owned by\n \"me\" and at least mode 0644 or stricter.\n\n 3. Reads the keys in that file, and finds what is sent as\n the public key from the client.\n\n 4. Uses that public key to challenge the client to make sure\n the client has the corresponding private key.\n\nWhat this implies is that sharing the home directory among\nmultiple UNIX users would not work with ssh daemon the way you\nexpect. The check in step 2 would fail for all but one user.\n\nBeing able to list more than one key in authorized_keys is so\nthat you can use more than one key to become the _same_ user,\nand does not give you the ability to become a user other than\nthe one that owns that home directory on that remote host.\n\nSo while you could make a repository \"/pub/project.git\" the home\ndirectory of _one_ UNIX user, and store her key in the file\n\"/pub/project.git/.ssh/authorized_keys\", that would not work\nvery well for a shared repository setup if you want to be able\nto tell more than one physical users apart.\n\nYou _could_ tell them to use the same -l option and log-in as\nthe same UNIX user with their own keys, though. But that way\nyou cannot tell which developer pushed into the repository (of\ncourse if you trust the commits, commit log message would say\nthe committer ident).\n"},{"id":"15733","messageId":"43EA7D57.7040409@iaglans.de","threadId":"3268","inReplyTo":"7vhd79o6m5.fsf@assigned-by-dhcp.cox.net","subject":"Re: git + ssh + key authentication feature-request","fromName":"Nicolas Vilz 'niv'","fromEmail":"niv@iaglans.de","sentAt":"2006-02-08T23:23:03Z","receivedAt":"2006-02-08T23:23:03Z","isPatch":false,"sender":{"key":"niv@iaglans.de","avatar":"https://gravatar.com/avatar/e4d43a32d721241212d4edb1d2210327e28423c913071b4bfeeaa0ce15296110?d=mp&s=160"},"body":"Junio C Hamano wrote:\n> Nicolas Vilz 'niv' writes:\n> \n> \n>>I would like to ask if it is possible to use ssh keys to authenticate\n>>via ssh on a git repository via git-pull/git-push. Since ssh supports\n>>them, wouldn't it be nice to use them in git, too?\n> \n> \n> Please read what has been discussed within the last couple of\n> weeks at least. I could say the last couple of months but I\n> know that is asking too much ;-).\n> \n> http://thread.gmane.org/gmane.comp.version-control.git/15462\n> \n\nSorry, i haven't found that, yet, so i asked..\n\nin my case it would be only one system-user which has full access to \nseveral repositories. At this time, the users which use that account, \nhave to give a password, which isn't that bad... it would be easier and \nmore secure for me, not to give a password, but ask the users for the \nssh pubkey..\n\nI can still live with the password thing :)\n\nSincerly\nNicolas\n"},{"id":"15738","messageId":"200602082335.42449.alan@chandlerfamily.org.uk","threadId":"3268","inReplyTo":"43EA7D57.7040409@iaglans.de","subject":"Re: git + ssh + key authentication feature-request","fromName":"Alan Chandler","fromEmail":"alan@chandlerfamily.org.uk","sentAt":"2006-02-08T23:35:42Z","receivedAt":"2006-02-08T23:35:42Z","isPatch":false,"sender":{"key":"alan@chandlerfamily.org.uk","avatar":"https://gravatar.com/avatar/1862247e5ea8eac114c842f9dc3a5db6253754e24ef7171757cf97eedce48b8c?d=mp&s=160"},"body":"On Wednesday 08 February 2006 23:23, Nicolas Vilz 'niv' wrote:\n\n> in my case it would be only one system-user which has full access to\n> several repositories. At this time, the users which use that account,\n> have to give a password, which isn't that bad... it would be easier and\n> more secure for me, not to give a password, but ask the users for the\n> ssh pubkey..\n\nThis sounds like you haven't got sshd set up correctly. You can get it to log \nyou in soley based on keys, and whether or not you give a password is then \ndependent soley on whether your private key has a pass phrase or not and then \nwhether or not you are using some ssh-agent to remember them for you.\n\nI have it setup so that access to ssh controlled accounts is soley via key.\n\nPrivate keys remaining on fixed computers at home have no passphrase, my \nlaptop has a private key with a passphrase which I enter once on login.\n\nI have several accounts around the place with my public keys enumerated in \ntheir .ssh/authorized_keys file, so I have been able to contact git \nrepositories with urls like\n\ngit@www.chandlerfamily.org.uk\nwww-data@www.chandlerfamily.org.uk\n and for my own account\njust www.chandlerfamily.org.uk\n\nall without entering a password.\n\nBut following the discussion thread Junio pointed to I have converted \neverything to shared repositories and I now only use my own account to log \nin.\n\n-- \nAlan Chandler\nhttp://www.chandlerfamily.org.uk\nOpen Source. It's the difference between trust and antitrust.\n"},{"id":"15742","messageId":"Pine.LNX.4.64.0602081545330.2458@g5.osdl.org","threadId":"3268","inReplyTo":"43EA8DDA.3070906@iaglans.de","subject":"Re: git + ssh + key authentication feature-request","fromName":"Linus Torvalds","fromEmail":"torvalds@osdl.org","sentAt":"2006-02-08T23:50:56Z","receivedAt":"2006-02-08T23:50:56Z","isPatch":false,"sender":{"key":"torvalds@linux-foundation.org","avatar":"https://avatars.githubusercontent.com/u/1024025?v=4"},"body":"\n\nOn Thu, 9 Feb 2006, Nicolas Vilz 'niv' wrote:\n> \n> So, how do i tell git to send my identity-file to sshd? And could I set an\n> alias like in .git/remotes for that location / identity?\n\nUse a \"fake host\".\n\nIe, let's say that your project is \"project@host.com\", then make each user \njust have in their .ssh/config:\n\n\thost project.host.com\n\t\tUser project\n\t\tHostName host.com\n\t\tIdentityFile /home/myhome/project-key\n\nand there you are. Just use \"project.host.com:repo-name\" as the thing you \npull and push from.\n\n(Yeah, I forget the exact ssh config file format, so you should \ndouble-check that.)\n\n\t\tLinus\n"},{"id":"15743","messageId":"7vzml1mmmh.fsf@assigned-by-dhcp.cox.net","threadId":"3268","inReplyTo":"43EA8DDA.3070906@iaglans.de","subject":"Re: git + ssh + key authentication feature-request","fromName":"Junio C Hamano","fromEmail":"junkio@cox.net","sentAt":"2006-02-08T23:55:34Z","receivedAt":"2006-02-08T23:55:34Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Nicolas Vilz 'niv' writes:\n\n> So, how do i tell git to send my identity-file to sshd? And could I\n> set an alias like in .git/remotes for that location / identity?\n\nThat is not a git question but you are using me as an ssh\nhelpdesk. See ssh_config(5).\n\nThe answers are:\n\n\tIdentityFile\n User\n\nFor example, I have this in my .ssh/config on my local machine:\n\n Host osiris.pyramid.com\n User junio\n IdentityFile ~/.ssh/osiris-pub\n ForwardAgent no\n ForwardX11 no\n\nWithout \"User\", it would send out \"junkio\", so I have that line\nto override it (I could do it with -l command line, but there is\nno point because that is I would use _always_ to go there).\nWithout \"IdentityFile\" it would use ~/.ssh/identity (same\nrationale with -i), which is the identity file I usually use for\nother sites.\n"},{"id":"15749","messageId":"slrndul2bq.2i8.mdw@metalzone.distorted.org.uk","threadId":"3268","inReplyTo":"7v4q39o3xs.fsf@assigned-by-dhcp.cox.net","subject":"Re: git + ssh + key authentication feature-request","fromName":"Mark Wooding","fromEmail":"mdw@distorted.org.uk","sentAt":"2006-02-09T00:14:50Z","receivedAt":"2006-02-09T00:14:50Z","isPatch":false,"sender":{"key":"mdw@distorted.org.uk","avatar":null},"body":"Junio C Hamano wrote:\n\n> So while you could make a repository \"/pub/project.git\" the home\n> directory of _one_ UNIX user, and store her key in the file\n> \"/pub/project.git/.ssh/authorized_keys\", that would not work\n> very well for a shared repository setup if you want to be able\n> to tell more than one physical users apart.\n\nAhh! But you can. The trick is to set the remote user's identity based\non the key he uses to authenticate himself. This doesn't work if you\nuse password authentication. You add items of the form\n`environment=\"VAR=VALUE\"' to the end of each authorized_keys entry, as\nappropriate for whoever it is that owns the corresponding private key;\nthe GIT_{AUTHOR,COMMITTER}_{NAME,EMAIL} variables are ideal choices to\nset here. You could set some other variables and do some more\nsophisticated checking of who's doing what, which would require souping\nup git-daemon somewhat, but I don't think it's beyond the realms of\npossibility.\n\nIt's important that your users can't use this SSH access to mess with\nthe shared user's SSH configuration itself, but, hey, that sort of\nrestricted access is what git-daemon is for, right?\n\n> You _could_ tell them to use the same -l option and log-in as the same\n> UNIX user with their own keys, though. But that way you cannot tell\n> which developer pushed into the repository (of course if you trust the\n> commits, commit log message would say the committer ident).\n\nI think the problem there is more that the commits themselves were\ncreated elsewhere, where this server wasn't watching, and therefore it\npretty much has to take the committer and author information there on\ntrust.\n\n-- [mdw]\n"},{"id":"15737","messageId":"43EA8DDA.3070906@iaglans.de","threadId":"3268","inReplyTo":"7v4q39o3xs.fsf@assigned-by-dhcp.cox.net","subject":"Re: git + ssh + key authentication feature-request","fromName":"Nicolas Vilz 'niv'","fromEmail":"niv@iaglans.de","sentAt":"2006-02-09T00:33:30Z","receivedAt":"2006-02-09T00:33:30Z","isPatch":false,"sender":{"key":"niv@iaglans.de","avatar":"https://gravatar.com/avatar/e4d43a32d721241212d4edb1d2210327e28423c913071b4bfeeaa0ce15296110?d=mp&s=160"},"body":"Junio C Hamano wrote:\n> Nicolas Vilz 'niv' writes:\n> \n> \n>>in my case it would be only one system-user which has full access to\n>>several repositories. At this time, the users which use that account,\n>>have to give a password, which isn't that bad... it would be easier\n>>and more secure for me, not to give a password, but ask the users for\n>>the ssh pubkey..\n\n[... how sshd operates ...]\n\n> You _could_ tell them to use the same -l option and log-in as\n> the same UNIX user with their own keys, though. But that way\n> you cannot tell which developer pushed into the repository (of\n> course if you trust the commits, commit log message would say\n> the committer ident).\n\nI think this (last) scenario would match my thoughts best :)\n\nExactly that was, what i was trying to do, although I couldn't tell git \nto send my identify-file. That was (more or less) my initial-question \n(howto do that, the ssh option -i) :)\n\nYou got a point which i haven't recognized, yet...\n\nI really can't tell later on which developer pushed unless i trust the \ncommit-messages. I will think about that.\n\nSo, how do i tell git to send my identity-file to sshd? And could I set \nan alias like in .git/remotes for that location / identity?\n\nThank you very much for your explanations and help.\n\nSincerly\nNicolas\n"},{"id":"15752","messageId":"7vacd1mkk9.fsf@assigned-by-dhcp.cox.net","threadId":"3268","inReplyTo":"slrndul2bq.2i8.mdw@metalzone.distorted.org.uk","subject":"Re: git + ssh + key authentication feature-request","fromName":"Junio C Hamano","fromEmail":"junkio@cox.net","sentAt":"2006-02-09T00:40:06Z","receivedAt":"2006-02-09T00:40:06Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Mark Wooding writes:\n\n> It's important that your users can't use this SSH access to mess with\n> the shared user's SSH configuration itself, but, hey, that sort of\n> restricted access is what git-daemon is for, right?\n\nCorrect modulo s/git-daemon/git-shell/.\n\n> I think the problem there is more that the commits themselves were\n> created elsewhere, where this server wasn't watching, and therefore it\n> pretty much has to take the committer and author information there on\n> trust.\n\nThat's an different issue. Anybody could create bogus commits\nall they want based on somebody else's history. Making\nrefs/{heads,tags}/ pointers to point at the tip of a development\ntail that contains such bogus commits is something you would\nwant to have control upon.\n\nFor example, Documentation/howto/update-hook-example shows\nCarl's idea to implement access control using the unix user\nidentity (because it assumes you set up one home directory per\ndeveloper to use public key authentication to cause sshd to give\na true unix uid to an incoming connection) to make sure who can\nupdate which head. By updating a branch head, the developer is\nasserts that the development trail that led to it is something\nshe feels valid.\n\nNow, you brought up an interesting way to do this without using\nunix uid. Some sshd installations do not honour environment=\nsettings, but that problem aside, you could define a token, say\nGIT_USER, with different value on each line in the shared\nauthorized_keys file so that you can distinguish incoming\ndevelopers that share the same \"home directory\", and change the\nexample hook Carl gave us to use that token instead of the unix\nuser identity. I'd imagine that would work quite well.\n"},{"id":"15740","messageId":"43EA901D.3030008@iaglans.de","threadId":"3268","inReplyTo":"Pine.LNX.4.64.0602081438390.2458@g5.osdl.org","subject":"Re: git + ssh + key authentication feature-request","fromName":"Nicolas Vilz 'niv'","fromEmail":"niv@iaglans.de","sentAt":"2006-02-09T00:43:09Z","receivedAt":"2006-02-09T00:43:09Z","isPatch":false,"sender":{"key":"niv@iaglans.de","avatar":"https://gravatar.com/avatar/e4d43a32d721241212d4edb1d2210327e28423c913071b4bfeeaa0ce15296110?d=mp&s=160"},"body":"Linus Torvalds wrote:\n> Create a \"project\" account on some shared machine, create the project(s) \n> in that accounts home directory, and set the login shell for that \n> project to \"git-shell\".\n\ndone..\n\n> It _should_ all work perfectly fine. There are features you may want to \n> add, like logging (but sshd does some of that for you) and various \"admin\" \n> commands in addition to just plain push/pull. git-shell was really just a \n> quick hack, and I don't know if anybody actually uses it.\n\nI would like to use it.. i searched for something like scponly for ssh \njust for git.. and I found git-shell.\n\nas long as i can modify and setup git-repositories myself, i haven't \nneeded admin-commands, yet...\n\nas mentioned in the thread, i still search for a posibility to tell git \nto send my identify-file... and possibly set an alias for this command :)\n\nssh with bash for this account and the keys works... ssh with git-shell \ndoes work, too... (What do you think I am? A shell?) but git with keys \nand ssh transport, that is what i don't get working :)\n\nNicolas\n"},{"id":"15753","messageId":"slrndul4oi.2i8.mdw@metalzone.distorted.org.uk","threadId":"3268","inReplyTo":"7vacd1mkk9.fsf@assigned-by-dhcp.cox.net","subject":"Re: git + ssh + key authentication feature-request","fromName":"Mark Wooding","fromEmail":"mdw@distorted.org.uk","sentAt":"2006-02-09T00:55:46Z","receivedAt":"2006-02-09T00:55:46Z","isPatch":false,"sender":{"key":"mdw@distorted.org.uk","avatar":null},"body":"Junio C Hamano wrote:\n\n> Correct modulo s/git-daemon/git-shell/.\n\nD'oh! Finger trouble!\n\n> Now, you brought up an interesting way to do this without using\n> unix uid. Some sshd installations do not honour environment=\n> settings, but that problem aside, you could define a token, say\n> GIT_USER, with different value on each line in the shared\n> authorized_keys file so that you can distinguish incoming\n> developers that share the same \"home directory\", and change the\n> example hook Carl gave us to use that token instead of the unix\n> user identity. I'd imagine that would work quite well.\n\nQuite possibly.\n\nDon't give me the credit here, by the way. I completely stole this\nwhole idea from the Subversion documentation: see `SSH configuration\ntricks' in \n\n http://svnbook.red-bean.com/nightly/en/svn.serverconfig.svnserve.html\n\nat the bottom.\n\nOh, any my mistake: the `environment...' options go at the beginning of\nan authorized_keys line, not at the end.\n\nIt's so time I went to sleep.\n\n-- [mdw]\n"},{"id":"15748","messageId":"43EA958E.1090902@iaglans.de","threadId":"3268","inReplyTo":"7vzml1mmmh.fsf@assigned-by-dhcp.cox.net","subject":"Re: git + ssh + key authentication feature-request","fromName":"Nicolas Vilz 'niv'","fromEmail":"niv@iaglans.de","sentAt":"2006-02-09T01:06:22Z","receivedAt":"2006-02-09T01:06:22Z","isPatch":false,"sender":{"key":"niv@iaglans.de","avatar":"https://gravatar.com/avatar/e4d43a32d721241212d4edb1d2210327e28423c913071b4bfeeaa0ce15296110?d=mp&s=160"},"body":"Junio C Hamano wrote:\n> Nicolas Vilz 'niv' writes:\n> \n> \n>>So, how do i tell git to send my identity-file to sshd? And could I\n>>set an alias like in .git/remotes for that location / identity?\n> \n> \n> That is not a git question but you are using me as an ssh\n> helpdesk. See ssh_config(5).\ni didn't recognize that it had nothing to do with git.\n\nThank you very much for your help and your time. :)\n\nNicolas\n"},{"id":"15750","messageId":"43EA97E2.5060700@iaglans.de","threadId":"3268","inReplyTo":"Pine.LNX.4.64.0602081545330.2458@g5.osdl.org","subject":"Re: git + ssh + key authentication feature-request","fromName":"Nicolas Vilz 'niv'","fromEmail":"niv@iaglans.de","sentAt":"2006-02-09T01:16:18Z","receivedAt":"2006-02-09T01:16:18Z","isPatch":false,"sender":{"key":"niv@iaglans.de","avatar":"https://gravatar.com/avatar/e4d43a32d721241212d4edb1d2210327e28423c913071b4bfeeaa0ce15296110?d=mp&s=160"},"body":"Linus Torvalds wrote:\n> \n> On Thu, 9 Feb 2006, Nicolas Vilz 'niv' wrote:\n> \n>>So, how do i tell git to send my identity-file to sshd? And could I set an\n>>alias like in .git/remotes for that location / identity?\n> \n> \n> Use a \"fake host\".\n> \n[...ssh config...]\n\n> \n> (Yeah, I forget the exact ssh config file format, so you should \n> double-check that.)\n\ni will do that.. :))\n\nI thank you all for your help.\n\nNicolas\n"}]}