Among StackOverflow users [1], git-credential-store appears several times more popular than any other credential helper. Does this make anyone else uneasy? The docs warn that git-credential-store "stores your passwords unencrypted on disk" [2]. Are users sacrificing security for convenience? Firstly, how grave is storing credentials in plaintext? Software development guidelines such as CWE discourage storing credentials in plaintext [3]. Password managers in desktop environments, mobile operating systems and web browsers typically encrypt passwords on disk and guard them behind a master password. 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'. Thirdly, why doesn't everyone use SSH keys? Unlike HTTP remotes, upfront set-up is necessary to clone a public repo. For users unfamiliar with SSH, this set-up may be intimidating. Introducing users new to Git to SSH at the same time is a significant cognitive load. Any ideas how to improve the security of the average Git user? [1] https://stackoverflow.com/questions/35942754/how-can-i-save-username-and-password-in-git probably as good a survey of non-expert users as we can get [2] https://git-scm.com/docs/git-credential-store [3] https://cwe.mitre.org/data/definitions/256.html [4] https://github.blog/2020-12-15-token-authentication-requirements-for-git-operations/ [5] https://lore.kernel.org/git/20111210103444.GL16529@xxxxxxxxxxxxxxxxxxxxx/t/#u discussion at introduction of store helper
