mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: M Hickford <>
To: Jeff King <>
Cc: M Hickford <>,,,,
Subject: Re: The enduring popularity of git-credential-store
Date: Sat, 11 Feb 2023 07:11:00 +0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Tue, 8 Nov 2022 at 15:41, Jeff King <> wrote:
> On Tue, Nov 08, 2022 at 10:50:33AM +0000, M Hickford wrote:
> > Secondly, the docs recommend git-credential-cache [2] which ships with
> > Git and is equally easy to configure. So why isn't it more popular? My
> > hypothesis: while caching works great for passwords typed from memory,
> > the combination of caching with personal access tokens has poor
> > usability. The unmemorised token is lost when the cache expires, so
> > the user has to generate a new token every session. I suspect GitHub's
> > 2021 decision to stop accepting passwords [4] may have inadvertently
> > pushed users from 'cache' to 'store'.
> Another big problem with credential-cache is that it requires Unix
> sockets, so it doesn't run on Windows.

Thanks to the work of Carlo Marcelo Arenas Belón [1], credential-cache
*can* be built on Windows 10 April 2018 update or later. But Git for
Windows has to support older Windows versions for many more years so
the build flag can't be enabled. Perhaps Git for Windows could ship
with a credential-cache binary that works on Windows 10 and gracefully
degrades on older Windows versions? That's beyond my expertise. Help
very welcome at

Might this be suitable for a GSoC project? If a mentor could be found.


  parent reply	other threads:[~2023-02-11  7:11 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-08 10:50 The enduring popularity of git-credential-store M Hickford
2022-11-08 12:00 ` Michal Suchánek
2022-11-08 15:41 ` Jeff King
2022-11-08 21:03   ` Taylor Blau
2023-02-11  7:11   ` M Hickford [this message]
2022-11-08 22:52 ` brian m. carlson
2022-11-12  2:30   ` M Hickford
2022-11-17 17:17   ` Matthew John Cheetham
2022-11-17 18:51     ` Jeff King
2022-11-17 19:29       ` Lessley Dennington
2022-11-17 20:43         ` Jeff King
2023-05-29  9:53           ` M Hickford
2023-05-28 19:33       ` M Hickford

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:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='' \ \ \ \ \ \ \

* 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.
Code repositories for project(s) associated with this public inbox

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 read-only IMAP folder(s) and NNTP newsgroup(s).