Git password authentication is shutting down (github.blog)

Article summary

GitHub is shutting down password authentication for Git operations, requiring users to use token-based authentication instead. This change aims to improve security by reducing the risk of password leaks and reuse. The change affects HTTPS access, including command line Git access and desktop applications. Users can use personal access tokens, OAuth, SSH keys, or GitHub App installation tokens for authentication.

Main themes

• password authentication shutdown
• token-based authentication
• security improvements
• authentication methods
• password management
• GitHub security policies

What commenters say

• Some users believe that this change is a good thing, as it improves security and reduces the risk of password leaks and reuse.
• Others think that this change is unnecessary and that password length requirements would have been a better solution.
• The use of token-based authentication is seen as a more secure alternative to password authentication, but some users are concerned about the potential complexity and inconvenience of managing tokens.
• There is a desire for more flexible and convenient authentication methods, such as repo-specific tokens or WebAuthn.
• Some users argue that passwords are not a significant security risk and that the benefits of token-based authentication do not outweigh the added complexity.
• Others believe that the industry should move away from passwords altogether and adopt more modern and secure authentication methods.
• The change may cause issues for old, forgotten systems that rely on password authentication, but it is seen as a necessary step towards improving security.
• Some users are concerned about the potential for tokens to be leaked or compromised, and the need for secure storage and management of tokens.