News for hackers. Stuff that matters.

dujiulun2006

https://www.cloudflare.com/china/

[quote]For the moment the China network does not support HTTPS traffic (HTTP only). Support for SSL/TLS will be made available in the coming months.[/quote]

As long as you don't sign in to China servers, they won't put you there. Even if you want to, first you need valid ICP certificate issued by Chinese govt.

For Chinese people working in IT industry, Qihoo is an awful company for the reasons mentioned above, but also for allegedly assisting government Internet censorship.

Now let's make their awful name worldwide. ;)

Re:Nginx 1.9.11 with Dynamic Modules on Tuesday February 09, 2016 @10:46AM (#11066008)
Good for them.

It's worth to note that an nginx fork called Tengine (by Taobao) has a similar feature before.

http://tengine.taobao.org/index.html

Re:GitLab 8.3 released with Auto-merge and GitLab Pages on Tuesday December 22, 2015 @10:59PM (#10781870)
GitLab Pages (EE only)

That's it. I'm pirating GitLab EE.

Baidu also claims innovation is their source of power (or some crap like this).

Even though it's most famous for showing fake hospitals' ads for 1000 Yuan per click.

I wouldn't use pre-compiled binaries when it comes to certificates...

I would read the source code and compile ($ go build) it.

Re:Kazakhstan to MitM all HTTPS traffic starting Jan 1 on Thursday December 03, 2015 @02:16AM (#10668265)
@andreyf: More like a social experiment. See whether people would notice (we did) and what's their reaction.
Re:Kazakhstan to MitM all HTTPS traffic starting Jan 1 on Thursday December 03, 2015 @01:50AM (#10668167)
Sadly, they (Baidu) are not, which is why the script content was easily modified.

To clear it up, I said that GFW "can" do (but has not yet done) these. But it tried to MITM some https traffic earlier with a non-trusted certificate as an experiment.

Re:Kazakhstan to MitM all HTTPS traffic starting Jan 1 on Wednesday December 02, 2015 @12:16PM (#10664245)
Chinese govt is also capable of doing this. Best part? We even have our trusted* root certificate!

Could this get any "better"? Sure! We can even MITM all the OUTGOING https traffic if we want! #GitHubDDoS

* Recently un-trusted by Apple and Mozilla. https://support.apple.com/en-us/HT204938

Re:Access Denied to Apple.com on Saturday September 12, 2015 @12:42AM (#10207246)
Now that's what we call innovation.
I'm not sure but I suspect that they got the technology (hardware and software) from China too.

As a Chinese netizen I don't know if I should be proud that we have world-class advanced technology or be ashamed. Possibly ashamed.

Re:GitHub's down? on Wednesday May 06, 2015 @07:56AM (#9497951)
OK it's back.
Re:U.S. Coding Website GitHub Hit with Cyberattack on Sunday March 29, 2015 @12:43PM (#9285479)
Doesn't matter to us Chinese people because WSJ is evil and we are protected by the mighty GFW from it too. [sarcasm sign]
Re:GitHub under ongoing DDoS attack on Sunday March 29, 2015 @08:33AM (#9284614)
In that case maybe the other solution is better. Wow HTML5 is crazy...
Re:GitHub under ongoing DDoS attack on Sunday March 29, 2015 @08:21AM (#9284598)
Since GitHub (and other sites) can modify their webpages, something like:

<script> if (window != top) top.location = 'http://www.google.com'; </script>

returned as a static webpage would do the trick.

Re:GitHub under ongoing DDoS attack on Sunday March 29, 2015 @07:11AM (#9284476)
I saw this on Weibo earlier, NOT from a trusted source. But the first and third rounds have been confirmed.

> 第一轮外域JavaScript,一个alert防住;第二轮外域img,Referer挡外面;第三轮GitHub Pages被D;第四波正在进行,是TCP SYN Flood攻击。

My translation:

> The first round was cross-domain JavaScript, stopped with an "alert()". Second round was cross-domain <img>, stopped with referrer. Third was DDoS-ing GitHub Pages. Fourth is the ongoing TCP SYN Flood attack.

Re:Why Baidu Has Been Hijacked to Attack GitHub on Friday March 27, 2015 @12:05PM (#9277076)
LOL. I even used them wrong. I put in single line-breaks and three asterisks. Guess it's a markdown editor? ;)
Re:Why Baidu Has Been Hijacked to Attack GitHub on Friday March 27, 2015 @12:02PM (#9277060)
Wow. That was just a jokey comment about how angry I was about the Chinese govt.

As one of the billion people who live inside the Intranet "protected" by the GFW, I guess I can say I'm quite aware about how and why this happened. Let's start from the beginning.

For those who host things Chinese govt doesn't like, it usually just block the website altogether (Twitter, FB, and recently Google). But it had tried to block Github, twice. Each time there is a huge response from the Chinese webizens (mainly programmers) calling to unblock it.

Another way to block certain content from a website is to filter by keyword (like Wikipedia). But GH is encrypted so that's a no. The govt even tried to use some fake SSL certificates to MITM it. So some "smart" guys exploited this feature and created the repo greatfire/wiki and things like this.

Then some evil guys from GFW thought of this way, directing the attack at these user accounts, to warn GH to remove these accounts.

What I don't agree with you is the word "reasonable" (and the "no"). First, it's never "reasonable" to DDoS attack a website. Second, if you can't block the content, you have a choice to block the website and take the bitter from every single webizen against you. Finally, I believe it's the website owner's choice to choose who / what they want to use their website. Since GH is a U.S. company (I guess), it doesn't have to listen to a sh*t from the Chinese govt.

Re:Why Baidu Has Been Hijacked to Attack GitHub on Friday March 27, 2015 @09:40AM (#9276149)
Chinese govt is telling the world with this attack that: (1) GFW can interfere with incoming traffic. (2) GFW can f* with people all around the world. (3) You can't block a Chinese cyber attack simply by cutting off Chinese users. (4) The Chinese govt is a d*head.
Re:Lenovo to acquire Motorola Mobility on Wednesday January 29, 2014 @09:42PM (#7148762)
春节快乐! Today is the day before spring festival in China. Good timing, Lenovo.