On Sat, Jul 18, 2009 at 1:10 PM, brizly vaan van Ulciputz <brizly@xxxxxxxxxx> wrote: > > i think it could be the think with post-update. > But because i don't know for sure how to set it up, It was in the how to you mentioned. > comment: gitosis uses the same key as me as admin. isn't a problem, is > it? The user brizly exists on notebook as on s2 By "gitosis uses..." I presume you mean "the userid on the server that is being used as the gitosis user". Should not matter, normally, but see below > > (2) your gitosis.conf is all correct, but you forgot the "chmod" somewhere > > above, and the post-update hook never ran, so the real gitosis.conf (which > > gitosis uses -- this is ~git/.gitosis.conf) doesn't have the same data > > as mentioned above i don't know exactly where to set up the thing with > the post-update. And i actually don't have a git-user on the server (i > had one, but thought i didn't need one, so deleted it). you either follow howtos (good or bad) as closely as you can, or you understand enough about ssh to bypass it. You are mixing these two approaches; sorry I can't really help you. Let me say this: gitosis requires far more ssh knowledge than git knowledge. I do not want use this list to teach ssh, more than bare minimum. Anyway I have written quite a lot of stuff at http://sitaramc.github.com/0-installing/9-gitosis-server-install.html that might help you in understanding. > > I also don't like that howto; it appears to be doing everything on one > > machine, with the same userid, so people who don't grok ssh very well will > > still have trouble even after all this is done to translate that knowledge to a > > real deployment. > > Because my first run wasn't very successfull, i tried another tutorial > where the developer-machine and the gitosis-server are 2 different ones. > see http://www.shakthimaan.com/installs/gitosis.html > > > Bottom line: here's what should match for that error to go away: > > > > - the public key corresponding to the private key your client-side ssh is > > using > > - must match *exactly* one of the public keys in the server-side > > ~git/.ssh/authorized_keys > > see md5sums above, i think they are the same. You compared id_rsa.pub on both sides; you did not even compare the file I mentioned here (authorized_keys). Sorry. One mistake I made is I used the wrong emphasis above. "*exactly* one" should be read "exactly *one*" meaning it should not match more than one entry in the authorized_keys file. Oh the below para clarifies my intent anyway... > > [this is probably OK in your case, but please check there is *exactly one*. I > > have a vague memory of seeing a case when someone adds a key twice with > > different usernames in error. Ssh picks up perhaps the first one, while your > > gitosis.conf talks about the second one...] > So it is a problem when by 'normal' user on the server uses the same key > as gitosis does? The server is not only serving gitosis, an for other > reasons the user "brizly" is, for perspective of ssh, the same on > notebook and on server. Yes normally it is a problem. I repeat: this is nothing to do with gitosis; it is ssh knowledge you need. > > and > > - the name after "gitosis-init" on the pubkey line that matched above > > - must match a username in ~git/.gitosis.conf (which is a symlink to > > something but never mind) > > How do i check that? Since you did not even look in the file I asked you to look, I guess you would not find it... Summary: gitosis does require you to know a fair bit about unix and ssh. I'm sorry that most howtos pretend to whitewash all that. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html