mirror volunteers needed
If you are brave and have a unix account/machine with approximately 2Gig of disk free, we need you. -- Julian Assange |If you want to build a ship, don't drum up people |together to collect wood or assign them tasks and proff@iq.org |work, but rather teach them to long for the endless proff@gnu.ai.mit.edu |immensity of the sea. -- Antoine de Saint Exupery
On 16 Oct 2001, Julian Assange wrote:
If you are brave and have a unix account/machine with approximately 2Gig of disk free, we need you.
I have a machine with 2 gig (or thereabouts), located in Australia. Bandwidth is low (64k ISDN) but the machine is available. If high bandwidth is a necessity I know someone who might be able to help depending on the content. -- mailto:zem@zip.com.au F289 2BDB 1DA0 F4C4 DC87 EC36 B2E3 4E75 C853 FD93 http://zem.squidly.org/ "I'm invisible, I'm invisible, I'm invisible.."
Julian Assange wrote:
If you are brave and have a unix account/machine with approximately 2Gig of disk free, we need you.
More details, please. Mainly the kind of material to be hosted. Holding 2GB of kiddie porn (horseman alert!) might be objectionable on moral grounds as well as legal grounds. What kind of traffic is expected, in terms of connections per hours and bytes per hour? Why does it need to be a *NIX machine? Ease of remote access, security, active content, or the requirements of the mirroring software? The mirror would presumably need a fixed IP address. Are there any other requirements? -- Steve Furlong Computer Condottiere Have GNU, Will Travel 617-670-3793 "Good people do not need laws to tell them to act responsibly while bad people will find a way around the laws." -- Plato
Julian Assange wrote:
If you are brave and have a unix account/machine with approximately 2Gig of disk free, we need you.
More details, please. Mainly the kind of material to be hosted. Holding 2GB of kiddie porn (horseman alert!) might be objectionable on moral grounds as well as legal grounds.
Documents and images. No kiddie porn, but there are still three other horsemen to choose from. Absolutely legal for now, bar retrospective legislation, but that won't stop the horse trainers from pretending otherwise. Constitutionally protected in the US, but that doesn't mean you won't cop flak from ISP higher-up and other organisations regardless of where you live. If you'd be happy to mirror cryptome.org, then you'd probably be happy to mirror this material.
What kind of traffic is expected, in terms of connections per hours and bytes per hour?
Depends on interest. We can use dns tricks to shape traffic to reflect your resources.
Why does it need to be a *NIX machine? Ease of remote access, security, active content, or the requirements of the mirroring software?
The anonymous push nature of the mirroring software. We can support non-unix pull mirrors too, provided there are enough push mirrors to feed from. The software could be ported to other operating systems without too much difficulty, but that's another project.
The mirror would presumably need a fixed IP address. Are there any other requirements?
An ability to create mail-aliases, gpg, perl5, and a good sense of humour :) Cheers, Julian. -- Julian Assange |If you want to build a ship, don't drum up people |together to collect wood or assign them tasks and proff@iq.org |work, but rather teach them to long for the endless proff@gnu.ai.mit.edu |immensity of the sea. -- Antoine de Saint Exupery
On Tue, Oct 16, 2001 at 07:56:20PM +1000, Julian Assange wrote:
Julian Assange wrote:
If you are brave and have a unix account/machine with approximately 2Gig of disk free, we need you.
More details, please. Mainly the kind of material to be hosted. Holding 2GB of kiddie porn (horseman alert!) might be objectionable on moral grounds as well as legal grounds.
Documents and images. No kiddie porn, but there are still three other horsemen to choose from. Absolutely legal for now, bar retrospective legislation, but that won't stop the horse trainers from pretending otherwise. Constitutionally protected in the US, but that doesn't mean you won't cop flak from ISP higher-up and other organisations regardless of where you live.
Where's the site? I'm sure some of us might be interested if we can see whether we care about the content.
If you'd be happy to mirror cryptome.org, then you'd probably be happy to mirror this material.
Thanks for the legal advice. cryptome still has decss.zip (and I'm damned happy they do). Nearly every other site with it caved to MPAA pressure. (Publicly) mirroring cryptome isn't for the timid. Asking people to mirror content that might be dangerous to their status with their upstream provider requires some more details. -- Greg
pressure. (Publicly) mirroring cryptome isn't for the timid. Asking people to mirror content that might be dangerous to their status with their upstream provider requires some more details.
Content is not fully predictable due to the distribution system employed. If your upstream shoots before threatening, you probably don't want to mirror this material. Cheers, Julian.
At 07:56 PM 10/16/2001 +1000, Julian Assange wrote:
The anonymous push nature of the mirroring software. We can support non-unix pull mirrors too, provided there are enough push mirrors to feed from. The software could be ported to other operating systems without too much difficulty, but that's another project.
I get the impression this isn't exactly "mirroring" static content, but participating in a distributed publishing/retrieval system, a la Freenet and Mojo Nation or BitTorrent .. or maybe more like Gnutella or Kazaa .. or even Publius, which was nice but never seemed to catch on. Is that correct?
The mirror would presumably need a fixed IP address. Are there any other requirements?
An ability to create mail-aliases, gpg, perl5, and a good sense of humour :)
What software are you using? Is it well-known? Debugged? Is the source available? (well, it's Perl, I guess..) I don't mind mirroring Cryptome, but I'm pretty wary of installing other people's newly-hacked-up code in a [quasi-]production environment .. your proposal creates two kinds of risk. The first, which is relatively familiar by now, is content risk, from people angry about the content .. the second is the risk of security problems in the code or its configuration/installation, and that sounds like a bigger issue to me. Why not just use one of the existing distributed systems for this content? If you put content in the Gnutella or Kazaa systems, you can give us filenames or search strings and then we just make locally cached copies and leave machines running (even crappy little windows boxes) to create dispersed hard-to-clobber-them-all content. If you put it in the Mojo/Freenet/BitTorrent systems, and make the URLs of the content publically available, helpful people can make local copies of all or parts of your files pretty easily, too. Or, alternately, make just content available as a .zip or .tgz, and let others serve it using FTP/HTTP servers they're already familiar with. If you can find a way to separate the content risk from the untrusted software risk, this project (whatever it is) might have a better chance of success. -- Greg Broiles gbroiles@well.com "We have found and closed the thing you watch us with." -- New Delhi street kids
participants (6)
-
Alex Shiels -
Greg Broiles -
Greg Newby -
Julian Assange -
proff＠iq.org
-
Steve Furlong