From ff48e6741825afffcc5fda6a0686e329b3d6f364 Mon Sep 17 00:00:00 2001 From: Jean-Paul Calderone Date: Tue, 22 May 2018 08:42:16 -0400 Subject: [PATCH] flop some heading levels around --- docs/proposed/http-storage-node-protocol.rst | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/docs/proposed/http-storage-node-protocol.rst b/docs/proposed/http-storage-node-protocol.rst index 228d08f29..b6e23ba4d 100644 --- a/docs/proposed/http-storage-node-protocol.rst +++ b/docs/proposed/http-storage-node-protocol.rst @@ -12,11 +12,12 @@ Specifically, it should be possible to implement a Tahoe-LAFS storage server wit (substituting an HTTP server implementation). The Tahoe-LAFS client will also need to change but it is not expected that it will be noticably simplified by this change. -Security --------- Requirements -~~~~~~~~~~~~ +------------ + +Security +~~~~~~~~ Summary !!!!!!! @@ -62,7 +63,7 @@ Therefore, **message confidentiality** is necessary when exchanging these secret **Forward security** is preferred so that an attacker recording an exchange today cannot launch this attack at some future point after compromising the necessary keys. Solutions -~~~~~~~~~ +--------- Communication with the storage node will take place using TLS. The TLS version and configuration will be dictated by an ongoing understanding of best practices.