Revamping Freenet
N3wsByt3 writes "Many will have heard about the anonymous P2P-system Freenet. What many probably don't know is, that a big change is at hand: the Freenet developers have decided to drop all support for the 0.5x version, to skip version 0.6 and to completely revamp the 0.7 build into some kind of poorly described, presumably scalable darknet. The main coder even threatened to quit if such a darknet would be rejected.
So, is it finally going the right way with the development of Freenet? Maybe not, since they seem reluctant to provide real data and rather rely on security through obfuscation, and then there is still the problem of their general inability in regard to pooling human resources, which, for any OSS project, is of the utmost importance." Obviously, the article submitter has his own feelings on Freenet, but notwithstanding that, what's the latest scuttlebutt from within the Freenet crowd?
A very interesting article about flaw in Freenet
http://www.aviransplace.com
Matthew has indeed indicated that he believes it is essential that we support "trusted links" in Freenet, and the other core Freenet developers, myself included, agree with him - so Newsbyte's attempt to stir that up into some kind of controversy is just another example of his trolling.
I have no idea where Newsbyte's accusation that we are relying on security through obscurity comes from, certainly the archived email he links do doesn't seem to support any such claim.
As for the blog entry he links to, it essentially boils down to whining about why we don't implement each and every one of his suggestions.
When considering the value of Newsbyte's opinions, I would urge you to look first at what he has actually contributed to the project, versus those that he seeks to criticise.
We ran these observations by Freenet founder Ian Clarke. He agreed that the caching behavior does reveal far too many clues. But the next major revision is expected to eliminate the problem. Sometime later this year, it is hoped, the Freeenet developers will release a version that employs premix routing.
The World Wide Web is dying. Soon, we shall have only the Internet.
I don't want my node to be used to harbor child porn, offensive content or terrorism. What can I do?
The true test of someone who claims to believe in Freedom of Speech is whether they tolerate speech which they disagree with, or even find disgusting. If this is not acceptable to you, you should not run a Freenet node.
Free MacMini
Having said that, right now you basically install the software, and open your web browser - and you are surfing Freenet. Its only in "outlying" cases that things are significantly more complcated than this (ie. with firewall issues), and we are working on that.
Actually, while that's true in theory; the register printed an article that described how the information which you download is still viewable locally.
You can't tell what's stored on your node very easily.
However, it is relatively easy to see what is on freenet at large. There are several spiders that roam freenet and index freesites they come across. It's sort of like what Google does. So all one has to do is load up these indexes and see how many of the sites are child porn related. Another way to tell is load up Frost and see how many of the boards of child porn related.
There's a very large number of them.
Link to gnunet: http://gnunet.org
By the article, you can't actually see what's been downloaded, but if your local fascist government wants to determine if you downloaded file XX, they could try downloading that file from your node. If the performance is very good, then there's a good probability that the encrypted chunks are cached locally and in neighbour nodes, thus they can determine that you did download it.
2 related projects, but they're also very different to freenet.
Tor is simply an anonymous p2p proxy:
http://tor.eff.org/
i2p is a fork from freenet. Similar to Tor but you can host your own site off it.
Both are not nearly as freenet. I'm loving i2p though because it's much more practical.
For a lowdown from the i2p people on these and more similar technologies see here:
http://www.i2p.net/how_networkcomparisons
A blog I run for the wealth
If by "run" you mean "software executes as designed" then you are correct. Although I would interpret "run" to mean, does what the user expects it to do. Freenet will not load anything in a reasonable amount of time unless you open ports on the router.
Not necessarily a result of freedom and anonymity. I haven't looked for child porn, but I know there's plenty of music and programs up on gnunet.
I am trolling
I haven't used Freenet in a long time, and only really used it briefly when I did because I needed to fulfill my geeklike curiosity in the system, but I didn't see many music files on it at all; I would assume that this is because the slow transfer speeds make it completely unfeasible for a few megs of data that could be found easily enough on 'open' P2P networks. There were some movie repositories, but again the time and effort are probably only worthwhile if there's a real reason that the movie isn't available on normal P2P (I wouldn't be entirely surprised if 'high sensetivity' leaks hit Freenet first). I think there was a site full of MS software and cracks too. Nothing like the scale of a big torrent site or the eDonkey network though.
The small scale of copyright violation combined with the massive amount of work it would take to track down any Freenet user (it's more or less impossible for anyone to do without informants and the right to confiscate equipment on your side) mean that the providers probably won't bother tracking down users, and would be unlikely to bother even if copyright infringement on Freenet reached Suprnova proportions - at that point I guess that they would try the 'child porn' card to get Freenet itself outlawed since doing so would take much less time, money and effort than tracking people in a network specifically designed to avoid tracking.
I don't see freenet having those issues though. Node administrators for sure, but not freenet users. Freenet users don't really have keys or even any necessary knowledge of the technical layer of encryption. They need to know how to connect to a node.
You have a misunderstanding. Every freenet user is a node administrator. The freenet node is what actually does all the work. Every user runs a node, and every node has a data store. The node has a web interface on port localhost:8888, to which a browser can connect, so that the user can see the files in freenet in a comfortable and familiar environment.
Beyond that, if the user plans to publish content within freenet, then he must understand the basic freenet concepts of keys, keypairs, hops to live, and so on.
The thing about Freenet is that you can't report or block offending IPs; that's the exact thing it's designed to prevent.
When you retrieve a file from Freenet (at least the current "stable" implementation), your request is bounced through several other random nodes on the network; and relaying a request for another node looks exactly the same, protocol-wise, as initiating one. They call it "plausible deniability;" if a person's node contains stuff considered "bad," or illegal, then there's absolutely no way of knowing (as long as the person frequently clears their browser history and cache) whether the user of that node initiated the requests for any of that content or if they were just unknowingly relaying it for someone else.
A while ago, I saw a Freesite linked on the Freedom Engine (one of Freenet's most popular portals, probably because its operator links to kiddy porn and murder pictures, considering them to be "free speech") which claimed to filter content matching a certain list of hashes out of your node, so that your node would neither store that content nor relay requests for it. It came preloaded with a filter-list (somehow obfuscated so the real file keys couldn't be extracted by people who like that kind of stuff) of miscellaneous generally-objectional content. I'm not sure what the reaction to that was, if there was much.
But there's no way of finding out who's actually storing and retrieving that content. The current Freenet implementation leaves absolutely nothing to "security through obscurity." The only way to censor it would be through legal means, perhaps by declaring that allowing one's Freenet node to be used for illegal things is a contributory crime. But due to the nature of Freenet it would still be very hard to enforce.
Signature.
To get back on topic, it is possible to decrypt a given file in your cache if you already know its key. If the police/FBI/whoever want to know if the key CHK@iPw3Grf-hV7d8IQF2-WXFByWfzMQAwI,FGJqABIFcBZ91I qayz6aew is in your cache, it's trivial to check for that key, but if they grab a random file from your cache and want to decrypt it, the only way to do that is by trying every possible key.
Disclaimer: The opinions expressed are not necessarily my own, as I've not yet had my medication today.
This was the first I found, I believe there are a few others.
"you can always fork. If you do not agree with the current developers' direction, fork. "
People tried to fork Freenet a couple of years ago (October 2003) when it started going down the shitter (in April 2003). The forkers tried to be as nice as can be about such an issue, but the current Freenet developers told them in effect to 'Get the fuck out of here' and they did not bother.
What one of the would be forkers (jrandom) did do though which is a nice kind of tasty ironic desert is make I2P instead. Kinda nice, time that would have been spent on Freenet now made an application that in many respects meets or exceeds the abilities of Freenet.
I really do not want to make this sound like a bitter tale, it really isn't. I believe both projects (are?) seem to be getting a long since everyone has the goal of working anonymous p2p. This newest idea of Freenet is looking towards the future when our government (Western governments) try to outlaw anonymous p2p like current dictatorships are or have done.
. . .by using Freenet you are being FORCED to distribute it.
Doctor, it hurts when I go like this.
As the faq itself notes no one is forcing you to do anything. If you are not comfortable with the idea of absolute free speech, do not run Freenet since that's what it's all about. It's that simple.
And that is the issue with truely free speech you understand? It's inherently an all or none sort of deal.
And I see any particular impediment to your writing your own "Kinda, sorta Free around the edges accept for the stuff we don't like Net."
If you think that will protect you from the powers-that-be though you aren't paying attention. One power's kiddy porn is another power's freedom tract.
KFG
"If we do not believe in freedom of speech for those we despise we do not believe in it at all"
-Noam Chomsky