IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!

 

git.exe pull --progress -v --no-rebase "origin"
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@       WARNING: POSSIBLE DNS SPOOFING DETECTED!          @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
The RSA host key for github.com has changed,
and the key for the corresponding IP address 140.82.121.4
is unknown. This could either mean that
DNS SPOOFING is happening or the IP address for the host
and its host key have changed at the same time.
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@    WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!     @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that a host key has just been changed.
The fingerprint for the RSA key sent by the remote host is
SHA256:uNiVztksCsDhcc0u9e8BujQXVUpKZIDTMczCvj3tD2s.
Please contact your system administrator.
Add correct host key in /c/Users/xu/.ssh/known_hosts to get rid of this message.
Offending RSA key in /c/Users/xu/.ssh/known_hosts:1
RSA host key for github.com has changed and you have requested strict checking.
Host key verification failed.
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.


git did not exit cleanly (exit code 1) (13641 ms @ 2023/4/9 11:31:21)

solution:


1. What is Git?

Git is currently the most advanced distributed version control system in the world (no one).
Git is an open source distributed version control software for effective and high-speed processing of version management from small to very large projects. Git was originally designed and developed by Linus Torvalds to manage Linux kernel development.
GitHub is a Git-based remote file hosting platform (same as GitCafe, BitBucket, and GitLab, etc.).
Git itself is fully capable of version control, but all its content and version records can only be saved locally. If you want to save file content and version records remotely at the same time, you need to use it in combination with GitHub. Usage scenario:
No GitHub: maintain the elapsed files in the local .git folder
With GitHub: maintain the elapsed files in the local .git folder, and also host the elapsed files in the remote warehouse
II. Git history

Like many great events in life, Git was born in an era of great controversy and innovation. The Linux kernel open source project has a wide range of participants. The vast majority of Linux kernel maintenance work is spent on the tedious business of submitting patches and keeping archives (1991-2002). By 2002, the entire project team began to use the distributed version control system BitKeeper to manage and maintain the code.

By 2005, the partnership between the commercial company that developed BitKeeper and the Linux kernel open source community ended, and they took back the right to use BitKeeper for free. This forces the Linux open source community (especially Linus Torvalds, the creator of Linux) to learn a lesson, and only by developing a version control system of its own will it not repeat the same mistakes. They set several goals for the new system:


    Simple design     for speed
    Strong support for non-linear development models (allowing thousands of parallel development branches)
    Fully distributed
    Ability to efficiently manage very large-scale projects like the Linux kernel (speed and data volume)

Since its birth in 2005, Git has matured and improved, while maintaining a high degree of ease of use, it still retains the goals set at the beginning. It is fast and extremely suitable for managing large projects. It also has an incredible non-linear branch management system that can handle various complex project development needs.
3. Centralized VS Distributed

CVS and SVN, which Linus has always hated, are centralized version control systems, while Git is a distributed version control system. What is the difference between centralized and distributed version control systems?
Let me talk about the centralized version control system first. The version library is stored centrally on the central server, and when working, you use your own computer, so you must first obtain the latest version from the central server, then start working, and finish working. Live, and then push your own live to the central server. The central server is like a library. If you want to change a book, you must first borrow it from the library, then go home and change it yourself, and then put it back in the library.

 

Guess you like

Origin blog.csdn.net/xutongbao/article/details/130039971