GitHub on the decision to discontinue support for password authentication when connecting to Git. Direct execution of operations requiring authentication will only be possible using SSH keys or tokens (personal GitHub tokens or OAuth). A similar restriction will also apply to the REST API. New authentication rules for the API will take effect on November 13, and the tightening of access to Git is scheduled for the middle of next year. An exception will be granted only to accounts using , which will be able to connect to Git using a password and an additional verification code.
It is expected that tightening authentication requirements will help protect users from the compromise of their repositories in the event of user database leaks or hacks of third-party services where users have reused passwords with GitHub. Benefits of token authentication include the ability to generate separate tokens for specific devices and sessions, the support for revoking compromised tokens without changing credentials, the ability to restrict access scope via tokens, and the resilience of tokens against brute force attacks.
Source: opennet.ru
