News for hackers. Stuff that matters.
Re:Kazakhstan to MitM all HTTPS traffic starting Jan 1 by kaizendad on Wednesday December 02, 2015 @11:52AM (#10664055)
I really appreciate how they're doing this. The Chinese built up an amazing infrastructure for the Great Firewall; the Kazakhs just say "install our cert!" The Chinese spend billions and have to stay ahead of all of their citizens' clever new ideas at all times; the Kazakhs spend a few hundred and just need to point guns at their citizens until they install a cert.

Sure, it's going to be difficult to enforce, but it should also be quite cheap.

Re:Kazakhstan to MitM all HTTPS traffic starting Jan 1 by dujiulun2006 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:Kazakhstan to MitM all HTTPS traffic starting Jan 1 by andreyf on Wednesday December 02, 2015 @05:00PM (#10666165)
Was that trusted root cert ever misused? IIRC, it was un-trusted because they did not do their due diligence on how an issued sub-cert was being used by an Egyptian company.

What does the GitHub DDOS have to do with MITM attacks on https?

Re:Kazakhstan to MitM all HTTPS traffic starting Jan 1 by mil0 on Wednesday December 02, 2015 @09:07PM (#10667271)
the ddos was achieved by altering the contents of one of the script on a large chinese site (was it baidu? google it). Once every user on that site loaded the tampered script, it made sure to send many requests to github.
Re:Kazakhstan to MitM all HTTPS traffic starting Jan 1 by therein on Wednesday December 02, 2015 @10:31PM (#10667569)
Was the large Chinese site serving traffic over HTTPS?
Re:Kazakhstan to MitM all HTTPS traffic starting Jan 1 by dujiulun2006 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 by dujiulun2006 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 by andreyf on Thursday December 03, 2015 @02:06AM (#10668226)
Experiment? This isn't science. They can ask any engineer what MITM with a non-trusted cert would do, and that's nothing.
Re:Kazakhstan to MitM all HTTPS traffic starting Jan 1 by duncan_bayne on Wednesday December 02, 2015 @04:46PM (#10666071)
I really don't understand how that sort of behaviour doesn't constitute an act of war.

Imagine if China sent saboteurs in-country to physically destroy infrastructure being used by American businesses. That would Not Be Taken Lightly.

Re:Kazakhstan to MitM all HTTPS traffic starting Jan 1 by peteretep on Wednesday December 02, 2015 @08:27PM (#10667128)

    > how that sort of behaviour doesn't constitute an act of war
You need photos of explosions and dead babies to convince your populace to go to war. Making a case for war between nuclear powers on the basis that "some website for geeks became a bit less reliable" isn't going to cut it.
Re:Kazakhstan to MitM all HTTPS traffic starting Jan 1 by com_kieffer on Wednesday December 02, 2015 @06:54PM (#10666779)
The same way that Stuxnet destroying Iranian centrifuges was an act of war ?
Re:Kazakhstan to MitM all HTTPS traffic starting Jan 1 by duncan_bayne on Wednesday December 02, 2015 @07:02PM (#10666814)
Yes. Although I'd have thought that particular war would have started back with the hostage-taking in, what, 1979?

I really don't understand relationships between States.

Re:Kazakhstan to MitM all HTTPS traffic starting Jan 1 by ta0o0o0 on Wednesday December 02, 2015 @11:09PM (#10667694)
I'm not a West Hater by any means, but I'd say the war started when the US and the UK engineered a coup in Iran because Iran nationalized their oil industry (after the British oil company running it refused to be audited or to renegotiate terms).

https://en.wikipedia.org/wiki/1953_Iranian_coup_d'%C3%A9tat

Re:Kazakhstan to MitM all HTTPS traffic starting Jan 1 by duncan_bayne on Thursday December 03, 2015 @12:08AM (#10667874)
Whereas I'd say the problem was forced nationalisation.
Re:Kazakhstan to MitM all HTTPS traffic starting Jan 1 by ta0o0o0 on Thursday December 03, 2015 @11:15AM (#10670379)
That does not justify overthrowing another country's government. Most countries, including the United States, recognize the state's eminent domain over its land and its natural resources. Besides which, the Iranians tried to negotiate, the British refused, so the Iranians nationalized in response.
Re:Kazakhstan to MitM all HTTPS traffic starting Jan 1 by lhopki01 on Thursday December 03, 2015 @08:58AM (#10669545)
A foreign coup is a valid response to nationalisation?
Re:Kazakhstan to MitM all HTTPS traffic starting Jan 1 by duncan_bayne on Thursday December 03, 2015 @04:20PM (#10672725)
I'm not sure. But nationalisation is certainly a violation of rights.

Of course, I'd be interested to see how those assets were set up in the first place - my bet would be during a non-rights-respecting period of colonialism.

How far back do you go? (Serious question).

Re:Kazakhstan to MitM all HTTPS traffic starting Jan 1 by lhopki01 on Friday December 11, 2015 @11:50AM (#10718129)
You go to when the country got a democratically elected government.

As for nationalisation is certainly a violation of rights do you hold that all eminent domain is a violation of rights? IE if the government wants to build a road and uses compulsory purchase orders it's a violation of rights?

Re:Kazakhstan to MitM all HTTPS traffic starting Jan 1 by duncan_bayne on Friday December 11, 2015 @03:39PM (#10719818)
Yes. It's possible to do such things in non rights violating ways. For example, buying options on properties and exercising them when a route is made.
Re:Kazakhstan to MitM all HTTPS traffic starting Jan 1 by fleitz on Thursday December 03, 2015 @05:29AM (#10668867)
Starting point for international relations:

https://en.wikipedia.org/wiki/Realpolitik

Re:Kazakhstan to MitM all HTTPS traffic starting Jan 1 by mil0 on Wednesday December 02, 2015 @09:08PM (#10667275)
always love a good reference to Argo.
Re:Kazakhstan to MitM all HTTPS traffic starting Jan 1 by cortesoft on Wednesday December 02, 2015 @05:49PM (#10666461)
Which sort of behavior? Having their own root certificate?
Re:Kazakhstan to MitM all HTTPS traffic starting Jan 1 by duncan_bayne on Wednesday December 02, 2015 @05:53PM (#10666498)
I meant China's behaviour, e.g. orchestrating a DDOS attack against GitHub for political reasons.

The root certificate thing is 'merely' a violation of the rights of their own subjects.

Re:Kazakhstan to MitM all HTTPS traffic starting Jan 1 by cortesoft on Wednesday December 02, 2015 @05:53PM (#10666504)
Ah, ok that makes more sense.
Re:Kazakhstan to MitM all HTTPS traffic starting Jan 1 by orf on Wednesday December 02, 2015 @01:30PM (#10664808)
To be fair they really fucked up a couple of stages of that GitHub DDOS and made it trivial to stop.
Re:Kazakhstan to MitM all HTTPS traffic starting Jan 1 by jacquesm on Wednesday December 02, 2015 @05:13PM (#10666249)
And they managed to shine the spotlight on a project in need of some tlc.
Re:Kazakhstan to MitM all HTTPS traffic starting Jan 1 by egeozcan on Wednesday December 02, 2015 @11:54AM (#10664073)
> it's going to be difficult to enforce

I guess it's just a matter of dropping every connection that you can't MITM, no?

Re:Kazakhstan to MitM all HTTPS traffic starting Jan 1 by Elhana on Wednesday December 02, 2015 @02:02PM (#10665035)
You don't have to. Proxy handles the request and just gives response back to you signed with national cert. If you don't install it, your browser will just start complaining about every site. At least that is how Bluecoat ProxySG[1] works at my employee.

[1] https://bto.bluecoat.com/webguides/proxysg/security_first_st...

Re:Kazakhstan to MitM all HTTPS traffic starting Jan 1 by voltagex_ on Wednesday December 02, 2015 @05:16PM (#10666265)
Funny story, most of the machines / servers at my workplace weren't vulnerable to Heartbleed - but ProxySG was. AFAIK they built their own OS from scratch, too.
Re:Kazakhstan to MitM all HTTPS traffic starting Jan 1 by cortesoft on Wednesday December 02, 2015 @05:51PM (#10666481)
For SSL traffic, yes, but that wouldn't stop someone from using a different encryption protocol.
Re:Kazakhstan to MitM all HTTPS traffic starting Jan 1 by mil0 on Wednesday December 02, 2015 @09:13PM (#10667298)
country wide, this is a loud call for a cloud, distributed proxy provider with a better track record than the telco, to offer tor-like tunnels to at least exit the MITM zone.
Re:Kazakhstan to MitM all HTTPS traffic starting Jan 1 by barkingcat on Wednesday December 02, 2015 @11:59AM (#10664108)
easy to enforce inside the country. Just set it so that there's no https if you don't have the cert! It is becoming a legal requirement for all telcos in the country so even if you're roaming (with a data plan from a foreign provider, for example) - you're still using the local telcos.

Only way to avoid is to use some kind of foreign satellite internet or maybe private / non government / non telco dark fibre.

Re:Kazakhstan to MitM all HTTPS traffic starting Jan 1 by rogeryu on Wednesday December 02, 2015 @12:25PM (#10664309)
I guess VPN is the only way to avoid it. Or sshuttle or something over port 80. But then again, how long will it take before they can detect that and then block it?!

Or you can use non-standard ports, and change them continuously.

Re:Kazakhstan to MitM all HTTPS traffic starting Jan 1 by ta0o0o0 on Wednesday December 02, 2015 @02:05PM (#10665051)
They can just block everything by default and only enable what they can decrypt. Maybe you could try tunelling encrypted data over HTTP, but heuristics could probably pick that up too.
Re:Kazakhstan to MitM all HTTPS traffic starting Jan 1 by dheera on Wednesday December 02, 2015 @04:35PM (#10666007)
Well, in that case I'm just going to invent a TCP-over-cat-pictures VPN. Encode all the TCP packets in the subtle details of the fur and package everything up as innocent-looking HTTP GET requests.

This realistically shouldn't be too hard to do with obfsproxy's already-built framework.

Re:Kazakhstan to MitM all HTTPS traffic starting Jan 1 by jacquesm on Wednesday December 02, 2015 @05:14PM (#10666255)
You're going to run out of cat pictures pretty quickly.
Re:Kazakhstan to MitM all HTTPS traffic starting Jan 1 by femto113 on Wednesday December 02, 2015 @05:48PM (#10666457)
I've been thinking about this lately, and it seems that you could use something like a book code. Client and server use existing internet accessible images as the book and then your communication simply references bytes in those images: client requests a URL that encodes the bytes it wants to send, server returns HTML containing the urls of images containing the bytes it wants to send in response (and any extra content that helps make the page seem normal, ignored by the client). Pictures could be anything anywhere (lolcats, wikipedia, etc.), client should only ever need to download the picture once. Bandwidth wouldn't be great, but if the server is accessible via a wide (and evolving) variety of domains it seems like it would be quite hard to distinguish this from normal browsing.
Re:Kazakhstan to MitM all HTTPS traffic starting Jan 1 by jacquesm on Wednesday December 02, 2015 @09:21PM (#10667321)
Just pass a DVD with white noise when you meet in person. That should keep you in one time pads as long as you want to communicate with someone. All you need is XOR and a bookmark. Of course you need to meet once, if that's not feasible you're going to get more technical.
Re:Kazakhstan to MitM all HTTPS traffic starting Jan 1 by redler on Wednesday December 02, 2015 @10:26PM (#10667539)
In Vernor Vinge's A Fire Upon the Deep I recall a plot element along these lines. Traders traffic in cubes of material that acts as a super dense source of pad data. Your communication partner on another ship would have the twin cube, and the two would be synced up and then provide the carrier data stream for video and other content. When your cubestuff is exhausted your secure authenticated comms cease.
Re:Kazakhstan to MitM all HTTPS traffic starting Jan 1 by dheera on Thursday December 03, 2015 @09:23AM (#10669669)
If the censorship is based on the government being able to make some sense of what you're communicating, XORing with a PSK will not work, because they will see meaningless garbage and block it. The reason I suggested cat pictures is because the censors will see actual cat pictures and (hopefully) consider the protocol not worthy of blocking.

s/cat pictures/whatever you want/

Re:Kazakhstan to MitM all HTTPS traffic starting Jan 1 by mil0 on Wednesday December 02, 2015 @09:18PM (#10667316)
got a repo i can contribute to?
Re:Kazakhstan to MitM all HTTPS traffic starting Jan 1 by pstuart on Wednesday December 02, 2015 @06:07PM (#10666564)
Just drop fresh meme text on 'em and Bob's your uncle!
Re:Kazakhstan to MitM all HTTPS traffic starting Jan 1 by jacquesm on Wednesday December 02, 2015 @06:10PM (#10666580)
I think you may be on to something here.
Re:Kazakhstan to MitM all HTTPS traffic starting Jan 1 by rjbwork on Wednesday December 02, 2015 @04:56PM (#10666147)
Pretty easy really. Without knowing the key for the steganographic algorithm, it's really hard to get the data out unless you can compare it to the original. So if you're sourcing the pictures from somewhere, you'll need to manipulate false bits that aren't called for from the data itself to keep it from being breakable in such a manner.
Re:Kazakhstan to MitM all HTTPS traffic starting Jan 1 by ansible on Wednesday December 02, 2015 @03:40PM (#10665637)
If I had the free time, I'd create a cryptographic protocol running on top of telnet that looked like someone playing a MUD.

For email, you'd encrypt data to have it look like regular prose. So you'd only get a few bits per English word, but that would be sufficient for short messages. Could also make use of extra spaces in between words.

The real trick with that would be to take an existing document, and alter it to encode a message. So you'd be doing things like using synonym choice to get your bits.

Re:Kazakhstan to MitM all HTTPS traffic starting Jan 1 by metalliqaz on Wednesday December 02, 2015 @05:13PM (#10666251)
There aren't enough MUD players to make it inconspicuous.
Re:Kazakhstan to MitM all HTTPS traffic starting Jan 1 by nualartlee on Wednesday December 02, 2015 @05:37PM (#10666387)
Cat pictures and steganography.
Re:Kazakhstan to MitM all HTTPS traffic starting Jan 1 by pferde on Thursday December 03, 2015 @05:13AM (#10668824)
Wait, isn't reddit already used for this extensively? With each subreddit being a separate comms channel. Or is there another reason why very little reddit content makes sense?
Re:Kazakhstan to MitM all HTTPS traffic starting Jan 1 by nathan_f77 on Thursday December 03, 2015 @02:29AM (#10668298)
It's not even difficult to enforce. If you don't install their cert, you don't have access to the internet. Or you just have to force Chrome to ignore all SSL errors, which is the same thing.