•

China is attempting to mirror the entire GitHub over to their own servers, users report

Still (@still@infosec.exchange)

https://infosec.exchange/@still/112681853434505681

Attached: 3 images tldr: GitCode or China is attempting to mirror/clone the entire GitHub over to their own servers and there's nothing you can do about it, even if your license somehow disagrees with it. Apparently China now has their own GitHub/public Git repository hosting service called GitCode; it is owned and operated by CSDN under the company name "重庆开源共创科技有限公司". It is being reported that many users' repository are being cloned and re-hosted on GitCode without authorization - meaning your project may very well be on this service without you explicitly allowing.

GitCode, a git-hosting website operated Chongqing Open-Source Co-Creation Technology Co Ltd and with technical support from CSDN and Huawei Cloud.

It is being reported that many users' repository are being cloned and re-hosted on GitCode without explicit authorization.

There is also a thread on Ycombinator (archived link)

283 comments

See all comments

the_ocs

•

If it's hosted in a public repo, anyone can clone it, that's very much part of most git flows.

What you can do with the software, how you can use it, that's another matter, based on the licence.

That of course assumes China will respect the copyright..

kuberoot

•

Sure, you can probably clone it - I'm not 100% sure, but I think laws protect that as long as it's private use.

You can also fork it on GitHub, that's something you agree to in the GitHub ToS - though I think you're not allowed to push any modifications if the license doesn't allow it?

Straight up taking the content from GitHub, uploading it to your own servers, and letting people grab a copy from there? That's redistribution, and is something that needs to be permitted by the license. It doesn't matter if it's git or something else, in the end that's just a way to host potentially copyrighted material.

Though if you have some reference on why this is not the case, I'd love to see it - but I'm not gonna take a claim that "that's very much a part of most git flows".