Tahoe-LAFS: Difference between revisions
imported>Mjh No edit summary |
imported>Echarlie No edit summary |
||
| Line 113: | Line 113: | ||
* Tahoe's erasure coding maintains availability in the event of a loss of nodes, but not malicious nodes. It's trivial to DoS a grid either by a Sybil attack or just using up all available storage if you know the introducer furl string. A [https://tahoe-lafs.org/trac/tahoe-lafs/ticket/467 patch] is in the works to allow clients to choose their own storage nodes that should mitigate this. | * Tahoe's erasure coding maintains availability in the event of a loss of nodes, but not malicious nodes. It's trivial to DoS a grid either by a Sybil attack or just using up all available storage if you know the introducer furl string. A [https://tahoe-lafs.org/trac/tahoe-lafs/ticket/467 patch] is in the works to allow clients to choose their own storage nodes that should mitigate this. | ||
[[Category:VTLUUG Projects]] | [[Category:VTLUUG:Projects]] | ||
[[Category:Infrastructure]] | [[Category:Infrastructure]] | ||
[[Category:Software]] | [[Category:Software]] | ||