From c43eacc3a9b976e69e9757f3ddecedf3c2fbbc1b Mon Sep 17 00:00:00 2001 From: Jean-Paul Calderone Date: Wed, 13 Jun 2018 08:27:45 -0400 Subject: [PATCH] clarify which party is vulnerable --- docs/proposed/http-storage-node-protocol.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/proposed/http-storage-node-protocol.rst b/docs/proposed/http-storage-node-protocol.rst index 3057a8194..d6591217b 100644 --- a/docs/proposed/http-storage-node-protocol.rst +++ b/docs/proposed/http-storage-node-protocol.rst @@ -36,7 +36,7 @@ Discussion !!!!!!!!!! A client node relies on a storage node to persist certain data until a future retrieval request is made. -In this way, the node is vulnerable to attacks which cause the data not to be persisted. +In this way, the client node is vulnerable to attacks which cause the data not to be persisted. Though this vulnerability can be (and typically is) mitigated by including redundancy in the share encoding parameters for stored data, it is still sensible to attempt to minimize unnecessary vulnerability to this attack.