github 公钥 私钥,为什么GitHub只需要我的公钥即可推送?

I recently set up a project on cloud9 (c9.io). When you set up a project on cloud9, there is a .ssh directory with both public keys and private keys. I assume these are generated when you set up your account.

After creating a git repository, I set the origin to an empty repository on GitHub and attempted to push it upstream. As expected I didn't have the permissions.

I copied the contents of my public key and added it to GitHub. At that point I was able to push to GitHub.

I'm curious as to why GitHub only needs the public key. What happens behind the scenes when I attempted to push? What is the role of the private key?

解决方案

A private key, as its name indicates, is private. It's yours and yours only. You should never give a private key to anyone.

Your private key allows you to sign a message. You then send the message with its signature, and anyone having your public key can verify that the signature matches with the message. That's the principle of public key cryptography. So Github only needs your public key to check that you're the one you claim to be.

  • 0
    点赞
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论

“相关推荐”对你有帮助么?

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值