* Vladimir Arseniev <vladim...@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
pgpXdlDR1tKE8.pgp
Description: PGP signature
_______________________________________________ tahoe-dev mailing list tahoe-dev@tahoe-lafs.org http://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
