Login or Register to Ask a Question and Join Our Community

Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

git-credential-store(1) [xfree86 man page]

GIT-CREDENTIAL-STO(1)						    Git Manual						     GIT-CREDENTIAL-STO(1)

NAME

       git-credential-store - Helper to store credentials on disk

SYNOPSIS

       git config credential.helper 'store [options]'

DESCRIPTION

	   Note
	   Using this helper will store your passwords unencrypted on disk, protected only by filesystem permissions. If this is not an acceptable
	   security tradeoff, try git-credential-cache(1), or find a helper that integrates with secure storage provided by your operating system.

       This command stores credentials indefinitely on disk for use by future Git programs.

       You probably don't want to invoke this command directly; it is meant to be used as a credential helper by other parts of git. See
       gitcredentials(7) or EXAMPLES below.

OPTIONS

       --file=<path>
	   Use <path> to lookup and store credentials. The file will have its filesystem permissions set to prevent other users on the system from
	   reading it, but will not be encrypted or otherwise protected. If not specified, credentials will be searched for from
	   ~/.git-credentials and $XDG_CONFIG_HOME/git/credentials, and credentials will be written to ~/.git-credentials if it exists, or
	   $XDG_CONFIG_HOME/git/credentials if it exists and the former does not. See also the section called "FILES".

FILES

       If not set explicitly with --file, there are two files where git-credential-store will search for credentials in order of precedence:

       ~/.git-credentials
	   User-specific credentials file.

       $XDG_CONFIG_HOME/git/credentials
	   Second user-specific credentials file. If $XDG_CONFIG_HOME is not set or empty, $HOME/.config/git/credentials will be used. Any
	   credentials stored in this file will not be used if ~/.git-credentials has a matching credential as well. It is a good idea not to
	   create this file if you sometimes use older versions of Git that do not support it.

       For credential lookups, the files are read in the order given above, with the first matching credential found taking precedence over
       credentials found in files further down the list.

       Credential storage will by default write to the first existing file in the list. If none of these files exist, ~/.git-credentials will be
       created and written to.

       When erasing credentials, matching credentials will be erased from all files.

EXAMPLES

       The point of this helper is to reduce the number of times you must type your username or password. For example:

	   $ git config credential.helper store
	   $ git push http://example.com/repo.git
	   Username: <type your username>
	   Password: <type your password>

	   [several days later]
	   $ git push http://example.com/repo.git
	   [your credentials are used automatically]

STORAGE FORMAT

       The .git-credentials file is stored in plaintext. Each credential is stored on its own line as a URL like:

	   https://user:pass@example.com

       When Git needs authentication for a particular URL context, credential-store will consider that context a pattern to match against each
       entry in the credentials file. If the protocol, hostname, and username (if we already have one) match, then the password is returned to
       Git. See the discussion of configuration in gitcredentials(7) for more information.

GIT

       Part of the git(1) suite

Git 2.17.1							    10/05/2018						     GIT-CREDENTIAL-STO(1)

Check Out this Related Man Page

GIT-CREDENTIAL-CAC(1)                                               Git Manual                                               GIT-CREDENTIAL-CAC(1)

NAME

       git-credential-cache - Helper to temporarily store passwords in memory

SYNOPSIS

       git config credential.helper 'cache [options]'

DESCRIPTION

       This command caches credentials in memory for use by future Git programs. The stored credentials never touch the disk, and are forgotten
       after a configurable timeout. The cache is accessible over a Unix domain socket, restricted to the current user by filesystem permissions.

       You probably don't want to invoke this command directly; it is meant to be used as a credential helper by other parts of Git. See
       gitcredentials(7) or EXAMPLES below.

OPTIONS

       --timeout <seconds>
           Number of seconds to cache credentials (default: 900).

       --socket <path>
           Use <path> to contact a running cache daemon (or start a new cache daemon if one is not started). Defaults to
           $XDG_CACHE_HOME/git/credential/socket unless ~/.git-credential-cache/ exists in which case ~/.git-credential-cache/socket is used
           instead. If your home directory is on a network-mounted filesystem, you may need to change this to a local filesystem. You must specify
           an absolute path.

CONTROLLING THE DAEMON

       If you would like the daemon to exit early, forgetting all cached credentials before their timeout, you can issue an exit action:

           git credential-cache exit

EXAMPLES

       The point of this helper is to reduce the number of times you must type your username or password. For example:

           $ git config credential.helper cache
           $ git push http://example.com/repo.git
           Username: <type your username>
           Password: <type your password>

           [work for 5 more minutes]
           $ git push http://example.com/repo.git
           [your credentials are used automatically]

       You can provide options via the credential.helper configuration variable (this example drops the cache time to 5 minutes):

           $ git config credential.helper 'cache --timeout=300'

GIT

       Part of the git(1) suite

Git 2.17.1                                                          10/05/2018                                               GIT-CREDENTIAL-CAC(1)
Man Page