In accordance with the previously intended plan, GitHub stops Support for connecting to GIT objects using password authentication. The change will be applied today at 19 o’clock (MSK), after which the direct execution of GIT operations that require authentication will be possible only when using SSH keys or tokens (personal tokens Github or Oauth). The exception is provided only by accounts using two-factor authentication, which are connected to the GIT by password and an additional key.
It is assumed that the tightening of authentication requirements will allow you to protect users from compromising their repository in the event of a leakage of custom bases or hacking third-party services, on which users used the same passwords with GitHub. From the advantages of authentication on tokens, it is called the possibility of generating individual tokens for specific devices and sessions, supporting the recall of compounded tokens without changing accounting data, the ability to restrict access areas through the token, the impotence of tokens by definition by the Brute Force.