git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: supadhyay <supadhyay@imany.com>
To: git@vger.kernel.org
Subject: Re: User authentication in GIT
Date: Tue, 7 Feb 2012 03:47:42 -0800 (PST)	[thread overview]
Message-ID: <1328615262741-7262113.post@n2.nabble.com> (raw)
In-Reply-To: <1328595129258-7261349.post@n2.nabble.com>

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.


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?


--
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.

  parent reply	other threads:[~2012-02-07 11:47 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-07  6:12 User authentication in GIT supadhyay
2012-02-07  7:30 ` Robin H. Johnson
2012-02-07  9:12 ` Jakub Narebski
2012-02-07 11:47 ` supadhyay [this message]
2012-02-07 12:31   ` compufreak
2012-02-07 12:32   ` Johan Herland
2012-02-07 16:40     ` supadhyay
2012-02-07 18:26       ` Sitaram Chamarty
2012-02-10 16:57         ` supadhyay
2012-02-11  5:17           ` Sitaram Chamarty
2012-02-13 12:54             ` supadhyay
2012-02-13 14:32               ` Sitaram Chamarty
2012-02-13 18:19                 ` supadhyay

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=1328615262741-7262113.post@n2.nabble.com \
    --to=supadhyay@imany.com \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).