Infranet: Circumventing Web Censorship 103
edsonw writes "In this paper presented at the 11th USENIX Security
Symposium, Feamster et alii presented a method that provide access to censored sites while continuing to host normal uncensored content, using covert communication and steganographic techniques." The Infranet webpage has some more information. No public code yet, though.
Mmmm... (Score:3, Funny)
Re:Mmmm... (Score:1)
ROFL - roll on floor laughing
FOFL - fell on floor laughing
FELOFIL - fell easily laughing on floor in (greek) lunch
LFNT - there's a huge grey animal in here
jhgasd - I have a cat that likes to walk on the keyboard.
Re:Mmmm... (Score:1)
It's a shame that it's coming to this (Score:2, Insightful)
Information doesn't want to be free
Information just wants to be
Freedom? (Score:2)
Uh huh. And then, in the footnotes you'll find the literature references which almost exclusively point to repressive regimes.
It's pretty rare that you see privacy advocates point to blocking measures being used to increase privacy. In the case of corporations, that includes privacy w.r.t. corporate secrets, as well as privacy w.r.t. the internal infrastructure (think viruses, worms, JavaScript "window.open" bombs, etc).
For some reason, it never occurs to some privacy advocates that even at the individual level, blocking can be beneficial.
The most interesting discussion, on how democratic controls should be applied to the filtering, is rarely held.
I'm stuck in corporate hell. If dozens of users beat down my door with requests to block porn spam, then I'm not just legally justified in blocking the shit, but also morally.
It's rare that people are actually offended by it. More often than not, it's just because they lose work because they open an e-mail, and their system just locks up under the load caused by all the window.opens.
I'm fully aware that some corporate sysadmins are moralistic dorks. But I'm quite offended by the insinuation that by blocking certain web sites I'm somehow taking away my users $DEITY given rights to view certain information crucial to their civil rights.
Oh well. All evidence points to the conclusion that
lol (Score:2)
Seriously though, could the technology used to view the content, not be used by the very entity trying to prevent it's use to detect and block sites using the technology?
Transparency (Score:3, Interesting)
More serious Considerations (Score:4, Interesting)
Re:More serious Considerations (Score:1)
Re:More serious Considerations (Score:1)
Re:More serious Considerations (Score:4, Informative)
Re:More serious Considerations (Score:1)
Actually (Score:2)
I believe that something like this is in place Freenet would be ready for a population explosion...
Re:Actually (Score:1)
Now, whether an influx of near-luddites would be good depends on the quality of the software. But... yes!
Re:Actually (Score:2)
How much more familiar can thier inteface be?
One package (Score:2)
I think that to leave the development stage and enter the userbase sphere, Freenet will need to be not only stable, fast and secure, it will need to be easy to install and use too.
Re:More serious Considerations (Score:3, Insightful)
This not only encrypt the content, but also maskarades as an innocent-looking, 100% normal, everyday happening communication.
Re:More serious Considerations (Score:4, Interesting)
But a wireless grid network that just runs on our own computers, could potentially bypass the current internet infrastructure completely.
We each will turn into a micro-ISP, providing little routing and little storage for our neighbors.
Re:More serious Considerations (Score:1)
a step further... (Score:1)
what if you trained yourself to read numbers?
no more slashdot at work, oh no just a spreadsheet
a lot of work? perhaps, but who would catch you?
solution (Score:3, Funny)
how come when chinese
build wall damn mongolians
try to knock it down
No Censoring Unless It Suits Us! (Score:2, Troll)
Or is it that we completely support censoring? Or completely against it?
Can there be a middle ground??
Re:No Censoring Unless It Suits Us! (Score:2)
Re:No Censoring Unless It Suits Us! (Score:1)
Re:No Censoring Unless It Suits Us! (Score:1)
And, actually, slashdot is censored with its new policies (like auto-score:-1 people can only post twice per day, etc...), but slashdot isn't a democracy, so the point is moot.
Re:No Censoring Unless It Suits Us! (Score:1)
Obvious Question (Score:2, Insightful)
Does this sort of use of circumvention measures constitute breaking the DMCA?
Re:But the question we're all asking is... (Score:1)
then IORAL = I Only Resemble A Lawyer
DMCA Applies to Copy Protection systems (Score:2)
Which are used to protect copyrighted content.
Generally, they have to be able to argue that you broke a copy protection system, even lame copy-protection systems (Adobe's ROT13 for EBooks), or copy-protection systems that do little to prevent copying (DVD-CSS), but rather limit playback and conversion to other formats.
I can understand why one would think the DMCA's anti-circumvention section applies too all forms of circumvention giving the way the law has been abused (Threatening Academics with Lawsuits), but it really only applies to copy protection systems.
cost.. motivation..? (Score:2, Insightful)
Good idea, but IMHO it will be expensive to implement, and then the question is who would really want it. Of course dont expect your office people to install it. Maybe certain organizations want it... and then also what garuntee is that it wont be made illegal under some god awful bill.
Till now it has been true that technology has always been a step ahead of censorship, but with the current state of laws, this wont be true for long.
I am positive that by the time a proper implemention comes out somebody will table the bill to ban it, then we will all cry hoarse in slashdot. The story will make to
Paranoia? Not exactly.. censorship is here to stay... and it is getting bigger.
But surely they'll just block Infranet? (Score:2, Insightful)
If I understand this correctly a public server (probably a public web site) needs to host the Infranet server bit to fetch the actual site the user wants.
What's stopping the 'censor' blocking access to servers that are known to run Infranet? If the user / client software can find out which servers support it, the censor can.
Maybe I'm missing something, but it seems pretty flawed to me.
Re:But surely they'll just block Infranet? (Score:2)
Re:But surely they'll just block Infranet? (Score:1)
Well, I guess the plan to enable it by default on Apache installations is one thing stopping that...
Proxy Avoidance (Score:5, Interesting)
The problem here is that the "Infranet" software must talk to the responder directly in order for its steganographic stream to be understood. In the parlance of at least one censorware product, this type of thing would be classified as a "Proxy Avoidance System" and be blocked accordingly. This might be effective against keyword blocking due to the nature of the information being transmitted, but if used as a straight proxy bypass, most censorware products would only need to know where the responders are.
This method would be more difficult to detect than a straight proxy-through, but it still doesn't account for the fact that the "responders" must be known in some way to the transmitter. If a series of public responders is set up, it would only be a matter of time before those sites would be sewed up tighter than a drum by most "reputable" censorware companies' research teams.
As it is, it's not terribly difficult to bypass censorware if you have the ability to put something up on the outside to bounce off of. Nearly all of the production censorware that I see does absolutely nothing with HTTPS -- and the lax security of most firewall policies doesn't restrict the destination port of a standard HTTP/1.1 CONNECT request. With that available, give me any SSH server on the outside and I can get an encrypted session running to a proxy in a matter of minutes.
Come to think of it, I've never heard the people complaining about censorware's _limitations_, only about the limits that it places on them. The truth is that every one of them is imminently bypassable already. Why bother with steganographic communications unless you live in a place where even initiating encrypted communications would put you in the pokey?
Re:Proxy Avoidance (Score:2)
% ssh -D8080
browser -> configs -> proxy -> socks4 proxy = 8080
This approach works fine if the firewalls allow ssh traffic (22/tcp). But I was referring to the instance where an extremely restrictive firewall (and the ones where censorware exists tend to be the paranoid ones) allows only 80/443 and sometimes ftp. To jump past that, it's possible to use HTTPS CONNECT to push through to an SSH server ("CONNECT sitename:22 HTTP/1.1") -- the majority of firewall configurations I've seen always forget to restrict CONNECT.
I was at the talk. This is exactly the audience they're looking to serve.
Well, I figured that. For the Average Joe living in Average-JoeLand, this approach doesn't make much sense -- which is what a lot of the commenters seem to be assuming.
There were a lot of yet-unanswered questions raised about this tech, but they did address the one you raise about responders being known, and addressed it rather well. Basically, it should be difficult to identify responders by randomly talking to servers, and those that use the system are assumed to be in dire enough straits to keep the knoweledge of where responders are secret. They do, however, require the existence of a large network of responders and a client that can move amongst them seemingly at random to avoid basic traffic analysis that would show which servers the responders are. But if the tech is actually implemented as they envision, the problem you're talking about wouldn't really be there.
The requester has to know how to get to the responder -- and it may mask its requests with traffic to "random" sites -- that much is perfectly clear from the document. But it doesn't escape the fact that the following _must_ hold true in any "proxy avoidance" scenario where a large group of potential proxy sites is available:
1) The requester must obtain a list of possible responders from somewhere that is encoded into the requester itself, or
2) The requester must have a list of "master" responders encoded into itself, or
3) The requester must have a list of all active requesters loaded into it, either by hand or included in the distribution.
If the software is then made _generally_ available, then the knowledge of the identities of the "list container" sites, the "master" responders, or the master list would be known. And that's all the censorware people need to figure out how to block the traffic.
A far simpler approach would be to encode web traffic in steganographic traffic carried over ANOTHER common protocol that usually _isn't_ watched by common censorware. FTP? Telnet? SMB? As it is, this might work for limited P2P, but a "public" phalanx of these responders would get blocked ASAP.
Wish I could have been at that talk, though. It's a fascinating concept.
The stuff from "Hacker Convention" (Score:2)
Isn't there already something from a recent "Hacker Convention" (or something sounding more omninous) that can aid the user to circumvate state censorships ?
Sorry I don't remember exactly which "convention" is it, nor the name of the "stuff" (mebbe a program, mebbe a suggestion or an on-going project).
If anyone has more info, please post it here. Thanks !
Re:The stuff from "Hacker Convention" (Score:1)
Yes. (Score:1)
There are some similar project with working code (Score:2)
2. Gnunet www.gnu.org
3. and finally cDc is coming out with an anonymous P2P network sometime this month. (at least they claim)
Re:There are some similar project with working cod (Score:1)
Yeah that's peekabooty at http://sourceforge.net/projects/peekabooty
Oh great... (Score:1)
Other systems in place (Score:1, Redundant)
Peekabooty (http://sourceforge.net/projects/peekabooty/)
JAP - Just another proxy (web page is down, but you may be able to find the app out there)
Both of these apps create a local proxy which to my understanding fits the specs of the MIT project. My feeling is the more the merrier, as long as no spyware is added.
Steganography can be defeated (Score:2, Interesting)
Or, they could hold a copy of each image file the first time it is requested. Then, whenever the image is requested again they could compare the two. If the image files are not identical, then that is a clear sign of steganography, and they could then persue furthor investigation.
Come to think of it, the U.S. could do the same thing. I wonder if they are. It would certainly be an interesting way of feriting out potentuial terrists. Assuming that terrorists actualy use steganography.
Re:Steganography can be defeated (Score:1)
Steganography most commonly uses pictures right now since they're large and easy to hide data in, but it doesn't have to.
Re:Steganography can be defeated (Score:1, Funny)
Re:Steganography can be defeated (Score:1)
ThinkCrime (Score:4, Interesting)
First to go is the beloved and maligned 'hacker', we lost on that one, it's gone no matter what effort is used to returned the word to it's productive and wholesome origin. Using hacker is going to throw red flags in too many places to make it worth the risk of losing a fight that is about a lot more than words.
Lets substitute something harmless, instead of hack and hacker, make it repair and repairer.
other words some of the used in the infranet website are;
censor/ed, change to impair/ed
circumvention, to repair (don't used 'fix')
covert, to reliable.
Maybe some of you can see where I am headed.
The title for the Talks would change from:
Infranet:Circumventing Web Censorship and Surveillance to,
Infranet:Repairing Web Impairment and Data Leakage
For those who didn't get it yet, here is the point.
Our inside terms have spilled to the outside and been manipulated to the darkest of interpretations.
The inside terms have then been used to propagandise the public into accepting them, and then it gets codified into law.
Lets get out of our terms and sic the thought police on themselves by being more descriptive, and not letting them play us with our own words.
Use popular websites as responders (Score:2)
In the case of corporate proxy filtering, news and financial sites like CNN and the Wall Street Journal would be useful. In the case of foreign country censorship, you'd have to use non-news sites because objective reporting is exactly what they're trying to block.
Mmmmm.... (Score:1)