[tahoe-dev] keeping private grids private

markus reichelt ml at mareichelt.com
Sat Mar 10 12:18:10 UTC 2012


* Vladimir Arseniev <vladimira at aport.ru> wrote:

> Let's say that we have a private grid, with both local and hosted
> servers.  But our introducer.furl falls into the wrong hands, and
> uninvited nodes start appearing.  Maybe they're just leeching
> storage.  Maybe they're disrupting the grid through flapping,
> running deep-check all the time, or whatever.  Maybe they're
> actively attacking the grid.

> How do we exclude them?

Block/grant access at the network level, or have the grid run over a
VPN.


> Can introducers be configured to accept only known nodes?

Have a look at this:

extendable Introducer protocol: dictionary-based, signed
announcements:
https://tahoe-lafs.org/trac/tahoe-lafs/ticket/466

-- 
left blank, right bald
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: not available
URL: <http://tahoe-lafs.org/pipermail/tahoe-dev/attachments/20120310/c2d369d6/attachment.asc>


More information about the tahoe-dev mailing list