On Sun, Jun 08, 2014 at 01:15:48PM -0700, Thomas Ferris Nicolaisen wrote:
> On Sunday, June 8, 2014 8:34:32 PM UTC+2, wkevin wrote:
>> Hello, 
>> I an working against a git server where I need to enter the
>> password each time I perform git clone.  Is there a way to set some
>> entry in a git configuration file, like is done with user.name, for
>> example, (security is not an issue here as this repository does not
>> contain real secured things), so that I will not have to use this
>> password anymore ? 
> Note that Git is a transport and storage protocol which doesn't
> involve itself with authentication, so you need to automate (or
> remove) authentication in the surrounding platform, depending on
> which protocol and Git server (which you offered very little detail
> about by the way) you are using.
> I think one of these is the answers you are looking for, in order of
> which option is more likely to fit, statistically:
> a) You want to set up a SSH keypair and clone over SSH [1]. The urls
> for this typically look something like git@server:path/to/repo or
> ssh://user@server:path/to/repo. Your SSH key will take care of the
> authentication for you, so you're not prompted for password (unless
> you have protected the key with a passphrase, in which case you'll
> be prompted for the passphrase once in a while.
> b) You are cloning over HTTP(S). In this case you have a couple of
> options: (1) Hard-code your username and password in the .netrc
> file, or set up some credential helper so you will only be prompted
> for password once in a while [2].
> c) You are in control of the Git server yourself, in which case you
> can expose a repository open to all, using the Git daemon, and never
> be prompted for password again - urls will start with git:// [3]

d) If you already have an HTTP-server serving some web-based way of
inspecting the git repo (or serving it using the https protocol) you
can read the man-page of git-http-backend on how to set up read-only
access via http://.


Magnus Therning                      OpenPGP: 0xAB4DFBA4 
email: mag...@therning.org   jabber: mag...@therning.org
twitter: magthe               http://therning.org/magnus

As long as there are ill-defined goals, bizarre bugs, and unrealistic
schedules, there will be Real Programmers willing to jump in and Solve The
Problem, saving the documentation for later.  Long live Fortran!
     -- Ed Post

Attachment: pgprGdFXCFEmd.pgp
Description: PGP signature

Reply via email to