[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[freehaven-dev] [Fwd: A Prototype Distributed Anonymous File Server]
I don't konw about this...
> quoted... http://www.kripto.org/blocks/
So what anonymity features does it have?
When you start your Blocks server it connects to the Blocks network
and broadcasts your IP address as being that of a server looking for
connections. This is the only time your IP is advertised to the network,
and it is never associated with any other messages.
All other messages use a simple routing mechanism using an
alphabetic list of connection identifiers. Only the small number of
servers you are immediately adjacent to can associate your IP with file
advertisements, and even they cannot tell if you uploaded the file or it
simply migrated automatically from another server.
All network traffic is encrypted using a 128Bit stream cipher using
a key derived from a 512bit Diffie-Hellman key exchange.
All data in the disk bound cache is encrypted using a 128bit block
cipher using a key derived from a strong Pseudo Random Number Generator
(entropy provided by user). The cache is completely destroyed and an
empty one recreated each time the server is started or stopped, and the
key is different each time. No information about the origin of the data
blocks is stored in the cache.
> I saw this on freshmeat. I haven't read past the blurb, below. The URL is:
> The home page blurb includes:
> What is Blocks?
> Blocks is an anonymous distributed file transfer system designed for
> people with permanent ?always on? Internet connections like DSL lines or
> cable modems. It allows you to anonymously upload files from, and
> download files to the Blocks server ?network?. Blocks differs from
> other anonymous file transfer utilities in that the following ways?
> All ?uploaded? files are split into small 64Kb blocks.
> ?File advertisements? are broadcast through out the network. Your Blocks
> application needs to be running to see them. When you do a ?search? you
> are actually searching the local list maintained by your Blocks
> application, searches are never broadcast.
> The data blocks are routed from server to server rather than from point
> to point, with content being replicated through out the ?network?. IP
> addresses are not associated with uploads or downloads in any way.
> Each Blocks application acts as a potential client, server, and caching
> proxy for data blocks.
> Blocks uses a large disk bound cache (1-64Gb) that is protected by a
> 128bit block cipher using a random key based on a strong Pseudo Random
> Number Generator (entropy provided by user), and the cache is deleted
> and recreated each time the Blocks server is stopped or
> started. Therefore, even after a crash or abnormal termination, the disk
> cache cannot be used to ascertain what data has been downloaded or was
> being served.
> All network connections are protected by a 128bit stream cipher using a
> session key created from a 512bit Diffie-Hellman key exchange. So,
> network logs cannot be used to identify what network passed through the
> You can easily set up your own separate Blocks network or join a public
> one. You can even participate in a public Blocks network when you are
> behind a firewall that stops incoming connections.
> Blocks uses very little resources so you can use your computer for other
> things while you are running your Blocks server. Blocks uses ~2Mb+(1Mb
> per 4Gb of cache) of memory and a tiny amount of CPU. You can configure
> how much of your bandwidth you want Blocks to use and even play Quake or
> Tribes online and still be running your Blocks server (128Kb/sec minimum
> is required).
> Blocks is completely public domain. There are no licensing restrictions
> on the code or the binaries? obviously there is no warranty either :-)
> - Bill
> Spectre mailing list - Spectre@smartypants.zks.net
"Not all those who wander are lost." firstname.lastname@example.org