Knighthana
Knighthana
文章95
标签138
分类7
回到首页
文章归档
关于本站

文章分类

文章归档

最新文章

© 2024 Knighthana Powered by Hexo & Nexmoe
git克隆方法错误导致的推送出错

git克隆方法错误导致的推送出错

2019年05月20日 Dev-Env

错误地使用了git的克隆方法导致的推送出错

在简单地用代码git clone git://********.git将远端库的代码克隆到本地之后，我遇到了无法push的问题；

在查阅了网上的文章之后，我发现这是克隆方式错误导致的，

如果想要克隆一个自己的项目，就应该使用git clone git@git://*******.git这样的代码，这样才能保证正常使用终端推送代码；

以及ssh的默认安全设置要求id_rsa文件必须是仅用户本人可读写，即600权限，如果后两位不为0，那么就不能正常使用ssh的功能

最后，测试公钥私钥是否配置正常需要的代码是ssh git@github.com而不是ssh username@github.com

knighthana

2019年5月20日 于西电

Git Cannot Push Caused By Wrong Cloning Method

Today I cloned my repo. from github.com, and simply used git clone git://username/reponame.git ( BTW: "git://" means "http://" ) .

When I ended my job and tried to push my works to github it said that I can't push.

Warning text :

fatal:remote error:

You can't push to git://github.com/username/reponame.git

Use https://github.com/username/reponame.git

I don't know what happened at first. My direct sense told me that it maybe related to the remote repo settings.

I search it on the Internet, find that article 解决fatal:remote error:You can't push to git://github.com/username/*.git问题的办法. It's apparently that I used a wrong method to clone for I have future push plan. So, if I want to clone my own repo from online git repo, I'd better use git clone git@github.com:username/userrepository.git but not git clone git://

How to fix that?

1
2
git remote rm origin
git remote add origin git@github.com:username/reponame.git

So it has been solved. My work can be continued in new environment.

By the way, there was still some waves before I finally succeed in pushing my local repo to remote repo.

When I tried to use ssh -t git@github.com, there was a warning information said :

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

@ WARNING: UNPROTECTED PRIVATE KEY FILE! @

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

Permissions 0644 for '/home/username/.ssh/id\_rsa' are too open.

I delightly found that there is such a restriction about id_rsa file which I never noticed.

I copied my id_rsa and id_rsa.pub from another computer with a U size Flash Disk whose fileformat is FAT32 ( maybe NTFS but not *nix FS for sure ), and the file was copied through my Windows 10 OS's desktop.

The rsa file was copied in my WSL environment at last, but the operation permission set was 777.

I thought that the files' operation permission should defaultly be 644 ( refer to another Gulog "WSL operation permission" ).

Until now, the system gave me a lesson that if an id_rsa file was set any read or write permission for other users, it won't be trusted.

I changed it's operation permission to 600, and the problem was solved.

And ... don't try to ssh username@github.com. I must be drunk, or I wouldn't have typed that command.

Knighthana @ XDU

2019/05/20

×