If the machine run the introducer down,what can i do

Roland Haeder r.haeder at web.de
Mon Mar 17 21:56:35 UTC 2014

On 03/17/2014 10:08 PM, Zooko Wilcox-OHearn wrote:
> That's right. If you have a backup of the introducer's private keys
> then you could set up a new introducer that would have the same FURL.
> If not, then you'll have to put in the new introducer's FURL to each
> storage server and each client.
> The multi-introducer ticket that str4d mentioned is ticket #68:
> https://tahoe-lafs.org/trac/tahoe-lafs/ticket/68# implement
> distributed introduction, remove Introducer as a single point of
> failure
> The state of that ticket is: "test-needed" — it is waiting for someone
> to write unit tests that test the code changed by the patch.
> Regards,
> Zooko
> _______________________________________________
> tahoe-dev mailing list
> tahoe-dev at tahoe-lafs.org
> https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
Still the chicken-egg-problem needs to be solved:

How can a virgin node get "knowledge" about the network without
bootstrappers? :-) Of course, you can have multiple bootstrap nodes
("introducer" in your terms) so you have ruled out the SPoF (single
point of failure) but still privacy matters are left: all introducer
owner know about the network's structure, at least which IPs run the
storage nodes.

Okay, maybe not a topic here, as Tahoe-LAFS != Freenet.

So a good advice for you @topic start is that you run your introducer on
a RAID1 with at least 3 physical drives and none are SSDs please (SSD =
electronic method = shorter life of the "disk", HDD = magnetic =
longer-lasting storage).


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: <http://tahoe-lafs.org/pipermail/tahoe-dev/attachments/20140317/a2333118/attachment.asc>

More information about the tahoe-dev mailing list