![]() There’s no default credential store for Linux though. On the other hand, gcm stores its credentials in the Keychain.app on macOS and Windows Credential Manager on Windows so it’s much more secure. Note that this may change in the future, see feat: Support for storing OAuth token in encrypted keychain for more info. I’ve briefly covered this topic in the previous section - With gh, after authenticating using gh auth login, the credential will be stored in the configuration file ~/.config/gh/hosts.yml as a plain text format. Also, with gcm, these tokens (application password and the Internet password for ) are the same. To delete the authentication token you should manually remove it from the credential store. With gcm, there’s no concept of logging out. Also, with gh, the token in the ~/.config/gh/hosts.yml file and the token in the Keychain.app (Internet password for ) are different (unsure why). With gh, this is the reason why you can still clone a private repo after running gh auth logout -h and can be really confusing. ![]() $ cat /Applications/Xcode.app/Contents/Developer/usr/share/git-core/gitconfigĭue to this configuration, the first time you clone a repo after authenticating with gh or gcm, a new OAuth access token will be stored in the Keychain.app in addition to the one that’s already generated for the OAuth app. ![]()
0 Comments
Leave a Reply. |