On Tue, 10 Feb 2015 19:41:24 +0000, A Canuck wrote:
Canadian Internet users can no longer download software published at
sourceforge.net; all access to that site from Canadian broadband ISPs or
via the TOR privacy tool is being redirected to a fake "facade" clone of
the site (most of which consists of blank pages titled "Testing") as of
this morning:
http://upload.camzu.com/up/5dbfa46a4fe4e4be2930a3e3ae488677.jpg
All access via commonly known open web proxies produces 403 errors.
Hosted sub-sites (
thingy.sourceforge.net) respond to Canadian ISP IPs
with RST packets (denied at firewall), to TOR exits with 503 errors, and
to web proxies with 403 errors.
Sourceforge is now banned in Canada, folks! Which means that as of this
morning, February 10, 2015, there is a Great Firewall of Canada.
If you are not interested in the technical details, skip to near the end
for voting advice for the forthcoming federal election. Assuming Harper
doesn't become bold enough to start ignoring that part of the
Constitution too. But he isn't willing as yet to make the blocked
Sourceforge content serve up a big banner saying "NOW OUTLAWED IN
CANADA", either...
Do not be fooled by party names that no longer reflect party ideologies.
Remember when at the polling stations what happened here today. Remember
that a vote for your riding's Conservative candidate is a vote for
Harper, and that a vote for Harper is a vote for Chinese-style state
Communism and web censorship, not a vote for any form of actual
conservatism! Another five years of Harper will probably see the adoption
of five year plans and reeducation camps here in Canada. That MUST NOT
happen.
> So I put this question out to everyone who might read this: does anyone,
> anyone at all, know anything about that weird graphic, the favicon on
> the "testing" blank page at the phony copy of the Sourceforge site that
> they seem to have used for every page they decided not to include in
> their mock up?
P.S. Google Reverse Image Search returns zero matches for this thing. I
screenshotted the fake "Testing" page, cropped out the 16x16 favicon,
saved it as a lossless PNG, and threw it at Google, with no results.
Its apparent nonexistence anywhere that Google can see on the World Wide
Web tells us several things, many of them encouraging:
1. Google still "sees" the real Sourceforge, not the fake facade I run
into now when trying to access Sourceforge from Canada (or via TOR),
or it would find this mysterious image there.
So, we can put to bed any fears that the Sourceforge site itself was
seized. (Of course, that the attackers lack Sourceforge's HTTPS
signing key already pointed strongly in that direction, though a remote
webserver compromise might not give the attackers access to such
things.)
2. The image is not just some default one that comes with some big,
common site authoring tool, nor is it the icon of some big, common
hosting provider, or Google would surely find other occurrences.
So, the icon on the "Testing" page probably really is something
unique to the attackers, rather than being part of some Dreamweaver
template or something that they lazily didn't replace with the copied
SF logo on the "Testing" page.
3. The image is not a part of existing widely publicized Snowden
revelations, or the public logo of any of the known NSA contractors,
or again Google would surely have found other instances out there.
So, this icon represents *new* information about, if not the NSA, then
some comparably-powerful adversary. Remember, while Google apparently
still sees the real Sourceforge,
a) every Bell Canada internet customer and
b) every TOR user
gets transparently served with the "facade" version of the site
instead, the one with this mysterious "Testing" page and graphic. I can
think of few adversaries with the power to do such a thing except the
NSA. In particular, to intercept not only all traffic to Sourceforge
crossing Canadian border routers but also all traffic from TOR exit
nodes *all over the world* requires having your tap close to
Sourceforge's own infrastructure. Perhaps even on site. Other than
Sourceforge themselves (who have no motive, and who have an SSL
signing key the attacker demonstrably lacks) that almost has to be the
NSA, or at least some organ of the United States government, given
where Sourceforge is physically hosted. And the NSA is the organ of US
government that has recently been caught with its hands in very
similar cookie jars, like when they intercepted physical shipments of
Cisco routers. One wonders if Sourceforge's owners know all the stops
*their* Cisco routers made on the way to Sourceforge data centers.
One more bit of encouraging news in all of this: the certificate errors
point to the adversary (almost certainly the NSA) continuing to lack the
capability to break SSL encryption (at least, not in real time). The
data, taken together, indicate that the system diagram is like this:
[Real Sourceforge] [Facade]
| |
[compromised border router]---------' <- Canadian ISPs and TOR exits
| redirected to Facade
|
[rest of net]
On the server labeled "Facade", SSL pages are served with a Cloudfront
signing key, not a Sourceforge one, and consequently when users' browsers
*think* they're talking to
sourceforge.net (but are actually being
redirected to the Facade by the compromised border router) their browsers
reject the certificates as from the wrong domain. This tells us two
things:
1. Those responsible for the attack have not seized control of the real
Sourceforge data center (or their substitute pages would come from
real Sourceforge servers, and be signed with real Sourceforge
certificates), and they don't have Sourceforge's signing key or the
ability to break SSL encryption in real time. SSL security checks
succeed in detecting their man-in-the-middle attack on Sourceforge,
except when non-https pages are requested from that site.
2. Most likely, those responsible for the attack are hosting the Facade
at Cloudfront.
The phony "Testing" blank page that most of the links on the Facade
pothole to also points to certain lacks of resources on their part. In
particular, they scraped only parts of Sourceforge's site to construct
the Facade, perhaps by duplicating chunks of the site that passed through
the compromised border router in response to ordinary users' queries,
thus missing pages (like "about") that hardly anyone ever visits. If they
didn't get hits between the initial compromise and the erection of the
Facade, the pages didn't get duplicated in the Facade and the Facade
serves up the blank "Testing" page instead (probably by way of its 404
handler -- indeed, the same blank page, rather than a 404 page, is
returned for
http://sourceforge.net/gobbledygook/
this_page_shouldnt_exist_fuseuygudfhbjmdkf.html, after the same kind of
weird _escaped_fragment redirection first).
The big question still unanswered is: What the fuck are they doing?
They ARE:
* Concealing who is responsible, as best they can. There's no big banner
coming up saying BLOCKED IN CANADA - Harper has outlawed access to
Sourceforge.net from your country. Instead, it looks at first like
you've successfully reached the site, only you can't actually do
anything useful there. So it looks almost like it's just
malfunctioning ... if you ignore the fact that it's malfunctioning only
for certain people, or that there are clear indications of a MITM
attack if you go to any https page there.
* Preventing any downloads of software from Sourceforge across the
Canadian border, including Shareaza. Whether this is narrowly targeted
at p2p software is unknown.
* Mocking up parts, but by no means all, of Sourceforge's site.
* Systematically redirecting TOR and Canadian ISP users to the Facade,
which could only reliably be done at border routers connecting
Sourceforge's data center to the wider Internet, or at Sourceforge's
ISP. This points to that ISP, Sourceforge themselves, or (much more
likely) the NSA/other US government actors, and indicates that the
miscreants in question probably physically installed hardware on
Sourceforge/its ISP's premises, or intercepted and altered hardware
bound for such a site. Most major US ISPs have been strong-armed into
allowing the NSA to install equipment on-premises, and the NSA has
intercepted and presumably altered Cisco routers en route to Cisco
customers, as revealed by Snowden documents.
They ARE NOT:
* Taking responsibility of any kind for their actions, or acknowledging
anything. The only content original to the attackers at the Facade seem
to be the "Testing" page's favicon and the word "Testing" itself.
* Substituting malware or spyware-included versions of Shareaza.
Attempting to download Shareaza results only in the blank "Testing"
page at this time. But that may change, or this whole affair may be a
"dry run" for future compromises based on substituting altered versions
of software hosted at Sourceforge. (Consider how many security
products, privacy tools, and other things are developed there, though
TOR thankfully seems to use a combination of Github and its own
torproject.org site; then shudder.)
* Disrupting any sites other than
sourceforge.net and
shareaza.sourceforge.net, to my knowledge.
* Disrupting the use of
web.archive.org to browse snapshots of
Sourceforge. However,
web.archive.org does not archive exe files, so it
is impossible to download Shareaza from their mirror of Sourceforge,
though they have the 2.7.8.0 Files page, archived on Dec. 16, 2014.
Currently
web.archive.org is the only way for a Canadian to view other
aspects of Shareaza, though; for example, tickets:
http://web.archive.org/web/20141216133329/http://sourceforge.net/p/
shareaza/tickets/?source=navbar
This is also from Dec. 16; the "live" version is substituted with the
Facade's "Testing" page for Canadian Internet users and TOR users right
now.
* Censoring Usenet. These posts are visible on an Italian newsserver, and
can be read from inside Canada, as of this writing. Of course, the goal
here doesn't seem to be censorshop per se, but rather surveillance.
Censorship specifically of decentralized and/or encrypting tools is all
we've seen evidence of so far during this incident.
They MAY BE:
* Hijacking other sites than *.
sourceforge.net ones. I don't know.
There's no sign of them messing with
torproject.net though. At least,
not yet.
* Intercepting and searching storage media at the Canadian border. Such
searches have to my knowledge been sporadic and random in the past,
rather than routine. If they remain sporadic and random, then copies of
Sourceforge-hosted software could be downloaded in the United States
and brought into Canada via sneakernet.
If there has been a sudden shift in policy at Canadian Customs to
searching *all* electronic storage media entering the country, in the
past day or so, it will be strong evidence that these web redirections,
though perpetrated by US government agencies, are being done at the
behest of the Harper Conservatives. The question being: what is it he
doesn't want Canadian citizens to have anymore? The answer almost
certainly being: privacy and anonymity tools, and tools that work peer
to peer instead of through centralized (and thus easily surveilled) web
sites. Which would mean Github and
torproject.org are in the
crosshairs, even though they don't seem to have been attacked quite yet.
* Planning to attack other sites (Github, torproject) or media (Usenet)
in the future.
The intent of our enemy is clear: to block Canadians' access to any
method by which one might evade surveillance. HTTPS is permitted, because
centralized web sites can be leant on by the Five Eyes and monitored
centrally. P2P, on the other hand, lacks centralization, so the idea of
Canadians continuing to have access to software like Shareaza has Harper
crapping his pants.
The solution is equally clear: Throw the bums out.
1. If you are not a Canadian citizen, try to organize up some big Web
protest like the anti-SOPA and pro-net-neutrality ones that recently
succeeded big-time.
2. If you are a Canadian citizen, vote!
3. If the NDP is likely to outperform the Liberals in your riding this
year, vote NDP.
4. If an independent or Green is likely to outperform the Liberals, but
the NDP isn't, vote for them.
5. If nobody non-Conservative is likely to outperform the Liberals, vote
Liberal.
6. Do not, under any circumstances, vote Conservative. I don't care what
your local Conservative candidate is like. A vote for them is a vote
for Harper, and it's abundantly clear now that a vote for Harper is an
act of treason against Canadians, the Constitution, and the Charter of
Rights and Freedoms.
7. Encourage other Canadians to vote, and tell them about all of this,
and every other shitty thing Harper has done and plans to do.