Shulou(Shulou.com)06/03 Report--

This article is to share with you the content of an example analysis of how GitHub abandons account password authentication. The editor thinks it is very practical, so share it with you as a reference and follow the editor to have a look.

If your Git operation has been failing or making errors on GitHub since yesterday, it's probably because you're still using password-based Git authentication, and now you need to change this setting.

GitHub announced its decision in July last year that it would no longer accept account passwords to verify Git operations, and now it is time to formally implement this decision. Authentication Git operations now require the use of SSH keys or token-based authentication.

"starting from 09:00 PST on August 13, 2021 (000 p.m. Beijing time on 14th), we will no longer accept account passwords when authenticating Git operations on GitHub.com," GitHub said on the official blog. "instead, all Git operations that require authentication will require token-based authentication."

Affected workflow

Command line access to Git

Desktop applications that use Git (GitHub Desktop is not affected)

Use a password to directly access any application / service of the Git repository on GitHub.com

Unaffected by this change:

If you have enabled two-step authentication for your account, you are already using token-based or SSH-based authentication

If we are using GitHub Enterprise Server, we have not announced any changes to our internal products

If you are maintaining a GitHub App,GitHub Apps that does not support password authentication

If you are still using a user name and password to verify Git operations, you should take the following steps to avoid exceptions after the new requirements are implemented.

For developers, if you are still using passwords to verify GitHub.com operations, you must start using personal access tokens with HTTPS (recommended) or SSH keys before August 13, 2021 to avoid interruption. If you are warned that you are using an outdated third-party integration, you should update your client to the latest version.

For integrators, you must use network or device authorization process authentication to authenticate the integration before August 13, 2021 to avoid disruption.

Tokens have many security advantages over password-based authentication:

Unique: tokens are specific to GitHub and can be generated by use or by device

Revocable: tokens can be revoked separately at any time without the need to update unaffected credentials

Limited: tokens can narrow down to allow only the access required by the use case

Random: tokens are not affected by dictionary types or brute force attempts that users need to remember or enter on a regular basis

Over the years, GitHub has improved the security of user accounts by adding two-step authentication, login reminders, authenticating devices, preventing the use of compromised passwords and WebAuthn support.

Thank you for reading! This is the end of the article on "sample analysis of GitHub giving up account password authentication". I hope the above content can be of some help to you, so that you can learn more knowledge. if you think the article is good, you can share it out for more people to see!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.