Inline respon On Tue, Feb 7, 2012 at 12:47 PM, supadhyay <supadhyay@xxxxxxxxx> wrote: > Hi Robin and Jakub, > ... > Robin: > All users must have their own SSH key. You do not create keys for them. > My rely: can you please give some more idea about how it works.. I am not > getting this or if you can provide any link for this to understand. SSH authentication can use private/public keys. The user generates a keypair on their computer and gives you their public key, the private key stays on their computer. > > Jakub: > My reply: existing version control system used pserver protocol. > > You would still need for each user to generate their own SSH key. > My reply: Do I need to store all end users sSH key in .ssh/authorized_keys > file on GIT server? If you were to do it manually, yes. But if you use gitolite [1], then you add them to another git repository which handles everything for you. > -- > View this message in context: http://git.661346.n2.nabble.com/User-authentication-in-GIT-tp7261349p7262113.html > Sent from the git mailing list archive at Nabble.com. > -- > 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 [1]: https://github.com/sitaramc/gitolite -- 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