Freenet

For other uses, see Freenet (disambiguation).

Freenet is a peer-to-peer platform for censorship-resistant, anonymous communication. It uses a decentralized distributed data store to keep and deliver information, and has a suite of free software for publishing and communicating on the Web without fear of censorship.^{[4][5]: 151} Both Freenet and some of its associated tools were originally designed by Ian Clarke, who defined Freenet's goal as providing freedom of speech on the Internet with strong anonymity protection.^[6][7]

FProxy index page (Freenet 0.7)
Developer(s)	^[1]
Initial release	March 2000; 23 years ago (2000-03)
Stable release	0.7.5 build 1497^[2]  / 4 March 2023
Repository	https://github.com/hyphanet/fred
Written in	Java
Operating system	Cross-platform: Unix-like (Android, Linux, BSD, macOS), Microsoft Windows
Platform	Java
Available in	English, French, Italian, German, Dutch, Spanish, Portuguese, Swedish, Norwegian, Chinese, Russian^[3]
Type	Anonymity application, peer-to-peer, friend-to-friend, overlay network, mix network, distributed data store
License	GNU General Public License version 3 only
Website	www.hyphanet.org

The distributed data store of Freenet is used by many third-party programs and plugins to provide microblogging and media sharing,^[8] anonymous and decentralised version tracking,^[9] blogging,^[10] a generic web of trust for decentralized spam resistance,^[11] Shoeshop for using Freenet over sneakernet,^[12] and many more.

History

The origin of Freenet can be traced to Ian Clarke's student project at the University of Edinburgh, which he completed as a graduation requirement in the summer of 1999.^[13][14][15] Ian Clarke's resulting unpublished report "A distributed decentralized information storage and retrieval system" (1999) provided foundation for the seminal paper written in collaboration with other researchers, "Freenet: A Distributed Anonymous Information Storage and Retrieval System" (2001).^[16][17] According to CiteSeer, it became one of the most frequently cited computer science articles in 2002.^[18]

Freenet can provide anonymity on the Internet by storing small encrypted snippets of content distributed on the computers of its users and connecting only through intermediate computers which pass on requests for content and sending them back without knowing the contents of the full file. This is similar to how routers on the Internet route packets without knowing anything about files —except Freenet has caching, a layer of strong encryption, and no reliance on centralized structures.^[17] This allows users to publish anonymously or retrieve various kinds of information.^[5]: 152

 

The Freenet 0.7 darknet peers list.

Freenet has been under continuous development since 2000.

Freenet 0.7, released on 8 May 2008, is a major re-write incorporating a number of fundamental changes. The most fundamental change is support for darknet operation. Version 0.7 offered two modes of operation: a mode in which it connects only to friends, and an opennet-mode in which it connects to any other Freenet user. Both modes can be run simultaneously. When a user switches to pure darknet operation, Freenet becomes very difficult to detect from the outside. The transport layer created for the darknet mode allows communication over restricted routes as commonly found in mesh networks, as long as these connections follow a small-world structure.^{[19]: 815–816} Other modifications include switching from TCP to UDP, which allows UDP hole punching along with faster transmission of messages between peers in the network.^[20]

Freenet 0.7.5, released on 12 June 2009, offers a variety of improvements over 0.7. These include reduced memory usage, faster insert and retrieval of content, significant improvements to the FProxy web interface used for browsing freesites, and a large number of smaller bugfixes, performance enhancements, and usability improvements. Version 0.7.5 also shipped with a new version of the Windows installer.^[21]

As of build 1226, released on 30 July 2009, features that have been written include significant security improvements against both attackers acting on the network and physical seizure of the computer running the node.^[22]

As of build 1468, released on 11 July 2015, the Freenet core stopped using the db4o database and laid the foundation for an efficient interface to the Web of Trust plugin which provides spam resistance.^[23]

Freenet has always been free software, but until 2011 it required users to install Java. This problem was solved by making Freenet compatible with OpenJDK, a free and open source implementation of the Java Platform.

On 11 February 2015, Freenet received the SUMA-Award for "protection against total surveillance".^[24][25][26]

Features and user interface

Freenet served as the model for the Japanese peer to peer file-sharing programs Winny, Share and Perfect Dark, but this model differs from p2p networks such as Bittorrent and emule. Freenet separates the underlying network structure and protocol from how users interact with the network; as a result, there are a variety of ways to access content on the Freenet network. The simplest is via FProxy, which is integrated with the node software and provides a web interface to content on the network. Using FProxy, a user can browse freesites (websites that use normal HTML and related tools, but whose content is stored within Freenet rather than on a traditional web server). The web interface is also used for most configuration and node management tasks. Through the use of separate applications or plugins loaded into the node software, users can interact with the network in other ways, such as forums similar to web forums or Usenet or interfaces more similar to traditional P2P "filesharing" interfaces.

While Freenet provides an HTTP interface for browsing freesites, it is not a proxy for the World Wide Web; Freenet can be used to access only the content that has been previously inserted into the Freenet network. In this way, it is more similar to Tor's onion services than to anonymous proxy software like Tor's proxy.

Freenet's focus lies on free speech and anonymity. Because of that, Freenet acts differently at certain points that are (directly or indirectly) related to the anonymity part. Freenet attempts to protect the anonymity of both people inserting data into the network (uploading) and those retrieving data from the network (downloading). Unlike file sharing systems, there is no need for the uploader to remain on the network after uploading a file or group of files. Instead, during the upload process, the files are broken into chunks and stored on a variety of other computers on the network. When downloading, those chunks are found and reassembled. Every node on the Freenet network contributes storage space to hold files and bandwidth that it uses to route requests from its peers.

As a direct result of the anonymity requirements, the node requesting content does not normally connect directly to the node that has it; instead, the request is routed across several intermediaries, none of which know which node made the request or which one had it. As a result, the total bandwidth required by the network to transfer a file is higher than in other systems, which can result in slower transfers, especially for infrequently accessed content.

Since version 0.7, Freenet offers two different levels of security: opennet and darknet. With opennet, users connect to arbitrary other users. With darknet, users connect only to "friends" with whom they previously exchanged public keys, named node-references. Both modes can be used together.

Content

Freenet's founders argue that true freedom of speech comes only with true anonymity and that the beneficial uses of Freenet outweigh its negative uses.^[27] Their view is that free speech, in itself, is not in contradiction with any other consideration—the information is not the crime. Freenet attempts to remove the possibility of any group imposing its beliefs or values on any data. Although many states censor communications to different extents, they all share one commonality in that a body must decide what information to censor and what information to allow. What may be acceptable to one group of people may be considered offensive or even dangerous to another. In essence, the purpose of Freenet is to ensure that no one is allowed to decide what is acceptable.

Reports of Freenet's use in authoritarian nations is difficult to track due to the very nature of Freenet's goals. One group, Freenet China, used to introduce the Freenet software to Chinese users starting from 2001 and distribute it within China through e-mails and on disks after the group's website was blocked by the Chinese authorities on the mainland. It was reported that in 2002 Freenet China had several thousand dedicated users.^{[28]: 70–71} However, Freenet opennet traffic was blocked in China around the 2010s.^{[citation needed]}

Technical design

See also: Cryptography

The Freenet file sharing network stores documents and allows them to be retrieved later by an associated key, as is now possible with protocols such as HTTP. The network is designed to be highly survivable. The system has no central servers and is not subject to the control of any one individual or organization, including the designers of Freenet. The codebase size is over 192.000 lines of code.^[29] Information stored on Freenet is distributed around the network and stored on several different nodes. Encryption of data and relaying of requests makes it difficult to determine who inserted content into Freenet, who requested that content, or where the content was stored. This protects the anonymity of participants, and also makes it very difficult to censor specific content. Content is stored encrypted, making it difficult for even the operator of a node to determine what is stored on that node. This provides plausible deniability; which, in combination with request relaying, means that safe harbor laws that protect service providers may also protect Freenet node operators. When asked about the topic, Freenet developers defer to the EFF discussion which says that not being able to filter anything is a safe choice.^[30][31]

Distributed storage and caching of data

Like Winny, Share and Perfect Dark, Freenet not only transmits data between nodes but actually stores them, working as a huge distributed cache. To achieve this, each node allocates some amount of disk space to store data; this is configurable by the node operator, but is typically several GB (or more).

Files on Freenet are typically split into multiple small blocks, with duplicate blocks created to provide redundancy. Each block is handled independently, meaning that a single file may have parts stored on many different nodes.

Information flow in Freenet is different from networks like eMule or BitTorrent; in Freenet:

1. A user wishing to share a file or update a freesite "inserts" the file "to the network"
2. After "insertion" is finished, the publishing node is free to shut down, because the file is stored in the network. It will remain available for other users whether or not the original publishing node is online. No single node is responsible for the content; instead, it is replicated to many different nodes.

Two advantages of this design are high reliability and anonymity. Information remains available even if the publisher node goes offline, and is anonymously spread over many hosting nodes as encrypted blocks, not entire files.

The key disadvantage of the storage method is that no one node is responsible for any chunk of data. If a piece of data is not retrieved for some time and a node keeps getting new data, it will drop the old data sometime when its allocated disk space is fully used. In this way Freenet tends to 'forget' data which is not retrieved regularly (see also Effect).

While users can insert data into the network, there is no way to delete data. Due to Freenet's anonymous nature the original publishing node or owner of any piece of data is unknown. The only way data can be removed is if users don't request it.

Network

Typically, a host computer on the network runs the software that acts as a node, and it connects to other hosts running that same software to form a large distributed, variable-size network of peer nodes. Some nodes are end user nodes, from which documents are requested and presented to human users. Other nodes serve only to route data. All nodes communicate with each other identically – there are no dedicated "clients" or "servers". It is not possible for a node to rate another node except by its capacity to insert and fetch data associated with a key. This is unlike most other P2P networks where node administrators can employ a ratio system, where users have to share a certain amount of content before they can download.

Freenet may also be considered a small world network.

The Freenet protocol is intended to be used on a network of complex topology, such as the Internet (Internet Protocol). Each node knows only about some number of other nodes that it can reach directly (its conceptual "neighbors"), but any node can be a neighbor to any other; no hierarchy or other structure is intended. Each message is routed through the network by passing from neighbor to neighbor until it reaches its destination. As each node passes a message to a neighbor, it does not know whether the neighbor will forward the message to another node, or is the final destination or original source of the message. This is intended to protect the anonymity of users and publishers.

Each node maintains a data store containing documents associated with keys, and a routing table associating nodes with records of their performance in retrieving different keys.

Protocol

 

A typical request sequence. The request moves through the network from node to node, backing out of a dead-end (step 3) and a loop (step 7) before locating the desired file.

The Freenet protocol uses a key-based routing protocol, similar to distributed hash tables. The routing algorithm changed significantly in version 0.7. Prior to version 0.7, Freenet used a heuristic routing algorithm where each node had no fixed location, and routing was based on which node had served a key closest to the key being fetched (in version 0.3) or which is estimated to serve it faster (in version 0.5). In either case, new connections were sometimes added to downstream nodes (i.e. the node that answered the request) when requests succeeded, and old nodes were discarded in least recently used order (or something close to it). Oskar Sandberg's research (during the development of version 0.7) shows that this "path folding" is critical, and that a very simple routing algorithm will suffice provided there is path folding.

The disadvantage of this is that it is very easy for an attacker to find Freenet nodes, and connect to them, because every node is continually attempting to find new connections. In version 0.7, Freenet supports both "opennet" (similar to the old algorithms, but simpler), and "darknet" (all node connections are set up manually, so only your friends know your node's IP address). Darknet is less convenient, but much more secure against a distant attacker.

This change required major changes in the routing algorithm. Every node has a location, which is a number between 0 and 1. When a key is requested, first the node checks the local data store. If it's not found, the key's hash is turned into another number in the same range, and the request is routed to the node whose location is closest to the key. This goes on until some number of hops is exceeded, there are no more nodes to search, or the data is found. If the data is found, it is cached on each node along the path. So there is no one source node for a key, and attempting to find where it is currently stored will result in it being cached more widely. Essentially the same process is used to insert a document into the network: the data is routed according to the key until it runs out of hops, and if no existing document is found with the same key, it is stored on each node. If older data is found, the older data is propagated and returned to the originator, and the insert "collides".

But this works only if the locations are clustered in the right way. Freenet assumes that the darknet (a subset of the global social network) is a small-world network, and nodes constantly attempt to swap locations (using the Metropolis–Hastings algorithm) in order to minimize their distance to their neighbors. If the network actually is a small-world network, Freenet should find data reasonably quickly; ideally on the order of ${\displaystyle O\left(\left[log\left(n\right)\right]^{2}\right)}$  hops in Big O notation. However, it does not guarantee that data will be found at all.^[32]

Eventually, either the document is found or the hop limit is exceeded. The terminal node sends a reply that makes its way back to the originator along the route specified by the intermediate nodes' records of pending requests. The intermediate nodes may choose to cache the document along the way. Besides saving bandwidth, this also makes documents harder to censor as there is no one "source node".

Effect

 

The effect of the node specialising on the particular location.

Initially, the locations in darknet are distributed randomly. This means that routing of requests is essentially random. In opennet connections are established by a join request which provides an optimized network structure if the existing network is already optimized.^[33] So the data in a newly started Freenet will be distributed somewhat randomly.^[34]

As location swapping (on darknet) and path folding (on opennet) progress, nodes which are close to one another will increasingly have close locations, and nodes which are far away will have distant locations. Data with similar keys will be stored on the same node.^[33]

The result is that the network will self-organize into a distributed, clustered structure where nodes tend to hold data items that are close together in key space. There will probably be multiple such clusters throughout the network, any given document being replicated numerous times, depending on how much it is used. This is a kind of "spontaneous symmetry breaking", in which an initially symmetric state (all nodes being the same, with random initial keys for each other) leads to a highly asymmetric situation, with nodes coming to specialize in data that has closely related keys.^{[citation needed]}

There are forces which tend to cause clustering (shared closeness data spreads throughout the network), and forces that tend to break up clusters (local caching of commonly used data). These forces will be different depending on how often data is used, so that seldom-used data will tend to be on just a few nodes which specialize in providing that data, and frequently used items will be spread widely throughout the network. This automatic mirroring counteracts the times when web traffic becomes overloaded, and due to a mature network's intelligent routing, a network of size n should require only log(n) time to retrieve a document on average.^[35]

Keys

Keys are hashes: there is no notion of semantic closeness when speaking of key closeness. Therefore, there will be no correlation between key closeness and similar popularity of data as there might be if keys did exhibit some semantic meaning, thus avoiding bottlenecks caused by popular subjects.

There are two main varieties of keys in use on Freenet, the Content Hash Key (CHK) and the Signed Subspace Key (SSK). A subtype of SSKs is the Updatable Subspace Key (USK) which adds versioning to allow secure updating of content.

A CHK is a SHA-256 hash of a document (after encryption, which itself depends on the hash of the plaintext) and thus a node can check that the document returned is correct by hashing it and checking the digest against the key. This key contains the meat of the data on Freenet. It carries all the binary data building blocks for the content to be delivered to the client for reassembly and decryption. The CHK is unique by nature and provides tamperproof content. A hostile node altering the data under a CHK will immediately be detected by the next node or the client. CHKs also reduce the redundancy of data since the same data will have the same CHK and when multiple sites reference the same large files, they can reference to the same CHK.^[36]

SSKs are based on public-key cryptography. Currently Freenet uses the DSA algorithm. Documents inserted under SSKs are signed by the inserter, and this signature can be verified by every node to ensure that the data is not tampered with. SSKs can be used to establish a verifiable pseudonymous identity on Freenet, and allow for multiple documents to be inserted securely by a single person. Files inserted with an SSK are effectively immutable, since inserting a second file with the same name can cause collisions. USKs resolve this by adding a version number to the keys which is also used for providing update notification for keys registered as bookmarks in the web interface.^[37] Another subtype of the SSK is the Keyword Signed Key, or KSK, in which the key pair is generated in a standard way from a simple human-readable string. Inserting a document using a KSK allows the document to be retrieved and decrypted if and only if the requester knows the human-readable string; this allows for more convenient (but less secure) URIs for users to refer to.^[38]

Scalability

A network is said to be scalable if its performance does not deteriorate even if the network is very large. The scalability of Freenet is being evaluated, but similar architectures have been shown to scale logarithmically.^[39] This work indicates that Freenet can find data in ${\displaystyle O(\log ^{2}n)}$  hops on a small-world network (which includes both opennet and darknet style Freenet networks), when ignoring the caching which could improve the scalability for popular content. However, this scalability is difficult to test without a very large network. Furthermore, the security features inherent to Freenet make detailed performance analysis (including things as simple as determining the size of the network) difficult to do accurately. As of now, the scalability of Freenet has yet to be tested.

Darknet versus opennet

As of version 0.7, Freenet supports both "darknet" and "opennet" connections. Opennet connections are made automatically by nodes with opennet enabled, while darknet connections are manually established between users that know and trust each other. Freenet developers describe the trust needed as "will not crack their Freenet node".^[40] Opennet connections are easy to use, but darknet connections are more secure against attackers on the network, and can make it difficult for an attacker (such as an oppressive government) to even determine that a user is running Freenet in the first place.^[41]

The core innovation in Freenet 0.7 is to allow a globally scalable darknet, capable (at least in theory) of supporting millions of users. Previous darknets, such as WASTE, have been limited to relatively small disconnected networks. The scalability of Freenet is made possible by the fact that human relationships tend to form small-world networks, a property that can be exploited to find short paths between any two people. The work is based on a speech given at DEF CON 13 by Ian Clarke and Swedish mathematician Oskar Sandberg. Furthermore, the routing algorithm is capable of routing over a mixture of opennet and darknet connections, allowing people who have only a few friends using the network to get the performance from having sufficient connections while still receiving some of the security benefits of darknet connections. This also means that small darknets where some users also have opennet connections are fully integrated into the whole Freenet network, allowing all users access to all content, whether they run opennet, darknet, or a hybrid of the two, except for darknet pockets connected only by a single hybrid node.^[33]

Tools and applications

 

Screenshot of Frost running on Microsoft Windows

Unlike many other P2P applications Freenet does not provide comprehensive functionality itself. Freenet is modular and features an API called Freenet Client Protocol (FCP) for other programs to use to implement services such as message boards, file sharing, or online chat.^[42]

Communication

Freenet Messaging System (FMS)

FMS was designed to address problems with Frost such as denial of service attacks and spam. Users publish trust lists, and each user downloads messages only from identities they trust and identities trusted by identities they trust. FMS is developed anonymously and can be downloaded from the FMS freesite within Freenet. It does not have an official site on the normal Internet. It features random post delay, support for many identities, and a distinction between trusting a user's posts and trusting their trust list. It is written in C++ and is a separate application from Freenet which uses the Freenet Client Protocol (FCP) to interface with Freenet.

Frost

Frost includes support for convenient file sharing, but its design is inherently vulnerable to spam and denial of service attacks.^[43] Frost can be downloaded from the Frost home page on SourceForge, or from the Frost freesite within Freenet. It is not endorsed by the Freenet developers. Frost is written in Java and is a separate application from Freenet.

Sone

Sone provides a simpler interface inspired by Facebook^[44] with public anonymous discussions and image galleries. It provides an API for control from other programs^[45] is also used to implement a comment system for static websites in the regular internet.^[46][47]

Utilities

jSite

jSite is a tool to upload websites. It handles keys and manages uploading files.

Infocalypse

Infocalypse is an extension for the distributed revision control system Mercurial. It uses an optimized structure to minimize the number of requests to retrieve new data, and allows supporting a repository by securely reuploading most parts of the data without requiring the owner's private keys.^[48]

Libraries

FCPLib

FCPLib (Freenet Client Protocol Library) aims to be a cross-platform natively compiled set of C++-based functions for storing and retrieving information to and from Freenet. FCPLib supports Windows NT/2K/XP, Debian, BSD, Solaris, and macOS.

lib-pyFreenet

lib-pyFreenet exposes Freenet functionality to Python programs. Infocalypse uses it.

Vulnerabilities

Law enforcement agencies have claimed to have successfully infiltrated Freenet opennet in order to deanonymize users^[49] but no technical details have been given to support these allegations. One report stated that, "A child-porn investigation focused on ... [the suspect] when the authorities were monitoring the online network, Freenet."^[50] A different report indicated arrests may have been based on the BlackICE project leaks, that are debunked for using bad math^[51] and for using an incorrectly calculated false positives rate and a false model.^[52]

A court case in the Peel Region of Ontario, Canada R. v. Owen, 2017 ONCJ 729 (CanLII), illustrated that law enforcement do in fact have a presence, after Peel Regional Police located who had been downloading illegal material on the Freenet network.^[53] The court decision indicates that a Canadian Law Enforcement agency operates nodes running modified Freenet software in the hope of determining who is requesting illegal material.

• Routing Table Insertion (RTI) Attack^[54]

Notability

Freenet has had significant publicity in the mainstream press, including articles in The New York Times, and coverage on CNN, 60 Minutes II, the BBC, The Guardian,^[55] and elsewhere.

Freenet received the SUMA-Award 2014 for "protection against total surveillance".^[24][25][26]

Freesite

A "freesite" is a site hosted on the Freenet network. Because it contains only static content, it cannot contain any active content like server-side scripts or databases. Freesites are coded in HTML and support as many features as the browser viewing the page allows; however, there are some exceptions where the Freenet software will remove parts of the code that may be used to reveal the identity of the person viewing the page (making a page access something on the internet, for example).

See also

•  Free and open-source software portal

• Peer-to-peer web hosting
• Rendezvous protocol
• Anonymous P2P
• Crypto-anarchism
• Cypherpunk
• Distributed file system
• Freedom of information
• Friend-to-friend

Comparable software

• GNUnet
• I2P
• InterPlanetary File System
• Java Anon Proxy (also known as JonDonym)
• Osiris
• Perfect Dark – also creates a distributed data store shared by anonymous nodes; the successor to Share, which itself is the successor of Winny
• Tahoe-LAFS
• ZeroNet

References

1. . Freenet: The Free Network official website. 22 September 2008. Archived from the original on 21 September 2013. Retrieved 31 May 2014.
2. "Freenet build 1497: fix severe path folding vulnerability". 4 March 2023.
3. Language specific versions of Freenet 7 February 2018 at the Wayback Machine, GitHub: Freenet.
4. What is Freenet? 16 September 2011 at the Wayback Machine, Freenet: The Free network official website.
5. Taylor, Ian J. From P2P to Web Services and Grids: Peers in a Client/Server World. London: Springer, 2005.
6. Cohen, Adam (26 June 2000). . Time. Archived from the original on 8 July 2008. Retrieved 18 December 2011.
7. Beckett, Andy (26 November 2009). . The Guardian. Archived from the original on 8 September 2013. Retrieved 26 November 2009.{{cite news}}: CS1 maint: bot: original URL status unknown (link) The Guardian writes about Freenet (Ian Clarke's response)
8. "Sone: Pseudonymes Microblogging über Freenet". from the original on 5 October 2015. Retrieved 15 September 2015., German article, 2010
9. "Infoclypse". Wiki. Mercurial. from the original on 3 November 2021. Retrieved 2 December 2021.
10. "Flog Helper: Easy Blogging over Freenet". GitHub. 7 February 2019. from the original on 5 February 2022. Retrieved 16 December 2011.
11. "Web of Trust". 7 February 2019. from the original on 8 December 2015. Retrieved 15 September 2015.
12. "Freenet over Sneakernet. Freenet Key: USK@MYLAnId-ZEyXhDGGbYOa1gOtkZZrFNTXjFl1dibLj9E,Xpu27DoAKKc8b0718E-ZteFrGqCYROe7XBBJI57pB4M,AQACAAE/Shoeshop/2/". {{cite web}}: Missing or empty |url= (help)
13. Markoff, John (10 May 2000). "Cyberspace Programmers Confront Copyright Laws". The New York Times. from the original on 17 February 2017. Retrieved 19 February 2017.
14. "Coders prepare son of Napster". BBC News. 12 March 2001. from the original on 4 January 2014. Retrieved 1 June 2014.
15. "Fighting for free speech on the Net". CNN. 19 December 2005. from the original on 2 June 2014. Retrieved 1 June 2014.
16. Ian Clarke. A distributed decentralised information storage and retrieval system 16 March 2012 at the Wayback Machine. Unpublished report, Division of Informatics, University of Edinburgh, 1999.
17. Ian Clarke, Oskar Sandberg, Brandon Wiley, and Theodore W. Hong. Freenet: A Distributed Anonymous Information Storage and Retrieval System 4 April 2015 at the Wayback Machine. In: Proceedings of the International Workshop on Designing Privacy Enhancing Technologies: Design Issues in Anonymity and Unobservability. New York, NY: Springer-Verlag, 2001, p. 46-66.
18. Clarke, Ian; Sandberg, Oskar; Wiley, Brandon; Hong, Theodore W. (24 March 2019). "Freenet: A Distributed Anonymous Information Storage and Retrieval System". Springer-Verlag New York, Inc.: 46–66. CiteSeerX 10.1.1.10.4919. {{cite journal}}: Cite journal requires |journal= (help)
19. Singh, Munindar P. The Practical Handbook of Internet Computing. Boca Raton, Fl.: Chapman & Hall, 2005.
20. Ihlenfeld, Jens (4 April 2006). "Freenet 0.7 soll globales Darknet schaffen". Golem. from the original on 5 October 2015. Retrieved 17 September 2015.
21. release information for Freenet 0.7.5 29 November 2014 at the Wayback Machine, last accessed 17 September 2015
22. release information for Freenet build 1226 29 November 2014 at the Wayback Machine, last accessed 17 September 2015
23. Freenet 1468 release notes 29 November 2014 at the Wayback Machine 2015
24. SUMA Award 20 March 2015 at the Wayback Machine, 11 February 2015.
25. recording of the SUMA Award Ceremony 2015 5 September 2015 at the Wayback Machine, published on 14 April 2015.
26. SUMA Award für das Freenet Projekt 24 September 2015 at the Wayback Machine Jo Bager in Heise online, 2015
27. . Archived from the original on 30 April 2011. Retrieved 20 December 2010.
28. Damm, Jens, and Simona Thomas. Chinese Cyberspaces Technological Changes and Political Effects. London: Routledge, 2006.
29. Terry, Kyle. The dark side of the web -- exploring darknets. Salem, Baden-Württemberg: TEDx Talks. Archived from the original on 11 December 2021.
30. Toseland, Matthew. . Archived from the original on 3 March 2016. Retrieved 27 January 2013.
31. "IAAL*: What Peer-to-Peer Developers Need to Know about Copyright Law". 10 January 2006. from the original on 30 November 2015. Retrieved 15 September 2015.
32. Clarke, Ian (2010). Private Communication Through a Network of Trusted Connections: The Dark Freenet (PDF). (PDF) from the original on 1 December 2017. Retrieved 15 September 2015.
33. Roos, Stefanie (2014). Measuring Freenet in the Wild: Censorship-Resilience under Observation (PDF). Springer International Publishing. pp. 263–282. ISBN 978-3-319-08505-0. (PDF) from the original on 16 November 2014. Retrieved 15 September 2015.
34. "Freenet Project Documentation". freenetproject.org. from the original on 16 February 2011. Retrieved 20 April 2022.
35. "FreeNet". networxsecurity.org. from the original on 26 January 2019. Retrieved 25 January 2019.
36. "freesitemgr, code for inserting files as CHK, fixed revision". GitHub. from the original on 5 February 2022. Retrieved 29 November 2017.
37. Babenhauserheide, Arne. "USK and Date-Hints: Finding the newest version of a site in Freenet's immutable datastore". draketo.de. from the original on 8 February 2015. Retrieved 29 November 2017.
38. Babenhauserheide, Arne. "Effortless password protected sharing of files via Freenet". draketo.de. from the original on 10 September 2015. Retrieved 29 November 2017.
39. Kleinberg, Jon (2000). "The Small-World Phenomenon: An Algorithmic Perspective" (PDF). Proceedings of the thirty-second annual ACM symposium on Theory of computing. pp. 163–70. doi:10.1145/335305.335325. ISBN 978-1-58113-184-0. S2CID 221559836. (PDF) from the original on 12 November 2013. Retrieved 22 August 2013.
40. "Required trust for forming a darknet connection". random_babcom. 29 November 2017. Retrieved 29 November 2017.^{[permanent dead link]}
41. "Darknet-Fähigkeiten sollen Softwarenutzung verbergen". Golem. 9 May 2008. from the original on 5 October 2015. Retrieved 29 November 2017.
42. Freenet Social Networking guide 15 August 2015 at the Wayback Machine Justus Ranvier, 2013
43. Developer discussion about fixing Frost shortcomings 1 December 2017 at the Wayback Machine Matthew Toseland, 2007
44. description of Sone by its developer 1 December 2017 at the Wayback Machine, "it's a Facebook clone on top of Freenet", retrieved 15 September 2015
45. Sone in Freenet Wiki 12 August 2015 at the Wayback Machine, with the description of the FCP API, retrieved 14 September 2015
46. babcom description 11 May 2015 at the Wayback Machine, "it submits a search request on your local Sone instance by creating an iframe with the right URL", 2014.
47. "Sone". from the original on 2 October 2015. Retrieved 15 September 2015.
48. "Information about infocalypse. A mirror of the included documentation". from the original on 27 January 2012. Retrieved 16 December 2011.
49. Dickinson, Forum Communications Company 1815 1st Street West; at225-8111, North Dakota 58602 Call us. "news". The Dickinson Press. from the original on 24 March 2019. Retrieved 24 March 2019.
50. "Man jailed indefinitely for refusing to decrypt hard drives loses appeal". Ars Technica. 20 March 2017. from the original on 21 March 2017. Retrieved 21 March 2017.
51. "Police department's tracking efforts based on false statistics". freenetproject.org. from the original on 5 February 2022. Retrieved 23 September 2017.
52. "Errors in the Levine 2017 paper on attacks against Freenet". draketo.de. from the original on 14 April 2021. Retrieved 3 January 2021.
53. "CanLII - 2017 ONCJ 729 (CanLII)". from the original on 17 January 2021. Retrieved 13 November 2017.
54. "A Routing Table Insertion (RTI) Attack on Freenet". from the original on 5 February 2022. Retrieved 12 February 2021.
55. The dark side of the internet 8 September 2013 at the Wayback Machine Andy Beckett in The Guardian 2009

Further reading

• Clarke, I.; Miller, S.G.; Hong, T.W.; Sandberg, O.; Wiley, B. (2002). "Protecting free expression online with Freenet" (PDF). IEEE Internet Computing. 6 (1): 40–9. CiteSeerX 10.1.1.21.9143. doi:10.1109/4236.978368. (PDF) from the original on 20 July 2004.
• Von Krogh, Georg; Spaeth, Sebastian; Lakhani, Karim R (2003). "Community, joining, and specialization in open source software innovation: A case study" (PDF). Research Policy. 32 (7): 1217–41. doi:10.1016/S0048-7333(03)00050-7. (PDF) from the original on 20 July 2018.
• Dingledine, Roger; Freedman, Michael J.; Molnar, David (2001). "The Free Haven Project: Distributed Anonymous Storage Service". Designing Privacy Enhancing Technologies. Lecture Notes in Computer Science. pp. 67–95. CiteSeerX 10.1.1.420.478. doi:10.1007/3-540-44702-4_5. ISBN 978-3-540-41724-8.
• Clarke, Ian; Sandberg, Oskar; Wiley, Brandon; Hong, Theodore W. (2001). "Freenet: A Distributed Anonymous Information Storage and Retrieval System". Designing Privacy Enhancing Technologies. Lecture Notes in Computer Science. pp. 46–66. CiteSeerX 10.1.1.26.4923. doi:10.1007/3-540-44702-4_4. ISBN 978-3-540-41724-8.
• Riehl, Damien A. (2000). "Peer-to-Peer Distribution Systems: Will Napster, Gnutella, and Freenet Create a Copyright Nirvana or Gehenna?". The William Mitchell Law Review. 27 (3): 1761.
• Roemer, Ryan (Fall 2002). "The Digital Evolution: Freenet and the Future of Copyright on the Internet". UCLA Journal of Law and Technology. 5.
• Sun, Xiaoqing; Liu, Baoxu; Feng, Dengguo (2005). "Analysis of Next Generation Routing of Freenet". Computer Engineering (17): 126–8.
• Hui Zhang; Goel, Ashish; Govindan, Ramesh (2002). "Using the small-world model to improve Freenet performance". INFOCOM 2002: Twenty-First Annual Joint Conference of the IEEE Computer and Communications Societies. Vol. 3. pp. 1228–37. CiteSeerX 10.1.1.74.7011. doi:10.1109/INFCOM.2002.1019373. ISBN 978-0-7803-7476-8. S2CID 13182323.

External links

• Official website