Yes, that a poorly configured challenge/responce system. With TMDA it's possibly to have any address to which you send mail automatically added to your whitelist --- that allows people to reply to mails sent from you.
You're right, such a system is extremly efficient. The Tagged Message Delivery Agent implements such a system: TMDA.
With TMDA you can make several neat tricks with your email address, such as making short-lived addresses for one-time only uses and special addresses that only special senders can send mail to.
Yes, I know:-) But to be fair, then I've only seen these speeds when downloading Debian packages from nearby servers in Denmark or Sweden.
Right now, someone is downloading from my Freenet node with an average speed of 50 KB/s, another one is downloading with 30 KB/s. It's great to see, how the amount of queries has picked up after this Slashdot story.
Yes, if everything was encrypted and nobody could access it, then there wouldn't be much fun with Freenet:-)
I believe this key is part of the key you use when requesting a file on Freenet. Each file on Freenet is associated with a CHK, a Content Hash Key, which uniquely determines the file and which is also used to decode it. This key contains two parts, one of which is used to find the encrypted file, and the other part is used as key to decrypt the file.
So you cannot just decrypt your entire datastore, you need to know the keys of the files stored there before you can decrypt the files. I guess this means that one could "simply" collect a huge number of CHK's from Freenet and then use these to decode the files... please correct me if I'm wrong.
I believe Freenet works by storing whole files at several hosts at the same time. Each such file is associated with a key which is what you use when you try and download it.
Large files are broken up into many smaller files that can all be retrieved and used to reconstruct the big "splitfile" which has it's own key.
The data in the datastore on a node is encrypted, and it can only be decrypted by using the right key --- this is the key you use when downloading it. So if you just take a look at a datastore, then you wont be able to make anything out of it, but if you're looking for a particular file (and therefore know the key you're looking for) then it's possible to determine if the file is present in the datastore.
So nobody can do a general search on your computer for illegal material, they have to search for a particular piece of illegal material, which is much harder, as they have to search for the exact same file you store, or else they wont find anything. (The keys change with the content of the files, so if you add a newline to a document, you'll end up with a new key.)
That's how I've figured out things work, please correct me if I'm wrong:-)
The problem is, that it could have been your system that made the upsteam system go get this illegal content. So by mearely checking and requesting illegal material, you help spreading it!
This makes it kind of hard for you to argue, that the node you got the illegal material from was doing anything illegal before you asked for it. I think that's what they mean by plausible deniability.
Go read this article for an interesting analysis of the legal consequences of nets like Freenet.
I'm sitting on a good broadband connection over which I've been able to download files from the regular Internet at speeds up to 1.5 MB/s, so I have the necessary bandwidth...
With Freenet I've been able to download large splitfiles with an average speed of about 50 KB/s, with peaks over 100 KB/s. I tend to get about 2-3 KB/s on average downstream from fastest nodes I connect to, so you need a lot of connections to speed things up.
The seednode list is part of the "compromised" distribution tarball/zipfile:-) So you could download the release from SourceForge and then replace seednodes.ref with the one you got from my server.
You have to run a Freenet node for some time before the speed starts to pick up. The longer you run your node, then better it gets integrated into the network.
I've been using Freenet for a month now, and the performance has been growing steadily. Try downloading Freenet from my server to get a different set of seed-nodes than the ones distributed from SourceForge.
Slashdot Mirror
Yes, that a poorly configured challenge/responce system. With TMDA it's possibly to have any address to which you send mail automatically added to your whitelist --- that allows people to reply to mails sent from you.
You're right, such a system is extremly efficient. The Tagged Message Delivery Agent implements such a system: TMDA.
With TMDA you can make several neat tricks with your email address, such as making short-lived addresses for one-time only uses and special addresses that only special senders can send mail to.
Yes, I know :-) But to be fair, then I've only seen these speeds when downloading Debian packages from nearby servers in Denmark or Sweden.
Right now, someone is downloading from my Freenet node with an average speed of 50 KB/s, another one is downloading with 30 KB/s. It's great to see, how the amount of queries has picked up after this Slashdot story.
Yes, if everything was encrypted and nobody could access it, then there wouldn't be much fun with Freenet :-)
I believe this key is part of the key you use when requesting a file on Freenet. Each file on Freenet is associated with a CHK, a Content Hash Key, which uniquely determines the file and which is also used to decode it. This key contains two parts, one of which is used to find the encrypted file, and the other part is used as key to decrypt the file.
So you cannot just decrypt your entire datastore, you need to know the keys of the files stored there before you can decrypt the files. I guess this means that one could "simply" collect a huge number of CHK's from Freenet and then use these to decode the files... please correct me if I'm wrong.
I believe Freenet works by storing whole files at several hosts at the same time. Each such file is associated with a key which is what you use when you try and download it.
:-)
Large files are broken up into many smaller files that can all be retrieved and used to reconstruct the big "splitfile" which has it's own key.
The data in the datastore on a node is encrypted, and it can only be decrypted by using the right key --- this is the key you use when downloading it. So if you just take a look at a datastore, then you wont be able to make anything out of it, but if you're looking for a particular file (and therefore know the key you're looking for) then it's possible to determine if the file is present in the datastore.
So nobody can do a general search on your computer for illegal material, they have to search for a particular piece of illegal material, which is much harder, as they have to search for the exact same file you store, or else they wont find anything. (The keys change with the content of the files, so if you add a newline to a document, you'll end up with a new key.)
That's how I've figured out things work, please correct me if I'm wrong
The problem is, that it could have been your system that made the upsteam system go get this illegal content. So by mearely checking and requesting illegal material, you help spreading it!
This makes it kind of hard for you to argue, that the node you got the illegal material from was doing anything illegal before you asked for it. I think that's what they mean by plausible deniability.
Go read this article for an interesting analysis of the legal consequences of nets like Freenet.
I don't think the seednodes.ref file changes that often, but I've now made it readily available for download and made a small description here.
I'm sitting on a good broadband connection over which I've been able to download files from the regular Internet at speeds up to 1.5 MB/s, so I have the necessary bandwidth...
With Freenet I've been able to download large splitfiles with an average speed of about 50 KB/s, with peaks over 100 KB/s. I tend to get about 2-3 KB/s on average downstream from fastest nodes I connect to, so you need a lot of connections to speed things up.
Hehe, you're right, one cannot be too careful.
The seednode list is part of the "compromised" distribution tarball/zipfile :-) So you could download the release from SourceForge and then replace seednodes.ref with the one you got from my server.
You have to run a Freenet node for some time before the speed starts to pick up. The longer you run your node, then better it gets integrated into the network.
I've been using Freenet for a month now, and the performance has been growing steadily. Try downloading Freenet from my server to get a different set of seed-nodes than the ones distributed from SourceForge.