Bad file number problem occurs during GitHub connection

Some time ago I tried GitHub and gitorious, a very cool code hosting site. Feeling a lot.

First of all, I have always wanted to have such a code-hosted website, but I didn't know it until a while ago. O (zookeeper) O alas, cannot keep up with the trend!

The second is that these websites are much more beautiful than what I want. I like concise and clear, and these two websites are exactly the same, even better than what I want. We recommend that you use it here.

By following the instructions, GitHub is closed-source and gitorious is open-source. No matter what, it's good. I use free .... I won't talk about how to install it on the LAN. I'll go to the website and check it out. Give their links:

GitHub: https://github.com/

Gitorious: https://gitorious.org/

Of course, both websites use the GIT version control tool. Although I used CSS only before, I felt that I was too weak after I used git... Okay. Don't talk about this .. Avoid offending SVN and CVS parties ..

However, I encountered some minor issues when using GitHub. It is not stated on the official website, but it is actually very simple, but I think there will certainly be a cainiao like me at a loss. So let me list my problems.

Follow the set up git operation on the GitHub official website. When the SSH connection is executed, the following problems will occur:

"Bad file number, what is this?" I thought so.

Later, I carefully studied the help documentation on the official website and found that it mentioned a Config configuration file. Of course, I have not created this file. So I googled it and wrote a config file to the same directory of RSA:

But I still cannot reconnect:

So I am angry !!! Let's calm down and think it may be the port 22 problem, because I pinged github.com and found that it could be pinged. Then I checked the port with icesword and found that port 22 was disabled. Port 22 is the default SSH connection port, but it seems that this service has many weaknesses, so the system is not open by default .. Of course, opening it is a policy, but since there is a weakness, I still don't want to touch it, so I just need to use another port to connect to ssh ~~~ Haha! This new port cannot be the same as the service port used by the current program. Make sure it is open. When I see the GitHub URL, I think of port 443, which is used to support HTTPS services. This port is open by default. Haha !!

You can modify the configuration file as follows:

Note that the hostname is changed to ssh.github.com. Next, we will find everything is okay ~~ Haha!

After you enter yes, a known_hosts file will be generated in the RSA path.

 

After reading it, I found that it is actually a file similar to a cookie:

When this file exists, you do not need to enter yes, and connect it directly:

How about it! Is it true that I am talented .... Okay. I have 2 more...

This article from the "cainiao surfaced" blog, please be sure to keep this source http://rangercyh.blog.51cto.com/1444712/749490