Git, Cache HTTPS Password

From: https://stackoverflow.com/questions/5343068/is-there-a-way-to-skip-password-typing-when-using-https-on-github/5343146#5343146

With Git version 1.7.9 and later

Since Git 1.7.9 (released in late January 2012), there is a neat mechanism in Git to avoid having to type your password all the time for HTTP / HTTPS, called credential helpers. (Thanks to dazonic for pointing out this new feature in the comments below.)
With Git 1.7.9 or later, you can just use one of the following credential helpers:
git config --global credential.helper cache
... which tells Git to keep your password cached in memory for (by default) 15 minutes. You can set a longer timeout with:
git config --global credential.helper "cache --timeout=3600"
(That example was suggested in the GitHub help page for Linux.) You can also store your credentials permanently if so desired, see the other answers below.
GitHub's help also suggests that if you're on Mac OS X and used Homebrew to install Git, you can use the native Mac OS X keystore with:
git config --global credential.helper osxkeychain
For Windows, there is a helper called Git Credential Manager for Windows or wincred in msysgit.
git config --global credential.helper wincred # obsolete
With Git for Windows 2.7.3+ (March 2016):
git config --global credential.helper manager
For Linux, you can use gnome-keyring(or other keyring implementation such as KWallet).

With Git versions before 1.7.9

With versions of Git before 1.7.9, this more secure option is not available, and you'll need to change the URL that your origin remote uses to include the password in this fashion:
https://you:password@github.com/you/example.git
... in other words with :password after the username and before the @.
You can set a new URL for your origin remote with:
git config remote.origin.url https://you:password@github.com/you/example.git
Make sure that you use https, and you should be aware that if you do this, your GitHub password will be stored in plaintext in your .git directory, which is obviously undesirable.

With any Git version (well, since version 0.99)

An alternative approach is to put your username and password in your ~/.netrc file, although, as with keeping the password in the remote URL, this means that your password will be stored on the disk in plain text and is thus less secure and not recommended. However, if you want to take this approach, add the following line to your ~/.netrc:
machine <hostname> login <username> password <password>
... replacing <hostname> with the server's hostname, and <username> and <password> with your username and password. Also remember to set restrictive file system permissions on that file:
chmod 600 ~/.netrc
Note that on Windows, this file should be called _netrc, and you may need to define the %HOME% environment variable - for more details see:

Comments

Post a Comment

Popular posts from this blog

FFMPEG Deinterlacing Modes

FFMPEG has multiple supported deinterlacing filters.  Here they are: 10.14 bwdif Deinterlace the input video ("bwdif" stands for "Bob Weaver Deinterlacing Filter"). Motion adaptive deinterlacing based on yadif with the use of w3fdif and cubic interpolation algorithms. It accepts the following parameters: mode The interlacing mode to adopt. It accepts one of the following values: 0, send_frame Output one frame for each frame. 1, send_field Output one frame for each field. The default value is send_field. parity The picture field parity assumed for the input interlaced video. It accepts one of the following values: 0, tff Assume the top field is first. 1, bff Assume the bottom field is first. -1, auto Enable automatic detection of field parity. The default value is auto. If the interlacing is unknown or the decoder does not export this information, top field first will be assumed. deint Specify which frames to deinterlace. Accept ...
Read more

Remote debugging with GDB and GDBServer on Alpine and Visual Studio Code

Skip to end of metadata o to start of metadata gdb and gdbserver can be used in combination to provide debugging capabilities over the network.   gdbserver  is run on the machine you want to debug.   gdb  is run on the machine you want to debug from, usually your local machine. More  here . Before we get started, we need some software.  Alpine 3.8 will be the gdbserver. NFS We will be using nfs (Network File System) to mount a remote directory and have it look like a local directory.  We will cd to the nfs mounted directory which contains the program we want to debug before we launch gdb.  This way the program and symbols will match.  gdb will be running on your local client, but it will be launched when in a directory on the gdbserver's system. More than you wanted to know about  nfs . To set up nfs, you will need nfs software on your server and your client. SERVER  (Your Alpine machine) - Ad...
Read more

Build FFMPEG for Windows Using Visual Studio Toolchain

FFMPEG for Windows is built under MinGW or Cygwin.  We will be using MinGW. You may need ZLib, the ZLib provided with MinGW does not come with a .a file for some reason.  You can find ZLib at  https://zlib.net/ Build Zlib so that you get zlib.lib. Follow this page:  https://trac.ffmpeg.org/wiki/CompilationGuide/MSVC NOTE: When following the instructions on the above page, they only give a configure command for a release version, which is: ./configure --target-os=win64 --arch=x86_64 --toolchain=msvc If you want to do a full debug build, try this: ./configure --target-os=win64 --arch=x86_64 --toolchain=msvc --extra-cflags=" -EHa -nologo -D 'DEBUG' -D 'WINDOWS' -D 'HAVE_STRUCT_TIMESPEC' -D 'API_EXT_PARAM_LIST'" --enable-debug --disable-stripping --disable-optimizations --disable-cuda --disable-cuvid --disable-d3d11va --disable-dxva2 --disable-nvenc --disable-vaapi --disable-vdpau You should now be ready to use ffmpeg in a...
Read more