git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: supadhyay <supadhyay@imany.com>
Cc: git@vger.kernel.org
Subject: Re: User authentication in GIT
Date: Tue, 07 Feb 2012 01:12:21 -0800 (PST)	[thread overview]
Message-ID: <m3aa4vknwv.fsf@localhost.localdomain> (raw)
In-Reply-To: <1328595129258-7261349.post@n2.nabble.com>

supadhyay <supadhyay@imany.com> writes:

> I want to migrate my existing version control system (CVS) into GIT. The
> first question which comes to me is in CVS we have user authentication like
> username and their password while in GIT there is SSH authentication. 

Do you use _unencrypted_ pserver, or tunelling over SSH (with CVS_RSH)?
 
> Can any one suggest me what is the optimal way to manage the users in GIT?
> Does all users having username, passoword and SSH key? or there is no users
> credential but only SSH authentication? if I have 1000 users in old system
> CVS then do I need to create a key for all 1000 users in GIT? or etc.

First, Git supports unauthenticated anonymous fetching via custom
git:// protocol and via HTTP.  If you only need read-only access to
repository, it would be enough.  No account or SSH key necessary.

Second, Git uses SSH for authenthication instead of hand-rolling its
own security system, badly.  You don't need to create 1000 shell
accounts for SSH access: use tool like gitolite to manage git
repositories, which uses public-key infrastructure without need to
generate 1000 accounts.  You would still need for each user to
generate their own SSH key.

See gitolite documentation for more detail (older gitosis tool is no
longer maintained, as far as I know).

HTH
-- 
Jakub Narebski

  parent reply	other threads:[~2012-02-07  9:12 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 [this message]
2012-02-07 11:47 ` supadhyay
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=m3aa4vknwv.fsf@localhost.localdomain \
    --to=jnareb@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=supadhyay@imany.com \
    /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).