On Wed, 9 Oct 2013 01:31:36 -0700 (PDT)
Alfredo Licciardello <licciardello.alfr...@gmail.com> wrote:
> I use gitolite to admin my Repositories GIT. Following my problem:
> I added in the configuration file of git “gitolite.conf” a new user
> to work on an old GIT repository and in the same time the user sent
> me his “public key”. I copied the new .pub file in the keydir
> directory and I run the push on the origin. So I inserted that key on
> Git ADM repository, for me that’s all.
> The problem is when the user “clone” the repository using the
> “git clone user@server:Repo_Name”
> Git ask him always the password and doesn’t permit the clone, why
> in your opinion?
The main idea behind gitolite is is *virtualizing* the users which
access the repositories this tool manages -- this allows to set up only
a single system user account (usually "gitolite" or just "git") and use
it for all access *while still using personal SSH keys for
authentication.* That is, your developer should specify the user name
matching whatever system account has been created while setting up
gitolite but use its own SSH key for authentication, so everyone in
your shop has to user repo URLs like "git@server:repo" or
"gitolite@server:repo" -- the actual distinguishing between "real"
users is done by gitolite itself based on their SSH keys.
You probably should take another stab at reading .
You received this message because you are subscribed to the Google Groups "Git
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email
For more options, visit https://groups.google.com/groups/opt_out.