Re: User authentication in GIT
- From
Johan Herland <johan@herland.net>
- Date
- Feb 7, 2012, 12:32 UTC
- Message-ID
- <CALKQrgdvOhfhTPg+g+LqCb6XOQczcz-nYC61B9x4W5dB4Up5oA@mail.gmail.com>
- In-Reply-To
- <1328615262741-7262113.post@n2.nabble.com>
On Tue, Feb 7, 2012 at 12:47, supadhyay <supadhyay@imany.com> wrote:
Show 10 quoted lines
> Hi Robin and Jakub, > > Thanks for your reply. But I am still not getting what exactly I need to > perform on GIT server. Please find my reply on your suggestion below: > > > 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.
- Each user generates their own ssh key pair on their own workstation (in openssh, the command for generating a new key is called 'ssh-keygen')
- Each user then sends their public key to you (using email or whatever communication form is easiest for you).
- You then load the keys into gitolite (by copying them into your local clone of the gitolite-admin repo, committing, and pushing to the gitolite-admin repo to the server).
More details here: http://sitaramc.github.com/gitolite/add.html (and in associated documentation)
Show 6 quoted lines
> 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?
No. You load them into gitolite (as described above, and in gitolite's documentation), and then gitolite takes care of managing them.
Have fun! :)
...Johan
-- Johan Herland, <johan@herland.net> www.herland.net